Real-time event-driven integration with Symplify.
When to use Event Hub
Event Hub is the right choice when you need Symplify to respond to system events in real time, keeping your data as current as possible. It works especially well if you already use a message broker for application events, or if you'd prefer not to integrate directly with the Symplify REST API.
How it works
As shown in the diagram above, events flow from Your System into a Message Broker (AWS SQS). Inside the broker, a MappingSelector is attached to the payload — an arbitrary string you define that tells Symplify how to route the incoming data. Symplify listens to the broker, reads the selector, and triggers one or more configured Actions in response.
As long as your messages follow the recommended format, no further integration work is needed.
MappingSelector
Each payload you send includes a MappingSelector — a free-form string you choose at implementation time. This string is used to route the event to one or more Actions in Symplify.
For example, you might send a GENERIC_USER payload with MappingSelector: "CreateUser", then configure Symplify to execute both the CreateUser and EnterJourney actions whenever that selector arrives — as illustrated in the diagram. If no selector is provided, it defaults to the value of the Type field.
Tip: Because the MappingSelector decouples your event payload from the Symplify action configuration, you don't need to decide how data will be mapped at implementation time. Mappings can be updated in Symplify without touching your integration.
Learn more about, how to setup Event Hub.
Transport Options
AWS SQS is the recommended transport for Event Hub. If SQS is not available in your environment, the Symplify REST API accepts the same payload structure and mimics the broker behaviour — though some reliability and decoupling benefits of a message broker will not apply.
To learn more, please visit our API docs.