Resources · Make integration

OpenPhone Make integrationAutomate OpenPhone with Make.

Every call, text and contact in OpenPhone can start or feed an automation. The OpenPhone Make integration gives you 18 modules, 4 of them instant triggers. This guide is for teams that live on the phone: connect your account, then build your first 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 your team?

The OpenPhone Make integration links your business phone account to Make, so calls, texts and contacts can move between OpenPhone and your other tools without code. You build a scenario, which is the automation itself: a chain of modules, where each module is one brick such as a trigger, an action or a search.

Call notes that file themselves. When a call ends, Watch New Call Summaries hands the summary to Make, and the next module can post it wherever your team keeps account history. Sales managers stop chasing reps for recap notes.

A first text for every new lead. A lead coming from a form or a CRM goes through Create a Contact, then Send a Text Message (SMS) greets them from your business number. The contact is already in OpenPhone when they call back.

Searchable conversations. Watch New Call Transcripts and Search Text Messages let a support lead pull what was said on a line and copy it into a ticket or a spreadsheet.

The documentation lists no numeric limit for this app. When a need falls outside the 18 modules, Make an API Call reaches the rest of the OpenPhone API with the same connection. The same app may also exist on n8n; the n8n vs Make comparison explains how the two tools differ. For the bigger picture, read our Make review or check Make pricing before you pick a plan.

Connect

How do you connect OpenPhone to Make?

  1. 01

    Generate an API key in OpenPhone

    Log in to your OpenPhone account (Make's documentation now calls the product Quo), open Settings > API and click Generate API Key. Copy the key and keep it somewhere safe, since Make will ask for it in a moment.

  2. 02

    Create the connection in Make

    In your scenario, add any OpenPhone module and click Create a connection. A connection is your OpenPhone account linked to Make once, then reused by every OpenPhone module. You can type a label in Connection name if you run several accounts.

  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 and confirm access, accept it. The module now shows the connection, and you can move on to its settings.

First scenario

Build your first scenario: text every new lead

GoalWhen a new lead lands in the app your team already uses for forms or sales, Make adds the person to OpenPhone and sends a welcome text.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Search for the app where your leads arrive, a form tool or a CRM, and pick its trigger module.

  2. 02

    Add Create a Contact

    Click the + to the right of that trigger, search for OpenPhone and choose Create a Contact. Pick your connection, then map the lead's details from the previous module into the contact fields Make displays.

  3. 03

    Add the welcome text

    Add one more module: Send a Text Message (SMS). Write a short greeting and map the new contact's number from the step before, so every lead gets a message tied to their own record.

  4. 04

    Test with Run once

    Click Run once, then submit a test lead with your own phone number. Each module shows a bubble with the bundle it received, a bundle being one item passing between modules, here one lead.

  5. 05

    Schedule and switch it on

    Open the clock on the first module and set the schedule; a new scenario checks every 15 minutes by default. Switch the scenario on. From now on, each run counts operations, one per module per bundle.

Triggers

Which OpenPhone events can start a scenario?

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 rings or finishes on your OpenPhone numbers, so the call data reaches your other tools while the conversation is still fresh.

How it fires
instant, OpenPhone calls Make through a webhook as soon as it happens, with no schedule to wait for.
When to use it
log every inbound call in your CRM, or alert a teammate in chat when a key customer rings.
Watch out
it covers both ringing and completed calls, so add a filter after it if you only care about one of the two.
OpenPhone2Watch New Call Summaries

Watch New Call Summaries

Instant trigger

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

Once OpenPhone has finished writing the summary of a call, this trigger passes it to Make, giving you a ready-made recap without anyone typing notes after hanging up.

How it fires
instant, OpenPhone notifies Make through a webhook as soon as the summary is done.
When to use it
push each recap to the deal or ticket it belongs to, so the next person on the account reads it before calling.
Watch out
it reacts to the finished summary, not to the call itself; to act while the phone rings, pick Watch New Calls and Recordings.
OpenPhone3Watch New Call Transcripts

Watch New Call Transcripts

Instant trigger

In Make“Triggers for newly completed transcripts.”

You get the full written transcript of a call as soon as OpenPhone completes it, which is what you need when a summary is too short and every word counts.

How it fires
instant, the app calls Make through a webhook once the transcript is complete.
When to use it
archive what was said on compliance-sensitive lines, or hand the text to the next module to file it with the customer record.
Watch out
transcripts are long; if you only need the gist, Watch New Call Summaries keeps your next modules lighter.
OpenPhone4Watch New Messages

Watch New Messages

Instant trigger

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

Each text your team sends or receives through OpenPhone can kick off a scenario, turning SMS conversations into something your other apps can react to.

How it fires
instant, OpenPhone alerts Make by webhook as soon as a message is delivered or received.
When to use it
copy incoming texts to a shared inbox, or answer a keyword like a booking request with Send a Text Message (SMS).
Watch out
it catches outgoing messages too; if your scenario replies by text, add a filter so it does not react to its own replies.
Modules

What else can Make do in OpenPhone?

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

Actions

9 modules
OpenPhone1

Create a Contact

Action

In Make“Creates a new contact.”

Adds a new person to your OpenPhone contacts, so their name shows up on screen the first time they call or text your team instead of a bare number.

When to use it
right after a lead fills a form or a deal is created in your CRM.
Watch out
run Get a Contact or your own check first if the same person can arrive twice, or you will end up with duplicates.
OpenPhone2

Delete a Contact

Action

In Make“Deletes a contact.”

Removes a contact from OpenPhone for you, which keeps the shared address book clean when a customer leaves or asks to be forgotten.

When to use it
when a record is deleted in your CRM and OpenPhone should follow.
Watch out
it removes a real record from the shared address book, so test it with Run once on a dummy contact before you switch the scenario on.
OpenPhone3

Get a Call Summary

Action

In Make“Retrieves the summary of a call.”

Fetches the summary of one specific call on demand, handy when your scenario already knows the call and simply needs its recap text.

When to use it
after Search Calls, to attach a readable recap to each call it found.
Watch out
it needs the call's ID from an earlier module; for fresh calls, Watch New Call Summaries delivers the recap without this extra step.
OpenPhone4

Get a Call Transcript

Action

In Make“Retrieves the transcript of a call.”

Brings back the full transcript of a single call, giving you every word exchanged when a short recap would miss the detail you need.

When to use it
when a manager flags a disputed call and wants the exact wording saved to the customer file.
Watch out
like Get a Call Summary, it works from a call ID that a trigger or Search Calls must provide first.
OpenPhone5

Get a Contact

Action

In Make“Retrieves information about a contact.”

Reads one OpenPhone contact and returns its details, so later modules can personalize a text or update a CRM record with the right person's information.

When to use it
after Watch New Messages, to know who is writing before you route or answer the text.
Watch out
it targets a single contact you already identify; to explore many records, start from a search module instead.
OpenPhone6

Get a Text Message

Action

In Make“Retrieves information about a text message.”

Retrieves the details of one SMS, which helps when a scenario holds a message reference but needs the message itself before acting on it.

When to use it
after Search Text Messages, to open a specific message and copy its content into a ticket or a report.
Watch out
for texts that just arrived, Watch New Messages already carries the message, so this module would cost an extra operation.
OpenPhone7

Make an API Call

Action

In Make“Performs an arbitrary authorized API Call.”

Lets you call any endpoint of the OpenPhone API from your scenario with the connection you already set up, so a missing module never blocks you.

When to use it
when none of the 18 listed modules does the job you need.
Watch out
you build the request yourself from the OpenPhone API documentation, so it asks more care than a ready-made module.
OpenPhone8

Send a Text Message (SMS)

Action

In Make“Sends a text message.”

Sends an SMS from your OpenPhone number, so customers get confirmations, reminders or replies from the same line your team uses every day.

When to use it
when an appointment is booked, a payment arrives or a new lead needs a first hello.
Watch out
test with your own number during Run once, because every run really sends a text to whoever is mapped in the scenario.
OpenPhone9

Update a Contact

Action

In Make“Updates an existing contact.”

Changes an existing OpenPhone contact, so the details your team sees during a call stay in step with what the rest of your stack knows.

When to use it
when a customer changes company or phone number in your CRM and OpenPhone should reflect it.
Watch out
it edits a contact that already exists; pair it with Get a Contact to find the right record before writing.

Search functions

5 modules
OpenPhone10

List Call Recordings

Search

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

Returns the recordings attached to a given call, which lets you store audio alongside the rest of the customer's history outside OpenPhone.

When to use it
after Watch New Calls and Recordings, to save each recording next to the matching client's file.
Watch out
it is a search module, so it can return zero, one or several bundles; plan the next step for each case.
OpenPhone11

List Custom Fields

Search

In Make“Returns a list of custom fields.”

Shows the custom fields defined on your OpenPhone contacts, a quick way to see which extra data your account can store before you map anything.

When to use it
while designing a sync with your CRM, to line up its fields with the ones OpenPhone knows.
Watch out
it only describes the fields; to write a value into one, use Create a Contact or Update a Contact.
OpenPhone12

List Phone Numbers

Search

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

Returns the phone numbers available to your OpenPhone user, useful when a scenario has to choose which line sends or tracks something.

When to use it
in a team with several lines, to route texts from the number that matches each region or department.
Watch out
each number comes back as its own bundle, so every following module runs once per number and counts operations.
OpenPhone13

Search Calls

Search

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

Finds the calls that match the criteria you set, which lets you work on past conversations instead of waiting for new ones.

When to use it
to rebuild a call log in a spreadsheet when you first connect OpenPhone to Make.
Watch out
a broad search can return many bundles, and each module after it costs one operation per call found.
OpenPhone14

Search Text Messages

Search

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

Looks through your OpenPhone texts and returns those that match your criteria, so older SMS threads become data you can reuse elsewhere.

When to use it
when a customer disputes what was agreed by text and you want the thread copied to their file.
Watch out
an empty result is possible; add a check before modules that expect at least one message.
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?
Yes, on Make's side. OpenPhone is a standard app, so its modules work from the Free plan onward. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. You still need your own OpenPhone subscription, which Make does not cover.
02What do you need to connect OpenPhone to Make?
You need an OpenPhone account and an API key. In OpenPhone, open Settings, then API, and click Generate API Key. In Make, add an OpenPhone module, click Create a connection, paste the key into the OpenPhone API Key field and save. For a trigger, click Create a webhook first, since all four OpenPhone triggers are instant. The same connection then serves every OpenPhone module in your scenarios, so you only do this once per account.
03Do OpenPhone triggers in Make fire in real time?
Yes. All 4 OpenPhone triggers are instant: OpenPhone calls Make through a webhook as soon as a call rings or ends, a summary or transcript is done, or a message is delivered or received. The scenario does not wait for the 15 minute default schedule that applies to polling triggers. Each trigger shows the lightning badge in the editor, and you create its webhook when you add the module, just before the connection.
04What if an OpenPhone module is missing in Make?
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 listed modules. You will need the OpenPhone API documentation to write the request. The module sits in the Actions group and appears in the same search as the others when you click the + in your scenario. Make's documentation lists no numeric limit for this app, so there is no documented quota to plan around. For everything the listed modules already cover, keep them: they ask for far less setup than a raw request.
05Should you use Make or n8n for OpenPhone?
It depends on what you already run. On Make, OpenPhone comes with 18 modules, including 4 instant triggers and Make an API Call for the rest of the API. The same app often has an n8n node too, but check that it covers the calls, texts or contacts you need before choosing. Compare the modules each tool offers for your exact scenario, not the brand. This page does not rank the two tools.
Same platform

Other docs you might need on this stack.

Browse all integrations