Skip to main content
A trigger declares an event that can start an automation. Trigger functions return a signal containing the event data.
Deploying this program configures the Gmail event source. When a qualifying message arrives, Automate.ax creates an execution context and materializes the email signal with the parsed message.

​
Configuration and event data

Arguments passed to the trigger configure the subscription. The returned signal contains data from one matching event:
The Triggers reference documents each trigger’s configuration, event shape, filtering, and delivery behavior.

​
Trigger configuration is static

Event infrastructure is configured during deployment, before runtime values exist. Configuration that selects an event source—such as the account watched by onNewEmail—must therefore be static. A signal cannot choose the trigger’s account at runtime. Action account inputs are different: an action may select an account from a signal because that selection is resolved when the action executes. See Integration accounts.

​
Delivery and idempotency

Automate.ax owns provider subscriptions, renewal, ingestion, and durable event delivery. Provider notifications can be delivered more than once, so event sources normalize and deduplicate them using provider identities where the integration supports it. An event accepted by the active deployment keeps its own execution context. Actions in that context consume only its trigger and action outputs.

​
HTTP responses

HTTP triggers normally acknowledge accepted work immediately. With waitForResponse: true, ingress waits up to ten seconds for respondToHttpRequest in the same automation context. A missing response returns 504; execution can continue after the caller times out.