Trigger a journey from your application

Name the business event

Use an event name such as order.paid and a stable client event ID. Include a subscriber reference and the properties your automation needs. Keep personal data to the fields needed for the journey.

Use the same event ID and Idempotency-Key when retrying. A batch is validated and stored atomically. A rejected batch accepts no new events; fix the invalid input and keep the original IDs when retrying. Event IDs deduplicate within the workspace and mode for 30 days.

Inspect the outcome

The event timeline records processing state. Match an automation's event_received trigger to the event name and properties. Test-mode and historical events are recorded without executing live automations. Use the event timeline to inspect matching before enabling a live journey.