Resources · Make integration

peoplefone Make integrationAutomate peoplefone with Make.

Want your phone system to send texts and route calls without anyone clicking? The peoplefone Make integration gives you 6 modules: 2 triggers and 4 actions. This guide explains each one, links your account, and walks you through a first working scenario.

Try the peoplefone integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the peoplefone Make integration do for you?

The peoplefone Make integration links your peoplefone account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules. Each module is one brick, a trigger that starts things or an action that does something, so your SMS and call routing can react to other tools without code.

Texts that leave on their own. Put Create an SMS after a module from another app, such as a booking tool or a CRM, and each new record turns into a message sent from your peoplefone account.

A delivery log you never fill by hand. Watch SMS Status Event picks up status changes on your messages; pair it with Get an SMS Details and push the result into a spreadsheet or a support tool.

Calls sent where your own rules say. Watch Call for External Routing spots calls waiting for an outside decision, and Route External Routing call to destination tells peoplefone where to send each one.

What Make does not cover here: the listed modules stop at SMS and external routing. For anything else the peoplefone API offers, Make an API Call reuses the same connection. The official Make documentation for this app is marked as AI-generated and may contain mistakes, so check key details with peoplefone. Before you build, the Make review sums up the tool, Make troubleshooting helps when a run fails, and n8n vs Make compares both platforms.

Connect

How do you connect peoplefone to Make?

  1. 01

    Generate an API key in peoplefone

    In your peoplefone account, open the API section of the main menu, then API Keys, and click Add. Name the key, select the services it needs, click Save, and copy the key shown in the window.

  2. 02

    Open the connection window in Make

    Add any peoplefone module to your scenario and click Create a connection. A connection is your peoplefone account linked to Make once, then reused by every peoplefone module. The Connection name field is optional.

  3. 03

    Paste the key and save

    Paste the API key you copied into the credentials field, or follow the instructions Make shows on screen, and confirm. From now on the module can read and act on your peoplefone account.

First scenario

Your first scenario: text a customer from another app

GoalWhen a new record appears in another app, Make sends an SMS through peoplefone.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to place the first module. This one comes from the app that holds your customers, such as a form or a CRM.

  2. 02

    Set up the starting app

    Pick that app's trigger, link its account, and fill its fields. Each new record it finds becomes a bundle: one item handed to the next module, here one customer with a phone number.

  3. 03

    Add Create an SMS

    Click the + on the right of the first module, search peoplefone, choose Create an SMS and click Create a connection. Then map the data from the first module into its fields.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can check that the right customer got the right text.

  5. 05

    Schedule and switch it on

    Open the clock on the first module: a new scenario checks every 15 minutes by default, and the Free plan cannot go faster. Adjust it if your plan allows, then switch the scenario on.

Triggers

Triggers: what starts a peoplefone scenario

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

peoplefone1Watch Call for External Routing

Watch Call for External Routing

triggerIn the docs only

You get each call that peoplefone hands over for an outside routing decision, as a bundle your scenario can reason about. The documentation lists the module without a description, so its exact output is something to read on your first Run once.

How it fires
scheduled, judging by its Watch name: Make checks the app on the scenario's schedule. The clock badge in the editor confirms it.
When to use it
when routing depends on data held elsewhere, for example the account manager stored in your CRM.
Watch out
a scheduled check waits for the next run, so pick the shortest interval your plan allows.
peoplefone2Watch SMS Status Event

Watch SMS Status Event

triggerIn the docs only

Status updates on the texts you send turn into bundles, which lets you know what happened to a message without opening peoplefone. The documentation gives no list of statuses, so look at the bundles after a test to see which values appear.

How it fires
scheduled, going by its Watch name: Make checks the app on the scenario's schedule, shown by the clock badge.
When to use it
after a reminder or a code has been sent, to log the outcome or alert someone when a message fails.
Watch out
Free plan runs are spaced by 15 minutes at least, so updates arrive in batches.
Modules

Actions: what peoplefone does inside a scenario

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

peoplefone1

Create an SMS

ActionIn the docs only

Sends a text from your peoplefone account using data coming from earlier modules, so confirmations and reminders go out without a person typing them.

When to use it
right after the module that brings the customer, the order or the appointment.
Watch out
each bundle sends its own message; filter upstream so one event does not text a customer twice.
peoplefone2

Get an SMS Details

ActionIn the docs only

Fetches the information peoplefone holds about one message you already sent, which fills a log or a support ticket with facts instead of guesses.

When to use it
after Watch SMS Status Event, when the status alone is not enough and you want the full record.
Watch out
it reads a single message, so it needs the identifier of that SMS mapped from a previous module.
peoplefone3

Make an API Call

ActionIn the docs only

Opens the rest of the peoplefone API to your scenario, with the connection you already set up, so a missing module is not a dead end.

When to use it
once you have checked that none of the other five modules does the job.
Watch out
you write the request yourself, so keep the peoplefone API documentation open, and remember the API key only reaches the services you selected.
peoplefone4

Route External Routing call to destination

ActionIn the docs only

Gives peoplefone the destination for a call that is waiting on an outside decision, which puts your own routing logic in charge of who answers.

When to use it
as the last step after Watch Call for External Routing, once earlier modules have looked up where the caller belongs.
Watch out
the documentation says nothing about what happens to a call left unrouted, so test with Run once before relying on it.
Need help

Need help automating peoplefone with Make?

A person reads every message.

FAQ

peoplefone and Make: common questions

01Is the peoplefone Make integration free?
Yes, on the Make side. peoplefone is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs spaced by 15 minutes at least, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) go down to a 1 minute interval and count usage in credits each month. You still need an active peoplefone account, whose subscription is covered on the peoplefone pricing page.
02What do you need to connect peoplefone to Make?
An active peoplefone account and an API key. You create the key in peoplefone under API, then API Keys: click Add, name it, select the services it should reach, save and copy the key shown in the window. In Make, add a peoplefone module, click Create a connection, optionally fill the Connection name field and paste the key. The connection is then reused by every peoplefone module in your scenarios, so you only do this once.
03Do peoplefone triggers in Make fire instantly?
No, not as far as the documentation shows. Watch Call for External Routing and Watch SMS Status Event behave as scheduled triggers, a type deduced from their Watch names: Make checks peoplefone on the schedule of the scenario, which is every 15 minutes for a new scenario and never faster on the Free plan. Paid plans can shorten the interval to 1 minute. The clock badge on the module in the editor tells you the type for sure.
04What if a peoplefone module is missing in Make?
Use Make an API Call. It calls any endpoint of the peoplefone API from your scenario, through the connection you already have, so needs beyond SMS and external routing stay within reach. Check that your API key includes the services the request needs, since the key only reaches what you selected when creating it. Also keep in mind that the Make documentation for peoplefone is flagged as AI-generated and may contain errors: when a detail matters, confirm it with peoplefone.
05Should you use Make or n8n for peoplefone?
It depends on the tool your team already runs. In Make, peoplefone comes with 6 modules, two scheduled triggers and four actions, plus Make an API Call for the rest of the API, all usable without code from the Free plan. Many apps also have an n8n node, so check on the n8n side whether peoplefone has one before you choose. The dedicated comparison on this site lays out the criteria between the two platforms.
Same platform

Other docs you might need on this stack.

Browse all integrations