Bland AI
CommunicationDispatch autonomous AI phone agents with Bland AI. Agents place real outbound calls from a plain-language objective or a pre-built pathway, then collect transcripts, recordings, summaries, and structured answers, with stop controls for in-flight calls.
What This Integration Enables
The phone is the most invasive channel automation can touch: it rings in someone's pocket. Bland AI hands agents that channel for real, autonomous voice agents that dial actual numbers, hold conversations from a plain-language task or a deterministic pathway, transfer to humans, and come back with transcripts, recordings, and extracted answers. FlowRunner's contribution is the governance that makes this power deployable: consent checks before dispatch, human approval of lists and scripts, and stop controls wired as first-class workflow steps. - Outbound at scale: confirmations, reminders, follow-up surveys, and status calls driven by live data from your systems - Deterministic conversations: pathways built in the Bland dashboard give branching logic instead of prompt roulette, inspected with Get Pathway before anything dials - Structured outcomes: Analyze Call turns transcripts into typed answers ready for CRM fields and routing decisions - Full auditability: per-call transcripts, recordings stored to FlowRunner file storage, and price per call for QA and spend reviews Every call is real, billed by the minute, and aimed at a human being. That is why the dispatch decision, whom to call, with what script, in what window, belongs to a person through a [human-in-the-loop](/concepts/human-in-the-loop) gate, and the agent handles everything on either side of it.
Without FlowRunner
With FlowRunner
Use Case Scenarios
No-show rates meet an approved calling program
A clinic's booking sheet in [Google Sheets](/integrations/google-sheets) feeds tomorrow's confirmation run. The agent builds the list, drops rows without consent flags, and presents the batch for approval with the pathway named. After sign-off, Send Call works the list with each patient's name and slot injected as variables, Analyze Call extracts confirmed or reschedule per call, and the agent writes outcomes back to the sheet. Reschedule requests route to the front desk through [Slack](/integrations/slack) with the transcript excerpt attached, so the human callback starts with context instead of a cold redial.
Lead qualification that writes its own CRM fields
New inbound leads from the website land in [HubSpot](/integrations/hubspot). Within the approved calling window, the agent dispatches a qualification call from the vetted pathway: company size, timeline, budget authority. Analyze Call returns the answers as typed fields, and the agent updates the contact record and routes qualified leads to a rep's queue. Calls answered by voicemail get one scripted message and a follow-up task instead of a redial loop. The rep opens each qualified lead with a transcript, a summary, and a recording URL already on the record.
QA and spend review across every call the account makes
On a nightly schedule, the agent runs List Calls for the day, pulls Get Call Details for each completed call, and files transcripts and summaries. Get Call Recording stores audio for the calls flagged by outcome or duration, and the QA sheet gets a row per call with answered_by, duration, and price. Calls that ended in transfer or ran past the expected length surface for human review. The weekly report shows cost per confirmed outcome by campaign, which is the number that decides whether a calling program expands.
Human-in-Loop Highlight
Send Call is not a draft, a preview, or a simulation: the moment it is queued, a real phone rings on the public network, per-minute credits start burning, and whatever the agent says lands in a customer's ear under your company's name. A bad list dispatched at machine speed is a hundred wrong calls before a human notices, with regulatory exposure attached where consent rules apply. So in FlowRunner, no call list dials itself. The agent assembles the batch, verifies consent flags and calling windows, names the pathway, and estimates the spend; a person approves the run. The stop controls are wired into the same workflows: Stop Call kills a runaway call mid-sentence, and Stop All Calls, the account-wide kill switch that terminates every active call on the API key, is itself a deliberate human action, not an automated reflex.
Agent Capabilities
11 actionsCalls
6- Send Call Dispatches an autonomous AI voice agent to place a real outbound call, driven by a natural-language Task or a Pathway ID, with chosen voice and language, greeting detection, human transfer, voicemail handling, and webhook results. Returns a call ID immediately while the call runs. Real numbers, real per-minute billing: the action this page's human gate exists for.
- Get Call Details Retrieves the complete call record: statuses, per-utterance and concatenated transcript, AI summary, corrected duration, answered_by, recording URL, transfer details, pathway logs, captured variables, and price in USD.
- List Calls Lists call metadata newest first, filterable by date range, number, completion state, answered_by, batch, and campaign, with a total count for the filter.
- Get Call Recording Downloads a completed call's audio into FlowRunner file storage as MP3 or WAV and returns a shareable URL. Only for calls dispatched with recording enabled.
- Stop Call Immediately ends one in-progress call or cancels a scheduled one. Billing stops when the call ends, making this the fastest brake on a mistake.
- Stop All Calls Ends every active call on the account and reports how many were cancelled. An account-wide emergency stop that reaches calls from every flow and campaign on the key, used deliberately.
Analysis
1- Analyze Call Runs AI analysis over a completed transcript, answering your questions with typed answers in order, null where the transcript cannot support one. The bridge from conversation to CRM fields and routing decisions. Consumes credits by transcript length and question count.
Pathways
2- List Pathways Lists every conversational pathway with its name, description, and full node-and-edge graph, the source of Pathway IDs for Send Call.
- Get Pathway Retrieves one pathway's complete graph, so a human can inspect exactly how the agent will branch before any call dials against it.
Voices
1- List Voices Lists every available voice, curated, cloned, and public catalog, with IDs, descriptions, tags, engine, and ratings, for picking and auditing what your agents sound like.
Phone Numbers
1- List Inbound Numbers Lists purchased inbound numbers with their full configuration: answering prompt, webhook, voice, first sentence, transfer number, recording flag, and maximum duration.
Frequently Asked Questions
What can FlowRunner do with Bland AI?
FlowRunner agents can run Send Call, Get Call Details, and List Calls in Bland AI, plus 8 more actions.
Does connecting Bland AI to FlowRunner require OAuth?
No. Bland AI connects to FlowRunner with an API key, no OAuth flow required.
Can Bland AI trigger a FlowRunner workflow automatically?
Bland AI doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Bland AI
$100 in credits. No card required. Connect in minutes.