Consume Events
You can consume events sent from Adobe Commerce to Adobe I/O events in several ways. The following options for consuming events are available when adding events to your App Builder project and creating an event registration:
- Using the Journaling API (enabled by default)
- Using a Webhook URL
- Using a Runtime Action
- Using Amazon EventBridge
Using the Journaling API
When you create an Adobe I/O event registration, by default, the subscribed events get added to an ordered list (referred to as the journal). You can consume these events using a journaling endpoint URL that is unique to the registration. For more information on reading events from the journal, see the Introduction to Journaling.
You can also consume events from the Journaling API using the Adobe I/O Events SDK. See Subscribe to Events Using Journaling for details and sample code.
Using a Webhook URL
Consuming an event using a webhook URL is useful for cases that do not require App Builder to handle transformations to the event structure or additional API calls, which simplifies forwarding events from Adobe Commerce to a 3rd-party system using App Builder. The destination system must have an endpoint that can receive webhook requests to use this option.
You can register the webhook URL when creating or editing an event registration. If you are setting up the registration through the developer console UI, this option will appear in the final configuration step.
See Introduction to Adobe I/O Events Webhooks for more details.
Be careful not to confuse this method of consuming events with Runtime Actions as a Webhook. Runtime Actions as a Webhook is a functionality for creating a URL for App Builder to receive events from a 3rd party system.
Using a Runtime Action
An Adobe I/O Runtime Action allows you to receive Commerce events in an event registration. You can create actions from JavaScript functions, as described in Creating Actions. Within an action, you can execute business logic based on the received event payload, make API calls back to Adobe Commerce to update data, access additional information, and send data to another system.
See Runtime Action with a Callback to Commerce for an example of how a runtime action can consume an event and make an API call back to Commerce to get more information.
See more examples of end-to-end integrations between Commerce and 3rd party systems like ERPs that use runtime actions in our Starter Kit documentation.
Using Amazon EventBridge
You can configure an Adobe I/O event registration to forward received Commerce events to Amazon EventBridge. See Adobe I/O Events and Amazon EventBridge Integration for more details.
