Resources · Make integration

Bland Make integrationAutomate Bland with Make.

What happens after your AI agent hangs up? The Bland Make integration gives you 12 modules to place calls, fetch transcripts and recordings, and react the moment a call ends. This guide connects your account and walks you through a first scenario.

Try the Bland integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Bland Make integration do for you?

The Bland Make integration links your Bland account to Make, a no-code tool where you build a scenario (the automation itself, a chain of modules). Make can start a call from Bland, wait for one to finish, then send the transcript, the recording or an analysis to the rest of your stack.

Call every new lead without lifting the phone. A form from another app starts the scenario, and Send a Call dispatches your Bland agent. When the job is short and you do not need extra settings, Send a simple Call does the same with less to fill in, and Send a simple Call using Pathways follows a conversation flow you already designed in Bland.

Keep your CRM in sync after every conversation. Watch Outbound Phone Calls fires once a call you placed is over. Chain Get a Call Details to pull the transcript, then write it to your contact record. A support desk can do the same with Watch Incoming Phone Calls for calls that come in.

Turn each call into a clear verdict. Analyze a Call checks a finished call against the questions and goals you set, so a sales manager sees at a glance whether the prospect agreed to a meeting. Get an Audio Recording keeps the audio for quality review.

The integration stops at these 12 modules. For anything else in Bland, Make an API Call reuses your connection. Before you build, the Make review sums up the tool, Make pricing explains how operations are counted, and if you also look at the other option, n8n vs Make sets the two side by side.

Connect

How do you connect your Bland account to Make?

  1. 01

    Copy your API key from Bland

    You need an active Bland account and a valid API key. Log in to Bland AI, open the organization portal and find your API key there. Keep it at hand: Make asks for it once, then every Bland module reuses that connection.

  2. 02

    Add a Bland module and open the connection window

    In your Make account, add any Bland module to your scenario and click Create a connection. If you picked one of the two watch modules, which carry an instant tag, click Create a webhook first, then Create a connection.

  3. 03

    Name the connection and paste the key

    The Connection name field is optional, but a clear name helps when you run several Bland accounts. Paste the API key you copied, or follow the instructions on screen, and save. Make now lists what it can read from your account.

First scenario

Your first scenario: log and score every outbound call

GoalWhen an outbound call ends in Bland, Make pulls its transcript and analyzes whether the call reached its goal.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to add the first module. Search for Bland by name.

  2. 02

    Set the trigger

    Pick Watch Outbound Phone Calls, click Create a webhook, then Create a connection and paste your API key. This module waits for Bland to report a finished call.

  3. 03

    Fetch the transcript

    Click the + on the right of the trigger and add Get a Call Details. Map the call from the trigger into it, so Make knows which conversation to read.

  4. 04

    Add the analysis

    Add Analyze a Call after it, map the same call and write the questions and goals that matter to you, for example whether the contact accepted a demo.

  5. 05

    Test with Run once

    Click Run once, then let an outbound call finish in Bland. Open each module and read the bundles it received: the transcript and the answers to your questions should appear there.

  6. 06

    Switch it on

    When the test looks right, switch the scenario on. From now on, each outbound call that ends in Bland flows through the three modules without any manual step.

Triggers

Which Bland events can start a scenario?

2 modules start a scenario when something happens in Bland. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Bland as soon as it happens.

Bland1Watch Incoming Phone Calls

Watch Incoming Phone Calls

Instant trigger

In Make“Triggers when an incoming phone call has finished.”

This trigger starts your scenario each time an incoming call on your Bland account has finished, so the follow-up happens while the caller still remembers the conversation. It is an instant trigger: nothing is polled, Bland pushes the event to Make.

How it fires
instant, Bland calls Make through a webhook as soon as the incoming call is over, which is why the module shows a lightning badge.
When to use it
your AI agent answers a support or booking line and you want every call summarized in your helpdesk or posted to your team.
Watch out
create the webhook before the connection, and add Get a Call Details after it when you need the full transcript.
Bland2Watch Outbound Phone Calls

Watch Outbound Phone Calls

Instant trigger

In Make“Triggers when an outbound phone call is finished.”

Here the starting point is the other direction: a call your Bland agent placed has ended, and the scenario picks up the result right away. It pairs naturally with the Send modules, which place the call, while this one closes the loop.

How it fires
instant, Bland notifies Make through a webhook the moment the outbound call finishes, with no schedule to set.
When to use it
a sales team calls new leads with Bland and wants the outcome written back to the CRM or sent as a follow-up email.
Watch out
create the webhook before the connection, and add a filter after the trigger if only some of your outbound calls should go further.
Modules

What can Bland do inside a scenario?

Bland gives you 10 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Bland1

Analyze a Call

Action

In Make“Analyzes a call based on questions and goals.”

You get a structured read of a finished conversation: Bland reviews the call against the questions and goals you give it and returns the answers to Make, ready to route or store.

When to use it
a qualification call ended and you want to know whether the prospect has budget before anyone on your team reads the transcript.
Watch out
the analysis is only as useful as your questions, so keep them short and answerable from what was said.
Bland2

Get a Call Details

Action

In Make“Retrieves detailed information and the transcript of a call.”

This one hands you everything Bland knows about a single call, including its full transcript, so the next modules can copy it into a CRM note, a document or a message.

When to use it
right after a watch trigger, when a manager wants the written conversation attached to the contact without opening Bland.
Watch out
it reads one call at a time; to go through several, start with List Calls.
Bland3

Get an Audio Recording

Action

In Make“Retrieves the call's audio file, if it exists.”

Retrieve the audio file of a call so you can archive it in your storage app or share it with a coach. The file only comes back when a recording exists for that call.

When to use it
a quality reviewer listens to disputed calls and needs the audio saved next to the customer record.
Watch out
on the Free plan Make handles files up to 5 MB, so check the size of long recordings before you store them.
Bland4

Make an API Call

Action

In Make“Performs an arbitrary authorized API Call.”

When none of the other modules does what you need, this one lets you call any endpoint of the Bland API from your scenario, with the same connection and no new key to paste.

When to use it
you found a Bland feature in their API reference that has no dedicated module in Make yet.
Watch out
you write the request yourself, so keep the Bland API documentation open while you set it up.
Bland5

Send a Call

Action

In Make“Sends an AI phone call.”

Your AI agent picks up the phone for you: this module places an outbound call from Bland with the full set of options the module offers, straight from your scenario.

When to use it
a new lead lands in your form tool and your team wants Bland to call back while the interest is fresh, with the call tuned to that campaign.
Watch out
each run places a real call, so test with your own number before switching the scenario on.
Bland6

Send a simple Call

Action

In Make“Sends a simple call. Without a lot of settings.”

The quick version of Send a Call: fewer settings to fill in, so a first automated call is up and running with little setup.

When to use it
a reminder or confirmation call where the message is short and you do not need the advanced options.
Watch out
if you later need finer control over the call, switch to Send a Call rather than stacking workarounds around this one.
Bland7

Send a simple Call using Pathways

Action

In Make“Sends a simple call without a lot of settings using Pathways.”

Launch a call that follows a Pathway, the conversation flow you drew in Bland, while keeping the light setup of the simple call module.

When to use it
your team already built a branching script in Bland, for booking or screening, and wants Make to start it whenever a new request arrives.
Watch out
the Pathway has to exist in Bland first, since this module starts it and does not create it.
Bland8

Stop an Active Call

Action

In Make“Stops an active call.”

End a call that is still in progress, from a scenario, without anyone logging into Bland to hang up by hand.

When to use it
the contact replied by email or booked through your site during the call attempt, and another app tells Make the call is no longer needed.
Watch out
the conversation stops for the person on the line too, so trigger it on a clear signal and never on a guess.
Bland9

List Calls

Search

In Make“Returns a list of calls.”

Pull a list of your Bland calls into Make. It is a search, so it may find nothing, one call or many. Each module placed after it then runs once for every call it found.

When to use it
calls already happened before you linked Bland to Make, and you want that history in a spreadsheet so the team can sort it.
Watch out
every call returned costs an operation in each module after it, so narrow the list before you chain heavy steps.
Bland10

List Voices

Search

In Make“Lists available voices.”

See which voices your Bland account offers, straight inside Make, so you can pick the right one or store the list for your team.

When to use it
a marketer tests different voices per campaign and wants the available options in a shared table before choosing.
Watch out
it returns several bundles, one per voice, so add a filter or an aggregator if you only need a single value downstream.
Need help

Need help automating Bland with Make?

A person reads every message.

FAQ

Bland and Make: common questions

01Is the Bland Make integration free?
Yes, on the Make side. Bland is a standard app, so its modules are available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module per bundle. Your Bland account and its own billing are separate from Make.
02What do you need to connect Bland to Make?
An active Bland account and a valid API key. You find the key by logging in to Bland AI and opening the organization portal. In Make, add a Bland module, click Create a connection, give it a name if you like, and paste the key. For the two watch modules, which are instant, click Create a webhook first and then Create a connection. The connection is created once and reused by every Bland module in your scenarios, so there is nothing to repeat later.
03Do Bland triggers in Make fire in real time?
Yes. Both Bland triggers, Watch Incoming Phone Calls and Watch Outbound Phone Calls, are instant: Bland calls Make through a webhook as soon as a call has finished, and the module shows a lightning badge. You do not wait for a polling interval, unlike scheduled triggers, which Make checks on the scenario schedule (every 15 minutes by default). The event arrives when the call ends, not while it is in progress, so your scenario always works on a completed conversation.
04What if a Bland module is missing in Make?
Use Make an API Call. The integration ships 12 modules, and this one reaches any endpoint of the Bland API with the same connection, so you are not stuck when a feature has no dedicated module. You write the request yourself, which means keeping the Bland API documentation open. The Make documentation for Bland also notes that its content is AI-generated from the vendor docs and may contain errors, so check anything critical with Bland directly before you rely on it.
05Should you use Make or n8n for Bland?
It depends on where your team already builds. This page covers Make, where Bland comes with 12 modules, including two instant triggers and a Make an API Call module for anything else. The same app often has a node in n8n too, so if your automations already live there, check its catalog before switching tools. Neither choice changes how Bland places or analyzes calls. Pick the tool your team knows, and compare both on your own use case rather than on general claims.
Same platform

Other docs you might need on this stack.

Browse all integrations