Rich call data in every scenario.
Each finished Bland call arrives with its transcript, summary, extracted variables, and disposition, produced on Bland's own self-hosted stack.
Bland + Make
Send every Bland call into a Make scenario with signed webhooks, then route transcripts and outcomes visually, or start AI phone calls from a scenario.
What Bland does inside Make.
Calls arrive as scenario bundles.
Point a post-call webhook at a Make custom webhook. Each finished call starts the scenario with its transcript, summary, variables, and disposition.
Route by outcome.
Use pathway_tags, disposition, or any extracted variable to send booked calls one way and callbacks another inside the scenario.
Scenarios that place calls.
An HTTP module can POST to Bland's Send Call endpoint, passing request_data and metadata that come back on the post-call webhook.
Triggered by more than call end.
Bland triggers can post to a Make webhook on voicemail detected, transfer started, SMS received, batch completed, eval completed, and more.
Filtered before Make sees it.
Add conditions to a Bland trigger so only calls that match, like a given disposition, reach the scenario and use operations.
How it deploys.
Create a Make scenario with a custom webhook trigger and copy its URL.
Paste the URL as the webhook on your Bland inbound number, or pass it as webhook on outbound call requests.
Place a test call so Make can read the payload structure, then map fields into downstream modules.
Test by completing a call and confirming the scenario runs.
Our FDE team scopes the integration, maps Bland to your stack, and stays on through go-live. Enterprise deployments go live in 30 days.
Drop Bland into your editor.
MCP server runs in Claude Code, Cursor, and any MCP-aware editor. Or hit the REST API directly.
curl -X POST https://api.bland.ai/v1/calls \
-H "Authorization: $BLAND_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"phone_number": "+14155552120",
"task": "Qualify refi lead",
"voice": "june"
}'
Frequently asked questions.
How do I connect Bland to Make?
Through webhooks, which work with any scenario. Create a custom webhook in Make, set its URL as the post-call webhook on your Bland number or call request, and every finished call starts the scenario with the transcript, summary, and variables.
Can a Make scenario start an AI phone call?
Yes. Add an HTTP module that POSTs to Bland's Send Call API with your API key, the phone number, and a task or pathway ID. Pass request_data for context and metadata to tag the call for later routing.
How do I route different call outcomes in Make?
Branch on fields in the post-call payload, such as disposition_tag, pathway_tags, or extracted variables. Or filter earlier with a Bland trigger whose conditions decide which calls reach the scenario at all.
Can I pass my own IDs through the call?
Yes. Put your record ID or campaign name in metadata on the Send Call request. Bland returns that metadata in the post-call webhook, so the scenario can match the result back to the right record.
How do I know a webhook really came from Bland?
Create a webhook signing secret in Bland. Each webhook then carries an HMAC SHA-256 signature of the body in the X-Webhook-Signature header, which you can recompute and compare before the scenario acts.
Related integrations.
See every integration on the integrations hub.
With our team
Our FDE team scopes the integration with you.
They map Bland to your stack, design the rollout, and stay on through go-live. Enterprise deployments go live in 30 days.
On your own
Or drop Bland into your editor.
The Bland MCP server runs in Claude Code, Cursor, and any MCP-aware editor. Or hit the REST API directly. Free sandbox, no credit card.