Automations
Workflows that run around your conversations — triggered by calls, schedules or webhooks, and connected to the rest of your stack.
A flow decides what to say. An automation decides what happens around it: enrich a record before a call, post the result to your CRM afterwards, follow up on WhatsApp the next day, or run a whole process in which a conversation is just one step.
Building blocks
Automations are built on a canvas from nodes. Among them:
- Start an AI conversation — place an outbound call or chat with a flow or agent, and monitor it while it runs.
- Call an HTTP endpoint or an integration — Google Sheets, Slack, email and more.
- Collect input from a person — a form with a stable public link, answered in the browser, with the answers flowing back into the automation.
- Assign a task — hand work to a person or an agent, with context and a deadline.
- Branch, loop and wait — on values, on outcomes, or until something happens.
- Generate and process media — images and video, stored as downloadable artifacts.
Files an automation produces can be retrieved over the API — see Automation artifacts.
Triggers
An automation starts from an event such as a finished call, on a schedule, from an incoming webhook, or from another automation. See Triggers.
Billing
Automation runs are billed per run from your balance, with a monthly free quota. See Balance and top-ups.
Tip
Keep the conversation in the flow and the plumbing in the automation. A flow that also posts to three systems is hard to test; an automation that reacts to its result is easy.
In this section
- TriggersThe five ways an automation starts — by hand, on a schedule, from a webhook, as a tool, or from an event on the platform.
- AI conversationsStart an outbound AI call or chat from an automation, then wait for the outcome — or watch the conversation and react while it runs.
- Collecting input from peoplePause an automation and ask a person for text, files or media — over a link, the inbox, email, a Work channel or the API.