Webhook callback URLs

In a webhook input node, a webhook callback URL is a web address that receives notifications from a server when a specific event occurs. It is a way for an application to notify another application of an event, sending data to a specific URL in real time. In IBM® App Connect Enterprise, webhook callback URLs are used to receive notifications from external applications when a specific event occurs, which allows real-time integration and event-driven processing.

How webhook callback URLs work in App Connect

The following steps provide an overview of how webhook callback URLs work in App Connect:
  1. Configuring the webhook URL: In App Connect, you configure a webhook callback URL that receives notifications from an external application. For more information about configuring the webhook URL, see Configuring a webhook callback URL.
  2. External application sends a notification: When an event occurs in the external application, it sends a request to the callback URL specified in App Connect.
  3. App Connect receives a notification: App Connect receives the notification and processes the event information.
  4. Event-driven processing: App Connect uses the event information to trigger a flow or for other types of processing.

Manual webhook callback URL registration

For some connectors, such as Slack, you must register the App Connect generated webhook callback URL with the application provider. You can find the App Connect generated webhook callback URL associated with the event (for example, New slash command message in Slack) listed in the Launch Connector Discovery view of the connector input node. You can then work with the account administrator to register the App Connect generated webhook callback URL with the application.

Webhook callback URL generated in Slack connector
The following connectors require manual webhook registration:
  • IBM Maximo®
  • Magento
  • Marketo
  • Slack

Automatic webhook callback URL registration

For some connectors, such as Eventbrite, the App Connect webhook callback URL is registered automatically. The application uses this URL to publish events, which then trigger the flow in App Connect. For example, if you add an Eventbrite New event trigger event to your flow, Eventbrite uses the webhook callback URL to trigger the flow when a new event is added. You can find the App Connect generated webhook callback URL associated with the event that is listed in the Launch Connector Discovery view of the connector input node.

Webhook callback URL generated in Eventbrite connector
The following connectors support automatic webhook registration:
  • Eventbrite
  • Amazon EventBridge