Triggers
The five ways an automation starts — by hand, on a schedule, from a webhook, as a tool, or from an event on the platform.
Every automation starts from a trigger:
| Trigger | Starts the automation when… |
|---|---|
| Manual Launch | Someone starts it from the dashboard |
| Time Schedule | A schedule you set comes round |
| Hosted Webhook | A request arrives at the automation's own webhook URL |
| Direct Tool Call | A flow calls it as a tool during a conversation |
| System Data Event | Something happens on the platform, such as a conversation finishing |
Choosing one
- After every call — a system data event, so the automation reacts as each conversation ends: post the result to a CRM, send a follow-up, update a sheet.
- From another system — a hosted webhook, so your CRM or form tool can start it.
- During a conversation — a direct tool call, reached from a flow with the Run Automation node.
- Regular jobs — a time schedule, for reports and batch work.
Tip
One automation per trigger keeps runs easy to read. Share logic between them with a sub-automation rather than one automation with several entry points.