The Event hub functionality is perfect if you want to react quickly to events originating from your system, and need data in Symplify to be as up-to-date as possible at every single point in time. It's ideal if you already have a message broker where you publish application events, or if you want to avoid explicit integration with the Symplify REST API.
In an Event hub setup, Symplify is configured to listen for messages from a Message Broker (SQS or RabbitMQ), and instructed to take actions depending on incoming messages. As long as the incoming message format follows the recommended format, no additional integration is required.
Best practice is to send this data via AWS SQS, but if this is not possible the REST API mimics this functionality. The same payload is used but some benefits of the message broker are lost.
You will send a payload containing the data and then set a MappingSelector that will be used to map the data to one or more Actions in Symplify. I.e. you can send an event containing a GENERIC_USER payload with the MappingSelector "CreateUser". In Symplify you can them map this to the CreateUser action and the EnterJourney action and both these actions will be executed when an event comes in.
The mappingSelector is an arbitrary string that you choose. This way you will not have to decide at implementation time how the data shall be mapped. If no mapping selector is set, it will default to the same value as the Type field.
To learn more, please visit our API docs.