Actions Overview
Actions are the tasks a workflow performs after a call ends and all conditions pass. You can add one or more actions to a workflow, and they execute sequentially from top to bottom.
Action Categories
CRM Actions
Connect your call data to your customer relationship management system.
- GoHighLevel (GHL) — Log calls, manage contacts, update pipelines, book appointments, and more in GHL
- HubSpot — Log calls, manage contacts, update deals, book meetings, and more in HubSpot
Calendar Actions
Automate appointment scheduling based on call outcomes.
- Google Calendar — Book events, cancel events, and check availability
- Calendly — Check availability, generate booking links, and cancel events
Messaging Actions
Send notifications and follow-ups through various channels.
- Email, SMS & Slack — Send emails, text messages, and Slack notifications with call data
Integration Actions
Connect to any external system via HTTP.
- Webhook — Send call data to any URL via POST request for custom integrations
Sequential Execution
Actions in a workflow run one after another, in the order they appear. This means you can set up dependent actions. For example:
- upsert_contact — Create or update a contact in your CRM
- log_call — Log the call record to that contact
- auto_tag — Tag the contact based on call outcome
- Slack message — Notify your team about the call
If an action fails, subsequent actions in the workflow still attempt to run. Check the Execution Log to see which actions succeeded and which failed.
Template Variables
Most actions support template variables that let you insert dynamic call data into your action configuration. These variables are replaced with actual values when the action runs.
| Variable | Description |
|---|---|
\{\{caller_name\}\} | Name of the caller (if identified) |
\{\{phone_number\}\} | The caller’s phone number |
\{\{summary\}\} | AI-generated call summary |
\{\{sentiment\}\} | Call sentiment (positive, negative, neutral) |
\{\{duration\}\} | Call duration in seconds |
\{\{transcript\}\} | Full call transcript |
\{\{agent_name\}\} | Name of the AI agent |
\{\{call_id\}\} | Unique identifier for the call |
\{\{direction\}\} | Call direction (inbound, outbound) |
\{\{date\}\} | Date and time of the call |
You can use these in text fields like email bodies, note content, Slack messages, and more. For example, an email subject might be: Call Summary: \{\{caller_name\}\} - \{\{sentiment\}\}.
Use \{\{summary\}\} in Slack and email notifications so recipients get a quick overview of the call without needing to open the dashboard.
Prerequisites
Before using an action, make sure the corresponding integration is connected:
- GHL actions require a GoHighLevel connection configured in Integrations
- HubSpot actions require a HubSpot OAuth connection
- Google Calendar actions require a Google Calendar OAuth connection
- Calendly actions require a Calendly API token
- Email actions require email settings to be configured
- Slack actions require a Slack webhook URL
- Webhook actions work immediately with no prerequisites