Resources · Make integration

8x8 Make integrationAutomate 8x8 with Make.

Can an incoming text on 8x8 start a workflow on its own? The 8x8 Make integration gives you 3 instant triggers and 4 actions for SMS and chat app messages. This page is for teams that handle customer messages, and it walks you from the connection to a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the 8x8 Make integration do for you?

The 8x8 Make integration links your 8x8 account to Make, a no-code tool where you build a scenario, meaning an automation made of connected steps. Here those steps can react the moment an SMS or chat app message reaches you, follow the status of what you sent, and send new messages without anyone typing them.

Replies that go out by themselves. A customer texts your business number, Watch SMS Inbound Messages starts the scenario, and Send a Single SMS answers with a confirmation. Nobody has to sit by the inbox to acknowledge a request.

A clear view of delivery problems. Watch Outbound Message Statuses fires whenever the status of a message you sent changes. You can pass that change to another app and see at a glance which customers did not get your text.

Chat app conversations routed to the right place. Watch ChatApps Inbound Messages picks up each new chat app message, and Send a Single Chat App Message lets you answer on the same channel. For campaigns, Send a Bulk SMS sends messages in batches instead of one by one.

The listed modules cover messaging only. When you need another part of the 8x8 API, Make an API Call reuses the same connection. The same app also exists on n8n; the n8n vs Make comparison lays out how the two tools differ. If you are new to the editor, Make training covers the basics, and Make pricing explains the plans.

Connect

How do you connect your 8x8 account to Make?

  1. 01

    Create an API key in 8x8

    In your 8x8 account, open the API Keys menu in the left pane and click Create API Key. Give the key a name, click Save, then copy it with the document icon next to it.

  2. 02

    Add an 8x8 module and open the connection

    In Make, add any 8x8 module to your scenario and click Create a connection. The connection is your 8x8 account linked to Make once, and every 8x8 module in your scenarios reuses it. A name in Connection name is optional.

  3. 03

    Paste your credentials and save

    Enter the credentials you copied from 8x8, or follow the instructions Make shows on screen. Once the connection is saved, the module fields open and you can start setting them up.

First scenario

Your first scenario: acknowledge every inbound SMS

GoalWhen a customer texts your 8x8 number, Make sends a short confirmation back by SMS.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add the first module. Search for 8x8 and pick Watch SMS Inbound Messages.

  2. 02

    Set up the trigger

    Click Create a webhook, then Create a connection and paste your API key. From then on, 8x8 tells Make about each new text as soon as it lands.

  3. 03

    Add the reply

    Click the + on the right of the trigger and add Send a Single SMS. Map the data received from the trigger so the reply goes back to the person who wrote, then type your confirmation text.

  4. 04

    Test with Run once

    Click Run once, then send a text to your 8x8 number from your own phone. Open each module to read the bundle it received, one bundle being one message passed from step to step.

  5. 05

    Switch it on

    Once the test reply reaches your phone, switch the scenario on. Each module run counts as one operation, the unit Make tracks on your plan, so a text and its reply cost two.

Triggers

What can start an 8x8 scenario?

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

8x81Watch ChatApps Inbound Messages

Watch ChatApps Inbound Messages

Instant trigger

In MakeTriggers when you have a new ChatApp inbound message.

This trigger starts your scenario with each new message a customer sends you through 8x8 chat apps, so the conversation reaches your other tools without anyone copying it over.

How it fires
instant, 8x8 calls Make through a webhook as soon as the message arrives, so there is no polling interval to wait for.
When to use it
your support team answers on a chat app channel and wants every incoming question logged, tagged or answered with Send a Single Chat App Message.
Watch out
it only covers chat app traffic; inbound texts need Watch SMS Inbound Messages in a separate scenario.
8x82Watch Outbound Message Statuses

Watch Outbound Message Statuses

Instant trigger

In MakeTriggers when outbound message status has been changed.

You learn what happened to the messages you sent: each time the status of an outbound message changes, this trigger hands the update to your scenario so you can act on it.

How it fires
instant, 8x8 notifies Make through a webhook the moment the status changes.
When to use it
after a batch sent with Send a Bulk SMS, you want failed deliveries flagged so someone can call those customers instead.
Watch out
one campaign produces many status changes, and each one is a bundle that costs operations in every module after the trigger, so filter early.
8x83Watch SMS Inbound Messages

Watch SMS Inbound Messages

Instant trigger

In MakeTriggers when you have a new SMS inbound message.

Every text that reaches your 8x8 number can become the start of a workflow, whether it is a booking request, a reply to a campaign or a customer question.

How it fires
instant, 8x8 alerts Make through a webhook as soon as the SMS comes in.
When to use it
you want each inbound text answered with an automatic confirmation, or copied into the tool where your team follows up on requests.
Watch out
if your reply goes out with Send a Single SMS, test with Run once from your own phone first, so you read the bundle before real customers get the message.
Modules

What can Make do in 8x8?

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

8x81

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Reach any part of the 8x8 API that the other modules leave out, using the connection you already set up, with no second login or key to manage.

When to use it
the three send actions below do not do what you need, but the 8x8 API documentation describes a request that does.
Watch out
you write the request yourself, so keep the 8x8 API documentation open and check the result with Run once.
8x82

Send a Bulk SMS

Action

In MakeSends SMS by batches.

Get one message out to a whole list of numbers in batches, rather than running a separate send for each contact in your scenario.

When to use it
a store closure, a delivery delay or an event reminder has to reach many customers at once.
Watch out
pair it with Watch Outbound Message Statuses to find out which texts did not arrive.
8x83

Send a Single Chat App Message

Action

In MakeSends a ChatApps message.

Answer a customer on the chat app channel they used, straight from your scenario, so the reply stays in the conversation they started.

When to use it
right after Watch ChatApps Inbound Messages, to confirm you received a question or to send the next step.
Watch out
it sends one message per bundle, so a trigger that brings in several messages sends several replies.
8x84

Send a Single SMS

Action

In MakeSends a single SMS.

Send one text to one person at the exact point in your scenario where it matters, such as a confirmation, a code or a follow-up.

When to use it
a form is submitted in another app, an order ships or a text comes in and deserves an answer.
Watch out
for a message going to a long list, Send a Bulk SMS is the better fit than one single send per contact.
Need help

Need help automating 8x8 with Make?

A person reads every message.

FAQ

Common questions about the 8x8 Make integration

01Is the 8x8 Make integration free?
Yes, on the Make side. 8x8 is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run and 512 MB of data transfer. Paid plans go down to 1 minute between runs and remove the cap on active scenarios. You still need an active 8x8 account, which 8x8 bills on its own terms, so check its pricing page for that part.
02What do you need to connect 8x8 to Make?
An active 8x8 account and an API key. You create the key in 8x8 from the API Keys menu in the left pane: click Create API Key, name it, save it and copy it with the document icon. Then, in Make, add an 8x8 module, click Create a connection, and paste the key or follow the instructions on screen. For a trigger, click Create a webhook first. The connection is reused by every 8x8 module afterwards.
03Do 8x8 triggers in Make work in real time?
Yes. All three 8x8 triggers are instant: Watch ChatApps Inbound Messages, Watch Outbound Message Statuses and Watch SMS Inbound Messages. 8x8 calls Make through a webhook as soon as the event happens, so the scenario does not wait for a polling interval. That is why the setup asks you to click Create a webhook before creating the connection. The 15 minute default schedule of new scenarios only applies to scheduled triggers, which this app does not have.
04What if the 8x8 module you need is missing in Make?
Use Make an API Call. This module calls any endpoint of the 8x8 API with the same connection, so you can cover what the three messaging actions and the three triggers leave out. You write the request based on the 8x8 API documentation and check the response with Run once. The Make documentation for this app also notes that part of its content is AI generated from 8x8 sources, so verify important details with 8x8 directly.
05Should you use Make or n8n for 8x8?
It depends on the tool your team already works in. 8x8 often has an n8n node as well, so both tools can usually reach it. In Make you get 7 ready modules, including 3 instant triggers and Make an API Call for the rest of the API, inside a visual editor where you test with Run once. The comparison page linked earlier on this page goes through the differences between the two tools in detail.