Triggers
Receive events from outside the platform over a webhook URL and run workflows in response.
A trigger is a webhook URL. Anything that can make an HTTP request can post to it, and the platform classifies what arrived, picks the handlers that match, and starts a workflow for each one.
Use a trigger when something outside the platform should start work inside it: a payment provider telling you a charge settled, a CRM telling you a deal moved stage, a cron job in another system, a button in an internal tool.
The three objects
Event trigger
The URL, its code, and how incoming requests are classified.
Event handler
A workflow to run, which events it responds to, and the parameters it receives.
Event request
One row per request received, with what it was classified as and what each handler did.
A trigger owns many handlers. One request can run several handlers, or none.
What happens when a request arrives
Two properties of this flow are worth knowing before you build on it.
The request is recorded before anything is classified. A request that matches no handler is still in the log, with the event type it was classified as. That is the first place to look when a webhook appears to do nothing.
Workflows are started, not awaited. The response returns once every workflow has been
accepted, carrying a runId for each. It does not carry workflow results, and a slow
workflow does not hold the caller's connection open. Results are fetched afterwards, which
Monitoring covers.
Every HTTP method on the trigger URL executes the trigger, including GET. There is no read-only
variant of the live URL. Use the inspect
endpoint when you want to see
a payload without running handlers.
Where to go next
Quickstart
Create a trigger, capture a real payload, and wire a workflow to it.
Event types
How requests are classified and how handlers are matched. The subtle part.
Handlers
Handler fields, the two expression languages, and workflow parameters.
Monitoring
The live monitor, recent requests, handler outcomes, and webhook activity.
Trigger API
Manage triggers, handlers and requests programmatically.