Skip to main content
A trigger is the event that starts a workflow. It can react to an incoming HTTP request, a schedule, a new message or booking, a form submission, or another service event. This reference documents every trigger currently available in the editor. Browse by package in the navigation or search for the trigger by its node-picker name.

​
How trigger outputs work

When an event arrives, the trigger turns its data into outputs. Those outputs are the starting values for the rest of the workflow—for example, an incoming email’s sender, an HTTP request body, or a scheduled execution time. Some triggers change their outputs when you select a different event type or configuration. Make that choice before connecting the trigger to later actions.

​
Test before enabling

1

Configure the event

Select the account, event type, schedule, route, or other source settings documented for the trigger.
2

Generate a representative event

Send a test request or create a real service event so the workflow receives the same shape of data it will see in production.
3

Inspect the outputs

Confirm optional properties, files, and lists before relying on them in downstream actions.
4

Enable the workflow

Once the trigger and downstream actions behave as expected, enable the workflow so it can receive future events.
External triggers depend on the connected account and the service’s delivery behavior. Removing permissions, deleting a webhook or watch, or disabling the workflow can stop new events from arriving.
Need a step that runs after a trigger? Browse the complete Actions reference.