WEBHOOKS

OVERVIEW

Webhooks are user-defined HTTP callbacks that are triggered by specific events. When such an event occurs, the source system sends an HTTP request to the URL configured for the webhook.

In SLASCONE, webhooks can be used to notify external systems when selected entities are created, updated, deleted, or registered.

SUPPORTED EVENTS

SLASCONE currently offers webhooks for the following events:

• Customer
  • Created
  • Updated
  • Deleted
• License
  • Created
  • Updated
  • Deleted
  • Activated
• License User
  • Created
  • Updated
  • Deleted
• Portal User
  • Registered
• Product
  • Updated
• Edition
  • Updated
• Consumption
  • Alert fired

SETTINGS

Execute webhook in parallel

Runs the webhook at the same time as the main workflow continues, without waiting for the webhook to finish.

Read entity after webhook call

Fetches and refreshes the entity’s data after the webhook has completed its execution.

Failure Policy

Defines how the system should behave when a webhook call fails.

• No policy
  No additional action is taken when the call fails.
• Retry Call
  Automatically retries the failed call based on the configured settings:
  • Max retry count – the maximum number of retry attempts
  • Retry interval (seconds) – the waiting time between each retry attempt

HEADERS

Headers allow you to include additional information such as Bearer tokens, API keys, content and format information, or custom metadata.

SUPPRESS WEBHOOK

API requests can include a header to control webhook invocation.

Header name: x-webhook-control

If the called endpoint would normally trigger a webhook, the webhook is suppressed when the header contains the value suppress.