Event-based integration connects systems without requiring the source application to execute every downstream step synchronously. Elaine can receive business events for automation and can call external endpoints from supported outbound processes.
Inbound events
A source system can submit an event with the data required for identification and processing. Elaine accepts the event and routes it into the configured automation, where data updates, decisions, messages, and other actions can be orchestrated.
This pattern is useful when the source system should report what happened but should not need to know which Elaine automation processes the event. Because downstream processing is asynchronous, the initial API response normally confirms acceptance rather than the final business outcome.
Outbound webhooks
Supported Elaine automations and business rules can call external HTTP endpoints to notify another system or request an external action. Keep the payload minimal, authenticate the endpoint, and avoid making a long-running external dependency part of a latency-sensitive process.
When event integration fits
- A CRM reports a customer or lifecycle event.
- A commerce system reports a transaction, product, or fulfillment event.
- A website or app submits an engagement signal.
- Elaine must notify an external system about a workflow outcome.
- The source and target systems should scale independently.
Reliability design
- Use stable event and entity identifiers.
- Assume that a delivery may be delayed or repeated and make processing idempotent where possible.
- Define timeouts, controlled retries, backoff, and a recovery queue or manual replay process.
- Record technical acceptance separately from final automation success.
- Monitor event age, failure rate, retry count, and unprocessed events.
- Document ordering requirements and avoid relying on order unless it is explicitly guaranteed.