Resources · Make integration

SignalWire Make integrationAutomate SignalWire with Make.

What if every call and text in SignalWire could start the next task on its own? The SignalWire Make integration gives you 15 modules: 4 triggers, 9 actions and 2 searches. This guide links your account, then walks you through a first working scenario.

Try the SignalWire integration on MakeSee the 15 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SignalWire Make integration do for you?

The integration lets Make read and act on the calls and messages of your SignalWire account. You build a scenario, the automation itself, from modules: small blocks that each watch, create, fetch, update or delete one call or one message. SignalWire keeps handling the phone side, and Make decides what happens next.

Missed-call follow-up. Watch New Calls reacts the moment a call comes in, and Create a Message sends the caller a text right after. A small clinic or a repair shop gets back to every caller, even when nobody could pick up.

A clean message log. Watch Messages picks up each new message on the scenario's schedule, and the next module copies it to the spreadsheet or CRM your team already reads. Support leads stop scrolling through the SignalWire dashboard.

Housekeeping on old records. Search Calls or Search Messages finds the records you target, then Delete a Call, Delete a Message or Clear a Message tidies them up in one pass.

The listed modules only cover calls and messages. For any other part of the SignalWire API, Make an API Call reuses the same connection. If you are still picking a platform, the n8n vs Make comparison lays out the criteria, the Make pricing page explains how operations are counted, and Make training helps if this is your first scenario.

Connect

How do you connect SignalWire to Make?

  1. 01

    Add a SignalWire module

    In your scenario, click the +, search for SignalWire and pick any module. In its settings, click Create a connection. A connection is your SignalWire account linked to Make once, then reused by every SignalWire module.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, which helps when several accounts share one Make organization. Then follow the window: either approve Make on SignalWire's own page, or paste the key SignalWire gives you.

  3. 03

    Save and check the list

    Click Save. The connection now appears in the module's dropdown, and every other SignalWire module you add later can select it without asking for your credentials again.

First scenario

Your first scenario: text back every incoming call

GoalWhen a call comes in on SignalWire, Make sends the caller a text message.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the editor to place the first module.

  2. 02

    Add Watch New Calls

    Search for SignalWire, choose Watch New Calls and pick your connection. This trigger is instant: SignalWire tells Make through a webhook as soon as a call comes in.

  3. 03

    Add Create a Message

    Click the + on the right of the trigger and pick Create a Message. Fill its fields by mapping data from the call bundle, the item the trigger passes on, then write your reply text.

  4. 04

    Test with Run once

    Click Run once, then place a test call to your SignalWire number. Open each module's bubble to read the bundle it received and check the text went to the right person.

  5. 05

    Switch it on

    Turn the scenario on. With an instant trigger there is no interval to set: each incoming call starts a run, and each module that runs counts as one operation on your plan.

Triggers

What can start a SignalWire scenario?

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

SignalWire1Watch Calls

Watch Calls

Scheduled trigger

In Make“Triggers when a new call is created.”

Watch Calls hands your scenario each new call created in your SignalWire account, one bundle per call, so later modules can log it, tag it or notify someone.

How it fires
scheduled. Make checks SignalWire on the scenario's schedule, every 15 minutes by default, and collects the calls created since the last check.
When to use it
call reporting where a short delay does not matter, such as filling a shared sheet with every call your team handled.
Watch out
on the Free plan the shortest interval is 15 minutes; for an immediate reaction, pick Watch New Calls instead.
SignalWire2Watch Messages

Watch Messages

Scheduled trigger

In Make“Triggers when a new message arrives.”

With Watch Messages, each new message that reaches your SignalWire account becomes a bundle your scenario can route, store or answer.

How it fires
scheduled. Make queries SignalWire at the rhythm set on the scenario and gathers the messages that arrived in between.
When to use it
archiving texts in a CRM or a spreadsheet, where collecting them in batches is perfectly fine.
Watch out
each message read counts as operations for the modules it passes through, so a busy number drains your plan faster; filter early if you only care about some messages.
SignalWire3Watch New Calls

Watch New Calls

Instant trigger

In Make“Triggers when a new call comes in.”

Watch New Calls starts your scenario the instant a call comes in, which is what you need when the caller should hear back from you right away.

How it fires
instant. SignalWire calls Make through a webhook as soon as the call happens, so no schedule is involved.
When to use it
a text sent to every caller, or an alert in your team chat when a key line rings.
Watch out
the scenario must be switched on to receive anything; while it is off, incoming calls do not start a run.
SignalWire4Watch New Messages

Watch New Messages

Instant trigger

In Make“Triggers when a new message comes in.”

Watch New Messages reacts as soon as a text reaches your SignalWire number, which lets you acknowledge, sort or forward it before anyone opens a dashboard.

How it fires
instant. SignalWire notifies Make through a webhook the moment the message comes in.
When to use it
a keyword reply, a support ticket created from an SMS, or a lead pushed to sales the second it writes.
Watch out
if you answer with Create a Message in the same scenario, make sure the reply cannot be picked up as a new incoming message, or add a filter.
Modules

What can Make do in SignalWire?

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

SignalWire1

Clear a Message

Action

In Make“Clears the body of the existing message.”

Clear a Message empties the body of a message that already exists, while the message itself stays in your account. You keep the trace of the exchange without its content.

When to use it
once a text carrying a code or personal detail has been processed and copied where it belongs.
Watch out
the text is gone after this step, so run it only after the modules that needed the content.
SignalWire2

Create a Call

Action

In Make“Creates a new call.”

Create a Call places a new call from SignalWire, triggered by whatever happened earlier in the scenario, so a phone rings without anyone dialing.

When to use it
calling back a lead who just filled a form, or ringing the on-call person when an alert arrives from another app.
Watch out
test with your own number and Run once before mapping real contacts.
SignalWire3

Create a Message

Action

In Make“Creates a new message.”

Create a Message sends a new text from your SignalWire account, with content you write once and fill with data mapped from earlier modules.

When to use it
appointment confirmations, delivery updates or a quick reply after a missed call.
Watch out
each bundle reaching this module sends one text, so a search that returns many items sends many messages; check the bundle count with Run once.
SignalWire4

Delete a Call

Action

In Make“Deletes a call by ID.”

Delete a Call removes one call from SignalWire using its ID, the identifier another module such as Search Calls or Watch Calls gives you.

When to use it
cleaning out test calls after you finish building, or removing records your team no longer wants to keep.
Watch out
nothing in Make undoes this. Put a filter in front, then run the scenario once on a single test record before letting it loose on real calls.
SignalWire5

Delete a Message

Action

In Make“Deletes a message by ID.”

Delete a Message erases one message from your SignalWire account by its ID, taken from a trigger or a search earlier in the flow.

When to use it
when the whole message has to go, not just its text; if you only want the content removed, Clear a Message is the gentler option.
Watch out
nothing in Make brings a deleted message back, so copy it elsewhere first if it might matter later.
SignalWire6

Get a Call

Action

In Make“Gets a call by ID.”

Get a Call fetches the details of one call when you already hold its ID, so later modules work with complete, current information.

When to use it
a scenario receives a call ID from another tool, and you need the rest of that call's data before writing a report or a CRM note.
Watch out
it reads a single call; to find calls without knowing their ID, use Search Calls.
SignalWire7

Get a Message

Action

In Make“Gets a message by ID.”

Get a Message pulls one message from SignalWire by its ID and hands its full details to the next module in the scenario.

When to use it
checking the latest state of a text you sent earlier, for instance before logging it in a ticket or deciding on a follow-up.
Watch out
without an ID it has nothing to read; Search Messages is the module that finds messages by other criteria.
SignalWire8

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call reaches any endpoint of the SignalWire API that the ready-made modules leave out, and it reuses the connection you already created.

When to use it
you need a SignalWire feature beyond calls and messages, which is all the other modules cover.
Watch out
here you shape the request yourself, so keep the SignalWire API reference open and test with Run once before going live.
SignalWire9

Update a Call

Action

In Make“Updates a call by ID.”

Update a Call changes an existing call identified by its ID, so a scenario can steer a call that is already on record instead of creating a new one.

When to use it
when an event elsewhere, like a ticket closing or a form answer, should be reflected on a call SignalWire already holds.
Watch out
map the ID from a trigger or a search, never type it by hand, or every run edits the same call.
SignalWire10

Search Calls

Search

In Make“Searches for calls or lists them all.”

Search Calls looks up calls in your account, or lists all of them, and returns each match as its own bundle for the next modules.

When to use it
building a report, finding the calls to clean up, or checking whether a number already called before you act.
Watch out
the result can be zero, one or many bundles, and every following module runs once per bundle, so narrow the search to save operations.
SignalWire11

Search Messages

Search

In Make“Searches for messages or lists them all.”

Search Messages finds texts in your SignalWire account, or returns the whole list, one bundle per message found.

When to use it
exporting a conversation history to a spreadsheet, or spotting the messages to clear or delete in a later module.
Watch out
with zero results the next modules have nothing to process, and a long result multiplies operations downstream; test the search alone with Run once first.
Need help

Need help automating SignalWire with Make?

A person reads every message.

FAQ

SignalWire and Make: common questions

01Is the SignalWire Make integration free?
Yes, SignalWire is a standard app in Make, so its modules work on the Free plan. That plan has its own limits: 2 active scenarios, at least 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. Make counts usage in operations, one per module run, so a busy SignalWire number uses them faster than a quiet one.
02What do you need to connect SignalWire to Make?
A SignalWire account and a Make account. The documentation lists no special prerequisite. You add any SignalWire module, click Create a connection, optionally name it, then either approve Make on SignalWire's page or paste the key SignalWire gives you, and save. That connection is then shared by every SignalWire module in all your scenarios, so you do it once per account rather than once per module. SignalWire is a standard app, so this works on the Free plan as well as on paid ones.
03Do SignalWire triggers in Make fire in real time?
It depends on the trigger. Watch New Calls and Watch New Messages are instant: SignalWire notifies Make through a webhook as soon as the call or the message comes in. Watch Calls and Watch Messages are scheduled: Make checks SignalWire on the scenario's schedule, every 15 minutes by default, and the Free plan cannot go below that interval. Pick an instant trigger when the reply has to be immediate, and a scheduled one for logging or reporting.
04What if a SignalWire module is missing in Make?
Use Make an API Call. The 15 ready-made modules cover calls and messages only: watching, creating, reading, updating, searching and deleting them. For any other endpoint of the SignalWire API, this module sends the request with the connection you already set up, so you do not need a second login. You write the request yourself, so keep the SignalWire API reference open and test the module alone with Run once before adding it to a live scenario.
05Should you use Make or n8n for SignalWire?
It depends on your criteria rather than on a winner. On Make, SignalWire comes with 15 modules, including 2 instant triggers for calls and messages, plus Make an API Call for the rest of the API, and it runs from the Free plan. Before choosing, check whether the other tool covers the same events you need, how your team prefers to build, and how each one counts usage. The n8n vs Make comparison linked on this page walks through those points.
Same platform

Other docs you might need on this stack.

Browse all integrations