Resources · Make integration

CommPeak Make integrationAutomate CommPeak with Make.

Can Make send and react to your CommPeak text messages? Yes. The CommPeak Make integration gives you 4 modules: 2 triggers for incoming SMS and short link clicks, plus 2 actions. This page shows how to link your account and build a first scenario step by step.

Try the CommPeak integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the CommPeak Make integration let you automate?

The CommPeak Make integration links your CommPeak account to Make so text messages can start or finish an automation. In Make, that automation is called a scenario: a chain of modules, where each module is one brick, such as a trigger that watches CommPeak or an action that sends an SMS.

Replies that reach the right person. Watch Incoming SMS Messages picks up the texts your customers send, and a second step can pass them on. For a support desk, that could mean forwarding each reply to the mobile of whoever is on duty with Send an SMS.

Campaign links that trigger a follow up. Watch Clicks on Short URL notices when someone opens a link you shortened in CommPeak. A sales team can use that signal to add the lead to a spreadsheet or a CRM through another app's module.

Texts sent from any other tool. Send an SMS works just as well at the end of a scenario started elsewhere, for example a new booking in a scheduling app. The 10to8 Make integration is one starting point of that kind.

Know the limits before you start. Make's own documentation for CommPeak is marked as limited, with no description for any module, so this page sticks to what the module names and Make's editor tell you. For anything the 4 modules do not cover, Make an API Call reaches the rest of the CommPeak API. CommPeak may also exist as an n8n node; the n8n vs Make comparison helps you pick a tool, and the Make training covers the editor from scratch.

Connect

How do you connect your CommPeak account to Make?

  1. 01

    Add a CommPeak module

    Open your scenario, click the +, type CommPeak and pick any of its modules. Then click Create a connection. A connection is your CommPeak account linked to Make once, and every CommPeak module reuses it afterwards.

  2. 02

    Name it and give access

    Give the connection a name if you like, such as the brand or client it belongs to. Then follow what the window asks: either authorize Make on the CommPeak page that opens, or paste the key your CommPeak account gives you.

  3. 03

    Save and check

    Click Save. If the module now shows its fields instead of an error, the link works. From here, any other CommPeak module you add in this scenario or another one can select the same connection.

First scenario

Build your first scenario with CommPeak

GoalWhen a customer texts your CommPeak number, Make forwards the message to a teammate's phone with Send an SMS.

  1. 01

    Create the scenario

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

  2. 02

    Add the trigger

    Search for CommPeak, choose Watch Incoming SMS Messages and select your connection, or click Create a connection if you have none yet.

  3. 03

    Add the forwarding step

    Click the + on the right of the trigger and pick Send an SMS. Map the incoming message from the trigger into it and add your teammate's number where the module asks for one.

  4. 04

    Test with Run once

    Send a text to your CommPeak number, then click Run once. Open the bubble above each module to read the bundles it received, a bundle being one item passed along, here one message.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set how often Make checks CommPeak. A new scenario runs every 15 minutes by default. Then switch the scenario on so it keeps working without you.

Triggers

What can start a CommPeak scenario?

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

CommPeak1Watch Clicks on Short URL

Watch Clicks on Short URL

triggerIn the docs only

This trigger turns a click on one of your CommPeak short links into the start of a scenario, so a reader who opens your link can set off a follow up without anyone watching the stats.

How it fires
scheduled. Make checks CommPeak on the scenario's schedule, every 15 minutes by default, and handles the clicks found since the last check.
When to use it
after an SMS campaign, to log who opened the offer or to alert a salesperson through another app.
Watch out
Make's documentation gives no description of this module, so check the clock badge and the output of a Run once before you rely on it.
CommPeak2Watch Incoming SMS Messages

Watch Incoming SMS Messages

triggerIn the docs only

Every text a customer sends to your CommPeak number can become a bundle in Make with this trigger, ready to be forwarded, stored or answered by the modules that follow.

How it fires
scheduled. Make checks CommPeak on the scenario's schedule, so a message waits until the next check rather than arriving the second it is sent.
When to use it
a support or booking line where replies should land with a person or in a shared tool.
Watch out
each message processed costs operations on your plan, and the Free plan can only check every 15 minutes at best.
Modules

What can Make do in CommPeak?

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

CommPeak1

Make an API Call

ActionIn the docs only

Here is your way past the short module list: it calls any endpoint of the CommPeak API from your scenario, with the connection you already set up, so no second login is needed.

When to use it
the 3 other modules stop short of what you need, which is likely given how little Make documents for this app.
Watch out
you have to know the endpoint yourself, since Make gives no guidance on the CommPeak API.
CommPeak2

Send an SMS

ActionIn the docs only

With this action a scenario texts someone through your CommPeak account: a confirmation, a reminder or an alert, built from data that earlier modules passed along.

When to use it
at the end of a scenario started by another app, such as a new order or a booking, or to forward an incoming SMS to a colleague.
Watch out
every send is a real message, so point it at your own number while you test with Run once.
Need help

Need help automating CommPeak with Make?

A person reads every message.

FAQ

Common questions about CommPeak and Make

01Is the CommPeak Make integration free?
Yes, on Make's side. CommPeak 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) drop the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module per bundle. Your CommPeak account and its own costs are a separate matter.
02What do you need to connect CommPeak to Make?
A CommPeak account and a Make account. Make's documentation lists no specific prerequisite for this app. You add a CommPeak module, click Create a connection, optionally name it, then either authorize Make on CommPeak's page or paste the key your account provides, and click Save. The documentation is marked as limited and gives no official connection steps for CommPeak, so if something fails, the error Make shows in the connection window is your first clue. Once saved, the connection serves every CommPeak module.
03Do the CommPeak triggers in Make react in real time?
No. Both CommPeak triggers, Watch Incoming SMS Messages and Watch Clicks on Short URL, are scheduled: Make checks CommPeak on the scenario's schedule rather than being called the moment something happens. A new scenario runs every 15 minutes by default, and the Free plan cannot go below that. Paid plans let you check as often as every minute. That type is deduced from the module names, since Make's documentation for CommPeak is limited: glance at the clock badge in the editor to confirm it.
04What if a CommPeak module is missing in Make?
Use Make an API Call. It reaches any endpoint of the CommPeak API from your scenario with the same connection, which covers what the 4 listed modules do not. You will need to know which endpoint to call, because Make's documentation for this app is marked as limited and says nothing about the API. If a step is really about another tool, such as storing a message in a spreadsheet, add that tool's own module after the CommPeak one instead of forcing everything through CommPeak.
05Should you use Make or n8n for CommPeak?
It depends on the tool your team already builds in. On Make, CommPeak comes with 4 modules: 2 scheduled triggers, Send an SMS and Make an API Call for the rest of the API. CommPeak may also have an n8n node, so check its module list against the SMS tasks you need before choosing. Neither tool is ranked here: compare what each one exposes for CommPeak, how your team likes to work, and which other apps your scenario has to reach.
Same platform

Other docs you might need on this stack.

Browse all integrations