Resources · Make integration

OpenPhone Make integrationAutomate OpenPhone with Make.

What if every call and text in OpenPhone could start the next task for you? The OpenPhone Make integration offers 18 modules: 4 instant triggers, 9 actions and 5 searches. This guide shows how to link your account, then walks you through a first working scenario.

Try the OpenPhone integration on MakeSee the 18 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the OpenPhone Make integration do for you?

The OpenPhone Make integration links your business phone account to Make, a visual automation tool. You build a scenario (the automation itself, a chain of bricks called modules) that reacts to calls, summaries, transcripts and texts, or that creates contacts and sends SMS for you. No code is needed.

Keep your CRM in step with the phone. Watch New Calls and Recordings fires when a call rings or ends. Pair it with Get a Contact to see who called, or with Create a Contact when the number is new to you.

Turn conversations into notes someone will read. Once OpenPhone finishes a summary or a transcript, Watch New Call Summaries or Watch New Call Transcripts hands it to Make, ready to post in a team channel or attach to a deal.

Answer leads by text. A form submission in another app can end with Send a Text Message (SMS), so the prospect hears from your number while the request is still fresh.

A few limits to know first. The OpenPhone modules require a paid OpenPhone account. The documentation gives no numeric limits, so plan your tests with Run once rather than assumptions. For an outside view of the platform, read the Make review, and check Make pricing before you count operations. Weighing another tool? The n8n vs Make comparison lays out the criteria side by side.

Connect

How do you connect OpenPhone to Make?

  1. 01

    Generate an API key in OpenPhone

    Log in to OpenPhone, open the workspace settings and go to the API tab. Click Generate API key, give it a label you will recognize later, then copy the value and keep it somewhere safe.

  2. 02

    Open the connection window in Make

    In your scenario, add any OpenPhone module and click Create a connection. The Connection name field is optional, but a clear name helps when several teammates share the same Make organization.

  3. 03

    Paste the key and save

    Paste the key into the OpenPhone API Key field and click Save. If a window asks you to authenticate, confirm access. Every OpenPhone module in your scenarios reuses this connection from then on.

First scenario

Build your first scenario: text every new lead

GoalWhen a lead fills in a form in another app, Make adds the person to OpenPhone and sends them a text from your number.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module: the trigger of the app where your leads arrive, such as your form tool.

  2. 02

    Add Create a Contact

    Click the + on the right of that module, search for OpenPhone and pick Create a Contact. Choose your connection, or click Create a connection if this is your first OpenPhone module.

  3. 03

    Map the lead into the contact

    Fill the contact fields with data from the form module. Make shows the items the previous module produced, so you click them instead of typing values by hand.

  4. 04

    Add Send a Text Message (SMS)

    Add one more OpenPhone module, Send a Text Message (SMS). Write a short welcome and map the phone number coming from the form, so each new lead gets their own text.

  5. 05

    Test with Run once

    Click Run once, submit a test entry in your form, then open each module to read the bundles it received. A bundle is one item passing through, here one lead.

  6. 06

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. From now on, each lead lands in OpenPhone with a text already sent.

Triggers

The four OpenPhone triggers

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

OpenPhone1Watch New Calls and Recordings

Watch New Calls and Recordings

Instant trigger

In Make“Triggers for new calls that have been completed or are ringing.”

This trigger starts your scenario the moment a call on your OpenPhone line is ringing or has been completed, so the rest of your stack learns about the call without anyone copying it over.

How it fires
instant, OpenPhone calls Make through a webhook as soon as it happens (the lightning badge on the module).
When to use it
log every inbound call against the right record in your CRM, or alert a teammate when a key customer rings.
Watch out
ringing and completed calls both start the scenario, so design the next modules to handle either case.
OpenPhone2Watch New Call Summaries

Watch New Call Summaries

Instant trigger

In Make“Triggers when a new call summary is done.”

You get a ready-made recap of each conversation pushed into Make as soon as OpenPhone finishes writing it, which saves you from replaying the recording to know what was agreed.

How it fires
instant, OpenPhone notifies Make through a webhook once the summary is done.
When to use it
a sales rep closes a discovery call and the summary should appear on the matching deal or in the team channel.
Watch out
this fires on the summary, not on the call itself, so it will not see calls that never get a summary.
OpenPhone3Watch New Call Transcripts

Watch New Call Transcripts

Instant trigger

In Make“Triggers for newly completed transcripts.”

Full written versions of your calls reach Make through this trigger, which is handy when you need every word rather than a recap, for quality review or for searching old conversations later.

How it fires
instant, OpenPhone sends each completed transcript to Make by webhook as soon as it exists.
When to use it
archive support calls in a document store where the team can search them by keyword.
Watch out
every module that handles a transcript uses one operation, so keep the chain after this trigger short.
OpenPhone4Watch New Messages

Watch New Messages

Instant trigger

In Make“Triggers for new delivered or received messages.”

Every text your OpenPhone numbers deliver or receive can start a scenario with this trigger, giving you a way to route SMS conversations wherever your team actually works.

How it fires
instant, OpenPhone tells Make through a webhook as soon as a message is delivered or received.
When to use it
copy incoming customer texts into a helpdesk queue so nobody has to watch the phone app.
Watch out
your own outgoing texts count too; if the scenario also sends SMS, make sure it cannot end up answering its own messages.
Modules

What the OpenPhone modules can do

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

OpenPhone1

Create a Contact

Action

In Make“Creates a new contact.”

New people become OpenPhone contacts without anyone typing their details, so the next call from them shows a name instead of a bare number.

When to use it
right after a signup, a booking or a form entry in another app, before you text or call the person.
Watch out
run Get a Contact or your own check first if the same person may come in twice.
OpenPhone2

Delete a Contact

Action

In Make“Deletes a contact.”

Removing a contact from a scenario keeps your OpenPhone address book in line with the system you treat as the source of truth, such as a CRM where records get archived.

When to use it
when a customer asks to be forgotten or a record is merged elsewhere.
Watch out
deleting is the whole point here, so point it at a dummy contact during your Run once test, never a real customer.
OpenPhone3

Get a Call Summary

Action

In Make“Retrieves the summary of a call.”

Fetching the summary of one specific call gives you the recap on demand, for example later in a scenario that started from something else than the summary trigger.

When to use it
after Watch New Calls and Recordings or Search Calls, when you already know which call matters and want its recap attached to a ticket.
Watch out
it reads one call per operation, so avoid running it on long lists.
OpenPhone4

Get a Call Transcript

Action

In Make“Retrieves the transcript of a call.”

Pulling the transcript of a single call puts the full wording of that conversation into your scenario, ready to store, quote or pass to another tool for analysis.

When to use it
a manager flags a call for review and the transcript should land in the coaching document.
Watch out
pick Get a Call Summary instead when a short recap is enough for the people who will read it.
OpenPhone5

Get a Contact

Action

In Make“Retrieves information about a contact.”

Looking up one contact returns what OpenPhone knows about that person, which lets later modules personalize a text or update the matching record elsewhere.

When to use it
when a call or message arrives and you need the caller's details before deciding what happens next.
Watch out
it targets a single contact you already identify; to browse several, a search module is the better fit.
OpenPhone6

Get a Text Message

Action

In Make“Retrieves information about a text message.”

This action reads back one text message in detail, so a scenario can work on the exact content and context of an SMS instead of a shortened notification.

When to use it
a teammate references a message in a ticket and you want the full text copied next to it.
Watch out
for new messages as they happen, Watch New Messages already delivers them; this module is for fetching a known one.
OpenPhone7

Make an API Call

Action

In Make“Performs an arbitrary authorized API Call.”

Anything the listed modules do not cover can still be reached here: you call any endpoint of the OpenPhone API with the connection you already set up.

When to use it
you found an endpoint in the OpenPhone API documentation that none of the other modules exposes.
Watch out
you write the request yourself, so read the API reference and test with Run once before switching the scenario on.
OpenPhone8

Send a Text Message (SMS)

Action

In Make“Sends a text message.”

Your scenario can text a customer from your OpenPhone number, which keeps the conversation in the same thread your team already answers from.

When to use it
confirm an appointment, acknowledge a new lead or tell a client their order has shipped, triggered by the app where that event happens.
Watch out
One wrong mapping and the text reaches a stranger, so put your own number in the recipient field for the first Run once, and switch to the mapped number once the text looks right.
OpenPhone9

Update a Contact

Action

In Make“Updates an existing contact.”

Changing an existing contact keeps the OpenPhone contact current whenever the person's details change in the tool where your team edits customer data.

When to use it
a deal changes owner in your CRM and the OpenPhone contact should reflect it before the next call.
Watch out
you must point it at an existing contact, so pair it with Get a Contact or a stored ID rather than guessing.
OpenPhone10

List Call Recordings

Search

In Make“Returns a list of call recordings for by the call's ID.”

Given the ID of a call, this search returns the recordings attached to it, so you can file audio alongside the notes and records it belongs with.

When to use it
after Watch New Calls and Recordings, to save each recording in a shared drive folder for the client.
Watch out
like every search, it can return zero, one or several bundles, and each following module runs once per bundle.
OpenPhone11

List Custom Fields

Search

In Make“Returns a list of custom fields.”

Seeing the custom fields defined in your workspace helps you map extra contact data, such as a plan or an account manager, into the right place.

When to use it
while building a contact sync, to check which custom fields exist before you create or update contacts.
Watch out
it only tells you which fields exist; it changes nothing on your contacts.
OpenPhone12

List Phone Numbers

Search

In Make“Returns a list of phone numbers available to the user.”

Retrieving the phone numbers available to your user tells a scenario which line to use, which matters as soon as your team runs more than one number.

When to use it
choosing the right sending number for Send a Text Message (SMS), for example one line per region or per team.
Watch out
it returns only the numbers available to the user behind your connection, so compare the list with what you expect before relying on it.
OpenPhone13

Search Calls

Search

In Make“Returns a list of calls that match the criteria.”

Finding calls that match your criteria lets you work on past activity in bulk, instead of reacting only to calls as they happen.

When to use it
gather the calls with one customer before a renewal meeting, then fetch the summary of each one.
Watch out
a broad search returns many bundles and each module after it consumes one operation per bundle, so narrow the criteria first.
OpenPhone14

Search Text Messages

Search

In Make“Returns a list of text messages that match the criteria.”

Pulling the SMS that match your criteria gives you a slice of text history you can export, count or review, without scrolling the OpenPhone app by hand.

When to use it
before a dispute, collect every text exchanged with one client into a single document.
Watch out
an empty result is normal when nothing matches, and the modules after it then receive no bundle to work on.
Need help

Need help automating OpenPhone with Make?

A person reads every message.

FAQ

OpenPhone and Make: common questions

01Is the OpenPhone Make integration free?
On the Make side, yes: OpenPhone is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops each run after 5 minutes and caps transfer at 512 MB. Paid Make plans lower the interval to 1 minute and remove the cap on active scenarios. On the OpenPhone side, the documentation states the modules require a paid OpenPhone account, so budget for that subscription separately.
02What do you need to connect OpenPhone to Make?
Two things: a paid OpenPhone account and an API key. In OpenPhone, open the workspace settings, go to the API tab, click Generate API key, label it and copy the value. In Make, add an OpenPhone module, click Create a connection, paste the key into the OpenPhone API Key field and click Save. If a prompt appears, authenticate and confirm access. The connection is then reused by every OpenPhone module you add.
03Do OpenPhone triggers in Make react in real time?
Yes. All 4 OpenPhone triggers are instant: OpenPhone calls Make through a webhook as soon as the event happens, whether that is a call ringing or completed, a summary or transcript being ready, or a text delivered or received. Make does not have to poll on a schedule for these. The lightning badge on the module in the editor shows that a trigger is instant, which is a quick way to check when you build.
04What if the OpenPhone Make integration lacks the module you need?
Use Make an API Call. It reaches any endpoint of the OpenPhone API with the connection you already created, so you are not limited to the ready-made modules. Read the OpenPhone API documentation to find the endpoint and the request it expects, then test with Run once before switching the scenario on. The Make documentation lists no numeric limits for this app, so check the OpenPhone side if a request is refused.
05Should you use Make or n8n for OpenPhone?
It depends on your criteria, not on a winner. What this guide can confirm is the Make side: 18 ready-made modules, 4 instant triggers for calls, summaries, transcripts and texts, and Make an API Call for the rest, all built visually. For n8n, check whether an OpenPhone node exists and what it covers before deciding. Compare the two on the modules you actually need, how your team likes to build, and which tool already runs your other automations.
Same platform

Other docs you might need on this stack.

Browse all integrations