Automate phone calls using our AI calling platform.
Autocalls currently provides 3 triggers that can start a workflow and 5 actions a workflow can run. Use those building blocks to move information into the same workspace as the people, records, and next steps it affects.
Phone Call Ended
Triggers when a phone call ends, with extracted variables.
Updated Assistant
Triggers when assistants are fetched or updated in your Autocalls account.
Inbound Call
Triggers for variables before connecting an inbound call.
Add lead to a campaign
Add lead to an outbound campaign, to be called by an assistant from our platform.
Send SMS to Customer
Send an SMS to a customer using a phone number from our platform.
Start/Stop Campaign
Start or stop an outbound campaign from our platform.
Make Phone Call
Call a customer by it's phone number using an assistant from our platform.
Delete Lead
Delete a lead from a campaign.
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Autocalls event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
Phone Call Ended
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Autocalls action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Add lead to a campaign
Combine Autocalls with another integration and Coherence records to move information into the same workspace as the people, records, and next steps it affects.
Starts with
Phone Call Ended
Finishes with
Add lead to a campaign, then preserve the outcome in Coherence
The exact authentication fields depend on Autocalls. The workflow structure stays straightforward:
Authorize the Autocalls account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Autocalls or provide a complementary trigger or action.
Autocalls currently provides 3 triggers that can start a workflow and 5 actions a workflow can run. Use those building blocks to move information into the same workspace as the people, records, and next steps it affects.
Autocalls currently lists 3 triggers and 5 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Autocalls triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
