FlowRunner
PricingContact
Theme
Start Free

PreCallAI

Voice & Telephony

Place outbound AI sales calls with PreCallAI and manage the assistants, dialers, contact segments, and campaigns behind them. Agents qualify at volume and pass live interest to a person.

22 actions API key available
PreCallAI website ↗ Platform Documentation ↗ Capability data verified 2026-08-01
A nightly CRM sync flags pipeline that has gone quiet past a threshold
Agent pulls each record's job title, lifecycle stage and lead status to carry as call context
Agent stages the list with Create Segment and Bulk Upload Segment Contacts
Agent reads back the script with Get Assistants and the trunk credentials with Get Dialers
Agent compares the staged segment against Get Call History to drop anyone already reached
Agent posts the segment size, the assistant script and the exact trunk the calls will leave from
The sales lead authorizes the campaign, and only then does the agent run Create Campaign

What This Integration Enables

PreCallAI separates the AI caller from the phone line, and that split is the reason to care about it. The assistant carries the direction, language, voice, conversation script and post-call analysis prompts. The dialer carries the telephony credentials, and it can be backed by Twilio, Telnyx or your own SIP trunk. If you already own your carrier relationship and your number reputation, this is the shape you want, because the AI vendor never becomes your phone company.

FlowRunner agents work all four layers. They create and tune assistants, register and rotate dialers, and build contact segments from live pipeline data. They then read back per-contact results carrying status, duration, sentiment, transcript, recording URL, and flags for whether the call was transferred, a meeting was scheduled or a message was sent. Those connectors turn a calling platform into a step inside a larger flow rather than a destination you export to. The agent qualifies at volume, and the moment a call shows real interest, a person takes it.

Without FlowRunner

List built by hand Someone exports a CRM view to a spreadsheet and uploads it, then does it again next week
Script drift The assistant's prompt was last read by whoever created it, months ago
Carrier risk is invisible Nobody checks which trunk a campaign will dial from until the number reputation drops

With FlowRunner

List assembled from live pipeline Segments are built from current CRM state and deduplicated against prior call history
Script read before the launch The prompt and the dialer are surfaced to a person in the same message as the audience size
Dialing authorized, not assumed A campaign is created only after a named person signs off on it

Use Case Scenarios

Dormant pipeline, worked without a list-building week

Deals that stalled past a threshold are the classic candidate for AI calling and the classic reason nobody does it, because assembling the list takes longer than the calls save. An agent removes that friction. It queries HubSpot or Pipedrive for the qualifying records, runs Create Segment to stage a named list, and pushes the contacts in with Bulk Upload Segment Contacts, carrying job title, lifecycle stage and lead status through as context the assistant can use on the call. The list is current every time it runs because it is built from the CRM rather than from last month's export.

Interest routed to a person while it is still warm

After a campaign runs, Get Campaign Contact List returns each contact's outcome: status, duration, sentiment, transcript, recording URL, and whether the call was transferred, a meeting scheduled or a message sent. The agent splits that list three ways. Meetings booked go straight to the owning rep's calendar. Positive sentiment with no meeting goes to Slack as a callback task with the transcript attached, because a summary of a good call is worth more than a dashboard tile. Everything else updates the CRM record and stops. The rep spends their day on conversations a machine already established were worth having.

Trunk rotation and a script change that does not break the campaign

Number reputation degrades, and the fix is to move traffic. The agent registers a fresh trunk with Create Dialer, supplying the account SID and auth token for Twilio or the credentials for Telnyx, which does not require an auth token, or the termination URI and trunk credentials for a raw SIP connection. Update Assistant applies a partial script change without rebuilding the configuration, so a single sentence can be corrected without touching the voice or the model settings. Delete Dialer and Delete Assistant are the operations that stay behind a person, because campaigns still referencing a deleted dialer or assistant simply lose the ability to place calls.

Human-in-Loop Highlight

Create Campaign carries the gate here, and it carries it because of what is missing from the action list rather than what is in it. A PreCallAI campaign dials every contact in its segment using the chosen assistant and dialer, and with automation enabled it runs without a manual start. There is no pause, no stop and no cancel for a running campaign here. Delete Segment removes the contacts, but a campaign pointed at a deleted segment loses its list rather than stopping cleanly. The review therefore has to happen before creation, not after, and an agent that understands its own connector knows that.

So the agent builds everything and stops one step short. It posts to the sales lead: "Campaign 'Q3 dormant pipeline' is staged against segment 'No reply 30d', 412 contacts, deduplicated against 68 already called this quarter. Assistant is 'Ava, outbound qualifier', opening line and script below. Dialer is the Telnyx trunk ending 4471. There is no stop control once this is created. Create it?" The lead reads the script, cuts 30 contacts they know are in active negotiation, and approves. The agent runs Create Campaign against the corrected segment. This is the human-in-the-loop pattern doing its actual job, which is not adding a checkbox to a workflow but placing the decision at the last moment it can still be made.

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

22 actions

Calls

2
  • Place Call Places an outbound call to one or more numbers using the selected assistant and dialer. Recipient details supplied here are passed to the assistant as call context, and numbers are submitted as an array so one request can target several destinations.
  • Get Call History Returns the history of calls placed through the playground endpoint, each entry reporting the recipient along with the assistant and dialer that handled it. Used to deduplicate a new segment against contacts already reached.

Campaigns

3
  • Get Campaigns Returns every campaign the account can access, including the assistant, contact segment and dialer bound to each one and whether it has started.
  • Create Campaign Creates a campaign that dials every contact in the selected segment using the chosen assistant and dialer. A scheduled date starts it later, and automation lets PreCallAI run it without a manual start. Flows gate this behind an approval because the connector exposes no stop control once a campaign is running.
  • Get Campaign Contact List Returns the contacts a campaign dialed with the result of each call: status, duration, sentiment, transcript, recording URL, and whether the call was transferred, a meeting was scheduled or a message was sent. This is the action that turns a campaign into routable work.

Assistants

4
  • Get Assistants Returns every AI assistant on the account with its direction, language, voice, script, model settings and post-call analysis prompts. Used to surface the exact wording to a reviewer before a campaign is created.
  • Create Assistant Creates a calling assistant with its direction, language, voice, conversation script and behaviour settings. PreCallAI documents more fields as required than are marked required here, so supply the optional voice, model and prompt fields as well if the API rejects a minimal payload.
  • Update Assistant Applies a partial update to an assistant. Only the fields supplied are sent, so a single line of script can change without disturbing the voice or model settings.
  • Delete Assistant Permanently deletes an assistant. Campaigns still referencing it can no longer place calls, so flows confirm nothing depends on it first.

Dialers

4
  • Get Dialers Returns every dialer on the account. A dialer carries the telephony credentials PreCallAI dials with, backed by Twilio, Telnyx or a SIP trunk.
  • Create Dialer Registers a telephony dialer. Twilio requires the account SID and auth token, Telnyx does not require an auth token, and SIP requires the termination URI plus trunk credentials. Used to rotate traffic onto a fresh trunk.
  • Update Dialer Updates the credentials or settings of an existing dialer. Only supplied fields are sent.
  • Delete Dialer Permanently deletes a dialer. Campaigns and calls still referencing it can no longer place calls through it.

Segments

4
  • Get Segments Returns every contact segment on the account. A segment is the named list a campaign dials through.
  • Create Segment Creates a segment that groups contacts for campaign dialing. Contacts are added afterwards with Create Segment Contact or Bulk Upload Segment Contacts.
  • Update Segment Updates the name or description of a segment. Only supplied fields are sent.
  • Delete Segment Permanently deletes a segment. Campaigns still referencing it no longer have a contact list to dial.

Segment Contacts

5
  • Get Segment Contacts Returns every contact in a segment, including name, email, phone number and the source it was synced from. Used to read a list back before it is dialed.
  • Create Segment Contact Adds a single contact to a segment. Job title, lifecycle stage and lead status are stored alongside the contact and used as call context.
  • Update Segment Contact Updates a contact stored in a segment. Only supplied fields are sent.
  • Delete Segment Contact Permanently removes one contact from a segment so campaigns dialing it no longer call them.
  • Bulk Upload Segment Contacts Uploads a batch of contacts into a segment in one request. PreCallAI documents the response but not the request payload format, so supply the payload the dashboard's bulk upload produces for your account.

Frequently Asked Questions

What can FlowRunner do with PreCallAI?

FlowRunner agents can run Place Call, Get Call History, and Get Campaigns in PreCallAI, plus 19 more actions.

Does connecting PreCallAI to FlowRunner require OAuth?

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

Can PreCallAI trigger a FlowRunner workflow automatically?

PreCallAI doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with PreCallAI

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