Make.com SMS automation that sends from your own phone.
Add the SMS8 app to any Make scenario and your texts leave a real Android phone with your own SIM. Order updates, reminders, lead alerts, cart recovery and one-time codes run from the triggers you already use. Replies come back as an instant Make trigger, so a scenario can answer too.

A native Make app, not a webhook workaround
SMS8 is listed in the Make app directory under its own name. On the scenario canvas you click the plus icon, type SMS8, and the module shows up next to Gmail, Slack and Google Sheets. You add one connection, and every scenario on your team can use it.
When a scenario runs, Make hands the message to SMS8 and SMS8 passes it to the Android phone you paired. The phone sends it with its own SIM. Your contact sees a normal mobile number they can save, call back and reply to.
There is no HTTP module to configure, no JSON body to assemble and no signature to compute. You map a phone field and a message field like you would in any other module.
Make used to be called Integromat. Scenarios built before the rename work the same way, and you can drop the SMS8 module into them without rebuilding anything.
The SMS8 modules in Make
Three actions and one instant trigger. Each one is documented on the SMS8 page of the Make directory.
Send a Message (action)
Sends a text to one or several recipients through your paired phone. Map merge fields from any earlier module into the message. Optional fields let you pin a specific phone or SIM and mark the message as priority so it jumps the queue.
Send OTP Code (action)
Creates a one-time code with a built-in expiry and texts it to the number you map. The module returns a code reference you can check later in the same scenario or in your own app.
Watch Incoming Messages (instant trigger)
Fires the moment your paired phone receives a text. It hands the scenario the sender number, the message body, the device, the SIM slot and the timestamps, ready to route anywhere.
List Messages (action)
Pulls recent received or sent messages, with an optional status filter such as Received, Sent, Delivered or Failed. Handy for reports, audits and keeping a CRM in sync.
From zero to a live scenario
Most people send their first test text in about ten minutes.
Pair an Android phone
Create your SMS8 account, install the SMS8 Android app on a phone with Android 7 or newer, and scan the QR code on the Devices page of your dashboard.
Copy your API key
Open your SMS8 profile and copy the API key. This one key authenticates every SMS8 module call from Make.
Add the connection in Make
In any scenario, click the plus icon, search for SMS8 and pick a module. Click Add a connection, paste the key and give it a name such as SMS8 production. Teammates reuse it in their scenarios.
Place the module behind a trigger
Attach Send a Message or Send OTP Code to the trigger you already use: a Make webhook, Typeform, Stripe, Shopify, Google Sheets, Calendly or a schedule. Map the recipient and the message.
Run once, then switch it on
Click Run once to send a test to your own number. When it arrives, turn the scenario on. Every matching trigger now sends a real text from your phone, and replies thread into the SMS8 inbox.
Scenario recipes you can build today
Each one is a trigger you probably already have, a step or two in the middle, and the SMS8 module at the end.
Typeform lead to the sales rep
Typeform Watch Responses picks up a new submission. A Set Variable step pulls out the phone number and budget. SMS8 Send a Message texts the assigned account manager with the lead's name, so they can call while the lead is still on the thank-you page.
Shopify abandoned cart reminder
The Shopify abandoned checkout trigger starts the scenario. A Sleep step waits half an hour and a filter skips small carts. SMS8 sends the customer the cart link and a recovery code from a number that looks like a person, not a short code.
Appointment reminder the day before
Google Calendar Watch Events or a Calendly booking starts the run. Make sleeps until 24 hours before the start time, then SMS8 sends the time and the meeting link. Clients reply in the same thread to confirm or move it.
Failed payment follow-up
Stripe Watch Events filtered on a failed charge sends a first text right away with the card update link. Sleep steps add a reminder a day later and a final one two days after that.
Receipt check on large orders
A Stripe webhook on a successful charge enters the scenario and a Router splits by amount. The high-value branch runs Send OTP Code, and the customer confirms the code before download links unlock.
Order confirmation from a sheet
A teammate adds a row to the Orders sheet. Google Sheets Watch Rows catches it, an Iterator splits the line items, SMS8 texts the customer, and a last module updates the row status.
Property enquiry to the listing agent
A Google Form on each listing feeds Google Forms Watch Responses. A lookup in Sheets finds the agent's mobile number, and SMS8 sends them the buyer's contact details before they are back at their desk.
Monday digest for the leadership team
A schedule fires every Monday at 09:00. Aggregators collect pipeline from your CRM and revenue from Stripe, an Iterator walks the team list, and SMS8 sends each person the numbers. Their replies land in the SMS8 inbox.
Replies routed back into your tools
Watch Incoming Messages starts a scenario on every reply. Route it by keyword with a Router: add the contact to a CRM, post it in Slack, log it in Airtable or schedule a follow-up text.
Who builds SMS into Make with SMS8
Three kinds of Make builder, each with a reason to move the texting off a metered provider.
Ops teams with internal scenarios
Many teams wired Twilio into Make through HTTP modules and hand-built headers. Each new scenario meant copying that setup again, and the bill grew with every message. With SMS8 one paired phone serves every scenario the team builds, on one flat plan.
Agencies building for clients
On a metered provider every client needs its own sub-account, its own A2P brand and its own campaign approval before the first scenario runs. With SMS8 you pair one phone per client, pin that phone in the module, and hand over a working scenario the day you onboard them. You set what you charge clients for texting.
Founders running a product on Make
When your product runs on Make scenarios in the background, per-message fees make the unit economics hard to read. One SMS8 account with a paired SIM per customer turns the texting into a fixed monthly cost you can plan around.
Make with Twilio or Make with SMS8
The same scenario and the same trigger, with a different layer doing the sending.
| Make + Twilio | Make + SMS8 | |
|---|---|---|
| Setup | Account checks, A2P 10DLC brand and campaign approval | Pair a phone, paste the API key in Make |
| Time before the first text | Days to weeks while filings are reviewed | About ten minutes |
| Cost | Fee per message, number rental, carrier fees | One flat plan, no fee per message |
| A2P 10DLC paperwork | Required for US traffic | Not needed, you send from your own SIM |
| Number your contacts see | A rented virtual number or short code | Your real mobile number |
| Replies inside Make | Inbound webhook plus a Custom Webhook module | Watch Incoming Messages instant trigger |
| Several clients or brands | One sub-account per client | Pin a phone per client in the module |
| Sending volume | Set by the throughput tier you pay for | Set by your SIMs, add phones to send more |
Using Twilio for voice calls in another scenario? Keep it. SMS8 only replaces the texting.
Phones, routing and volume
How the module decides which phone sends, and what happens when one is busy or offline.
Pin a phone or let SMS8 choose
The Send a Message module has an optional device field. Pin a scenario to one phone to keep a client or brand on its own number, or leave it empty and SMS8 picks the next available SIM.
Split traffic with a Router
Put a Make Router before the SMS8 module to fork by country code, business unit or campaign. Marketing batches and one-time codes can then use different phones and never wait on each other.
Pacing that protects your number
Bulk sends are paced at one message every 10 to 30 seconds on each SIM. That keeps the number in good standing with the carrier. For bigger lists, spread the scenario over a time window or pair more phones.
Lists from Sheets or Airtable
Pull contacts with a search module, pass them through an Iterator, filter them, and SMS8 sends one row at a time. Numbers on your blacklist are skipped.
When a phone drops offline
If the paired phone loses connection, SMS8 keeps the message in its queue and sends it when the phone is back. The Make module run still succeeds and the scenario moves on. Pair two or three phones and SMS8 shares the load, so one quiet device does not hold anything up.
Dual-SIM and eSIM
On a dual-SIM or eSIM phone you can choose the SIM per scenario or let SMS8 alternate. That gives you two numbers or twice the sending from one handset.
Need more than the modules
Some scenarios need a call the modules do not cover. Use the Make HTTP module to POST to https://app.sms8.io/api/v1/messages with your key in the X-Api-Key header. It is the same account and the same phones.
If you would rather receive replies on your own server than in a scenario, SMS8 webhooks send each incoming message to your URL, signed with an X-Signature header so you can check it came from us.
The same API key also works in Zapier, n8n and the SMS8 MCP server at mcp.sms8.io, which lets AI agents such as Claude send texts and read replies. A scenario in Make and an agent elsewhere can share the same phone.
Sending responsibly from a scenario
You skip the carrier filing, and the care for your number stays with you.
Get consent first
Text people who gave you their number for this purpose, and keep that consent with the contact in your CRM or sheet.
STOP is handled for you
When someone replies STOP, SMS8 blacklists the number across every scenario and campaign on the account. Add a Watch Incoming Messages branch if you also want to mark the contact in your CRM.
Mind the hour
Use Sleep steps, schedules or filters on time so texts arrive during the day where the contact lives.
Write like a person
Use the first name and the details of the order or booking. Short and specific reads as a message from someone they know.
When a scenario text does not arrive
Check these in order. The cause is almost always the phone or the mapping, rarely Make itself.
The module run failed in Make
Open the run details. A connection error usually means the API key was changed or pasted with a space. Recreate the connection with a fresh key from your SMS8 profile.
The run succeeded but the text is pending
The phone is not collecting jobs. Open the SMS8 app on it, check Wi-Fi or mobile data, keep it on a charger and turn off battery optimisation for SMS8 in the Android settings.
The message shows as failed
The carrier refused it. Look for no signal, a plan with no texting credit, or a number mapped without its country code. Fix the cause and resend.
The recipient field is empty
The trigger did not hand over a phone number for that run. Add a filter before the SMS8 module so runs without a number stop there.
Replies do not start the scenario
Check that the scenario with Watch Incoming Messages is switched on and that the reply went to the paired phone's number.
A big batch is slow
That is the pacing. Each SIM sends one message every 10 to 30 seconds. Start earlier or add phones.
One flat plan behind every scenario
SMS8 plans are priced by how many phones you connect: USD 29 a month for one, USD 89 for five and USD 229 for twenty. Messages are unlimited on every plan, and yearly billing halves the monthly price.
The texts themselves run on the carrier plan of the SIM, and many mobile plans include unlimited texting. Every account starts with a 3-day trial with 30 messages, no card needed. Every plan includes the Make modules.
On the Make side, the modules work on any Make plan. Busy scenarios use more Make operations, so pick the Make tier that fits your run volume.
Pair an Android phone in SMS8, copy your API key, then in Make add the SMS8 module to a scenario and create a connection with that key. Map the phone and message fields, click Run once, and the text leaves your phone. No code is needed.
It is a native app in the Make directory. You find it by name in the module picker and reuse one connection across all scenarios. You never handle request signing, retries or rate limits yourself.
Yes. Integromat is the old name of Make, and older scenarios run as before. Replace the Twilio module or the HTTP module that called another SMS gateway with SMS8 Send a Message, reconnect the fields, and save.
Yes. Put SMS8 Send a Message right after a Make webhook trigger and drag the phone and message fields from the incoming data into the module. It works the same for Stripe, Typeform or your own JSON webhook.
Yes. The Watch Incoming Messages instant trigger fires when your paired phone receives a text, with the sender, body, device and SIM slot. Send it on to a CRM, Slack, Airtable or another SMS step.
No. SMS8 replaces the texting part of Twilio in your scenarios. There is no virtual number to rent, no A2P 10DLC brand or campaign to file and no per-message bill. You pay the SMS8 plan and whatever your carrier charges for the SIM.
Yes. The text leaves your Android phone through its SIM, so contacts see that SIM's mobile number, not a short code or rented long code.
Yes. Pin a phone in the device field, or leave it empty and SMS8 picks the next free SIM. A Router before the module can send different traffic to different phones.
The message waits in the SMS8 queue and goes out as soon as the phone reconnects. The Make run is marked successful. For important sends, pair a second phone so the load is shared.
The rules are the same as on any SMS channel: get consent, honour STOP and respect quiet hours. SMS8 blacklists numbers that reply STOP across your account. A2P 10DLC registration does not apply because each text leaves a regular SIM, person to person.
Send your first Make scenario text today
Pair a phone, paste your key in Make, and every scenario can text from your own number. 3-day trial with 30 messages, no card needed.