Autocalls AI

Place outbound phone calls with an Autocalls.ai voice agent and run lead-calling campaigns end to end. Agents dial, qualify, and hand off to a person when the conversation needs judgment.

1 trigger 21 actions API key available

Platform Documentation ↗ Capability data verified 2026-08-01

Agent pulls the day's qualified leads from the CRM segment that feeds outbound

Agent checks each phone number's country and timezone against the campaign's schedule windows and allowed weekdays

Agent adds the accepted leads to the campaign with Create Lead, carrying their variables through

Agent reads Get Current User for the account balance and List Leads for the final queue size

Agent posts the queue size, the balance, and the leads it rejected on schedule grounds

The outbound owner approves the launch, and only then does the agent call Update Campaign Status to start

What This Integration Enables

Autocalls AI puts the campaign, not the call, at the centre. A campaign carries the outbound assistant that will speak, the phone numbers it dials from, a timezone, schedule windows, allowed weekdays, a retry policy and a parallel call limit. Those settings are not decoration. They are where calling compliance actually lives, and they are the reason a flow that loads leads into an Autocalls AI campaign is doing something more careful than pushing rows into a dialer.

The connector gives agents the full lifecycle: create the campaign, add leads with the variables the assistant will substitute into its prompt, start and stop it, and read back every call with its status, transcript, recording URL, cost breakdown and the evaluation data the assistant extracted from the conversation. That extracted data is the useful part downstream. An agent does not have to guess what a call meant from a duration and a disposition code; it can read the fields the assistant was told to collect and route on them. Then it does what a machine should not do alone, which is decide whether to spend the account's remaining balance on a list that cannot be un-called.

Without FlowRunner

Lists loaded by hand Someone exports a CSV, cleans it, and uploads it before the campaign can run

Calling rules live in someone's head Timezone and weekday restrictions are checked informally, if at all

Launch is a leap The campaign starts and the balance question surfaces when calls begin failing

With FlowRunner

Queue built from live pipeline Leads flow into the campaign from the CRM segment that already defines them

Rules checked per lead Every number is tested against the campaign's schedule windows before it joins the queue

Launch is a decision The owner sees queue size, balance and rejections together before anything dials

Use Case Scenarios

Building tomorrow's calling queue from live pipeline

Each evening a flow reads the CRM segment that defines qualified outbound. For each record, the agent checks the phone number's country against the campaign's schedule windows and allowed weekdays, drops the ones that cannot legally be called in that window, and adds the rest with Create Lead so the assistant receives their name, company and reason for the call as prompt variables. It reads List Leads to confirm the final queue and Get Current User for the balance. Then it stops and asks. The queue is assembled by the agent; the decision to run it belongs to a person.

Call outcomes routed by what the assistant heard

The On Call Ended trigger fires. The agent calls Get Call to read the full record: transcript, recording URL, who answered, cost, and the evaluation data the assistant extracted. Calls where the extracted fields show a booked follow-up go to the rep's queue in HubSpot with the transcript attached. Calls that hit voicemail update the lead's status with Update Lead so the retry policy handles them. Calls where the assistant recorded a complaint or an opt-out request never touch the retry path at all; they go straight to a person, because a second call to somebody who asked you to stop is not a retry, it is a problem.

Campaign retirement without orphaned data

A quarterly cleanup flow reads List Campaigns and finds campaigns that have been stopped for months. Before proposing anything, the agent exports each one's calls and leads so the transcripts and evaluation data survive the teardown, because Delete Campaign removes every lead attached to the campaign and releases its phone numbers back to the account. It posts the candidates with their last activity date, lead count and assigned numbers, and waits for a person to confirm which ones go.

Human-in-Loop Highlight

The gate is Update Campaign Status. Starting a campaign is the moment the account's balance turns into real phone calls to real people, and Autocalls AI validates the channel, the schedule and the balance at exactly that point. If the balance covers only part of the queue, the campaign does not fail cleanly; it works its way down the list and stops somewhere in the middle, leaving half a segment called and half untouched with no record of where the line fell. So the agent assembles everything and stops before starting: "Q3 Outbound is loaded with 1,840 leads. Account balance is 412 USD. The last run averaged 0.31 USD per completed call. 63 leads were rejected because their local time falls outside the campaign's Monday to Friday 9am to 6pm window. Start the campaign now, trim to the top 1,300, or hold until the balance is topped up?" The outbound owner answers in the channel they already work in, and the agent starts the campaign or does not. This is human-in-the-loop placed on the spend, not on the paperwork.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

21 actions

Calls

Make Call Places an outbound phone call to a given number using the selected assistant. Custom variables passed here are substituted into the assistant's prompt and welcome message and must match the variables defined on that assistant. The response confirms only that the call was initiated, so use List Calls filtered by client phone number to locate the resulting record, its status, transcript and recording.
List Calls Returns a paginated list of calls, each with status, direction, duration, transcript, recording URL, cost breakdown, extracted evaluation data and who answered. Narrow by status, direction, client phone number, assistant, campaign and created date range.
Get Call Retrieves a single call by ID with the full record, including the variables passed in, the evaluation data the assistant extracted, carrier and total cost, who answered and the recording URL.
Delete Call Permanently deletes a call and everything attached to it, including its transcript, recording and metadata. The action is irreversible, so treat it as a records decision rather than cleanup.

Campaigns

Create Campaign Creates a calling campaign, which starts in draft status. A call campaign requires an outbound assistant. Schedule windows, allowed weekdays, retry policy and parallel call limits control when and how leads are contacted.
List Campaigns Returns every campaign on the account with its channel, current status, assistant, timezone, schedule windows, allowed days, retry policy, assigned phone numbers and fallback configuration.
Get Campaign Retrieves a single campaign by ID with its full configuration, including the schedule and retry settings a flow needs to validate leads against before adding them.
Update Campaign Status Starts or stops a campaign. Starting validates the channel configuration, the schedule and the account balance before the campaign begins contacting its leads. Stopping halts further contact attempts.
Delete Campaign Deletes a campaign. A running campaign is stopped automatically first, every lead attached to it is removed, and the phone numbers assigned to it are released back to the account.

Leads

Create Lead Adds a lead to a calling campaign so the campaign contacts that number when it runs. Variables supplied here are used by the assistant during the call. Secondary contacts add extra numbers for the same lead on call campaigns.
List Leads Returns a paginated list of leads with phone number, variables, current status, campaign and any secondary contacts. Filter by status, campaign, partial phone number and created date range. There is no single lead endpoint, so this list is also how one lead is retrieved.
Update Lead Updates a lead, changing only the fields supplied. The lead can be moved to another campaign, its number corrected, or its status set to Created, Completed or Reached Max Retries. Variables are merged with the lead's existing variables rather than replacing them.
Delete Lead Deletes a lead from its campaign so it is no longer contacted. Calls already placed to that lead remain on the account.

Assistants and Voices

List Assistants Returns a paginated list of every assistant on the account, inbound and outbound, with its voice, language, mode, status, prompts, timezone, post call schema and webhook settings.
List Outbound Assistants Returns every outbound assistant as a single array. These are the assistants that can place calls and the only ones a call campaign accepts.
List Assistant Phone Numbers Returns the phone numbers that can be assigned to an assistant, each with its country code, type label and availability, narrowable to inbound or outbound suitability.
List Voices Returns the speech voices available to the account with language, gender, accent, age and a preview URL, filterable by engine mode, language, synthesizer provider, gender, age and accent.
List Languages Returns every language an assistant can speak with its numeric ID, display name and ISO 639-1 code. The IDs are what the voice catalogue filters on.
List Models Returns the language models available to assistants, selectable by pipeline, multimodal or dualplex mode.

Account

List Phone Numbers Returns every phone number owned by the account with its nickname, country code, type, region, SMS capability and subscription status. These IDs are what a campaign uses for its outbound from numbers.
Get Current User Returns the account the API key authenticates as, with its name, email address and current balance in USD. Used as a connection check and as the balance guard before a campaign is allowed to start.

Triggers

1 triggers

Event Triggers

On Call Ended Fires when a call finishes on the account. Used to read the transcript and extracted evaluation data, route the outcome to the CRM or a person, and decide whether the lead belongs in the retry path or out of it entirely.

Frequently Asked Questions

What can FlowRunner do with Autocalls AI?

FlowRunner agents can run Make Call, List Calls, and Get Call in Autocalls AI, plus 18 more actions.

Does connecting Autocalls AI to FlowRunner require OAuth?

No. Autocalls AI connects to FlowRunner with an API key, no OAuth flow required.

Can Autocalls AI trigger a FlowRunner workflow automatically?

Yes. Autocalls AI supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Autocalls AI

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us