Workflows
Triggers
Start the next step automatically when a call is answered or ends.
| Trigger | When it runs | Variables available |
|---|---|---|
| Call start | In the background as the call is answered. | Call details and the built-in variables. |
| After call | Once the call has ended and been summarised. | {{summary}}, {{outcome}}, {{intent}}, {{caller_name}}, {{duration_s}}, {{transcript}}, {{call.link}} and more. |
#Call start
Use it to look the caller up before the conversation gets going, for example in your CRM or shop. The results reach the assistant as soon as they are in, usually before the caller finishes their first sentence, so it can greet returning customers by name or know about an open order.
#After call
Use it for anything that should happen once a call is over: add a row to a sheet, create a deal, post to a channel, email a manager about complaints. Put a condition block after the trigger to act only on some calls, for example when {{outcome}} is message.
#Limits
Trigger chains run without a live conversation. They can't speak, transfer or use conversation tools, but they can use code, HTTP, app, AI, set, condition, switch, text and email blocks.