Understand the events, triggers, actions, and timing controls available in automated campaigns.
Key concepts
- Triggers determine when a campaign or transition becomes eligible to run.
- Events represent business or engagement occurrences received from Elaine or connected systems.
- Actions send messages, update data, call supported integrations, or move processing forward.
- Wait and timeout controls coordinate actions that must happen later or depend on another event.
How it works
- Define an event name, producer, payload contract, identifier, and expected frequency.
- Configure the consuming campaign state and any event-data fields it needs.
- Choose synchronous or asynchronous handling according to the required feedback.
- Test duplicate, missing, delayed, out-of-order, and malformed events.
- Monitor acceptance separately from downstream campaign completion.
Governance and considerations
- Use stable event names and version payload changes.
- Do not assume an accepted event was consumed by a campaign.
- Apply idempotency and correlation identifiers across system boundaries.
Note
Exact UI labels, availability, and behavior can depend on the Elaine.io release, licensed capabilities, permissions, and project configuration.