Connect Emarsys
Send a trigger payload to an Emarsys external event.
All connectors · Checked against AXO’s implementation in October 2026.
Prepare access
Use an owner or admin account in AXO and confirm the selected site. Have permission to authorize the external account or create its server credentials. Keep secrets in the connector’s protected configuration.
| Setting | Value to prepare |
|---|---|
username | API username. |
secret | API secret. |
event_id | External event ID. |
Connect
Open Integrations, find Emarsys, and open its setup. Enter the fields above and save with Connect (or Save changes for an existing connection).
- Create a trigger, select this integration as its destination, and render the provider’s expected payload in its template. Selecting Events to forward alone does not invoke this native trigger adapter.
- Choose the external event that starts the intended Emarsys program. The catalog labels Emarsys as a source; the trigger destination also exists.
Verify the result
The check reads API settings using WSSE authentication; it does not trigger the external event.
Record the AXO integration or trigger result and the receiving system’s result. A saved configuration, credential check, and completed delivery establish different things. Use a controlled destination for a test that writes data or sends a message.
Fix a failed connection
Check the username/secret pair, external event ID, and the identifier in your event template.
For a saved catalog connector, open Health to read the latest error, then repair the settings through the setup method on this page. Pause delivery while correcting an unintended destination. Reconnect OAuth when its grant is revoked; for key-based connections, save the replacement key, verify it, then revoke the old key at the provider.
Next: create an event-triggered action, or implement a webhook receiver.