SMS8

Send unlimited SMS via n8n from your own phone.

Add one HTTP Request node to any n8n workflow, point it at the SMS8 API, and the text leaves your own Android phone a moment later. No Twilio account, no A2P 10DLC filing, no fee per message and no rented number. Replies come back into n8n through a signed webhook.

SMS8: Connect GoHighLevel, Zapier, Make, Google Sheets, WordPress or your AI tool.

How n8n and SMS8 fit together

n8n runs the workflow. SMS8 is the SMS gateway, and it runs on a phone you own. n8n has no SMS8 node to install. You use the HTTP Request node that ships with n8n, set it up once, and copy it into any workflow that needs to text.

Anything n8n can listen to can now send a real text: a form submission, a Stripe event, a new database row, a schedule, a file upload, a Slack mention. The path is short. n8n calls the SMS8 API, SMS8 hands the message to your paired phone, and the phone sends it from its SIM through your carrier.

It works the same on n8n cloud and on self-hosted n8n. If you run n8n in Docker next to the rest of your stack, the only outside service in the chain is SMS8 itself. That means one account, one invoice and one fewer vendor holding your customer data.

The other direction works too. When a contact replies, SMS8 posts the message to an n8n Webhook trigger, so a reply can start its own workflow.

Why builders send from n8n this way

Most people come from the n8n and Twilio combination. These are the reasons they switch.

01

A fixed bill

Twilio charges per message and per rented number, plus carrier and A2P fees. SMS8 is one flat monthly plan with unlimited messages. The texts ride on the SIM's own mobile plan, and many plans include unlimited texting.

02

No registration wait

A text from a real SIM in a real phone is person to person. There is no A2P 10DLC brand, no campaign approval and no carrier filing before your first workflow can send.

03

A number people answer

The sender is a normal mobile number. Contacts can save it, call it back and reply to it. People reply to a real mobile number much more readily than to a short code.

04

One request, any workflow

The node is the same in every workflow. Change the trigger and the text, keep the rest.

Your first n8n SMS workflow in five steps

About ten minutes from start to a sent text.

1

Create an account and pair a phone

Sign up at app.sms8.io. Install the SMS8 Android app on any phone with Android 7 or newer and a SIM, then scan the code on the Devices page. Keep the phone on a charger and online.

2

Copy your API key

Open the API page of your dashboard and copy the key. Treat it like a password.

3

Add an HTTP Request node

In n8n, open a workflow, click the plus sign and add HTTP Request after the node that holds the phone number.

4

Fill in the request

Set POST, the SMS8 messages URL, your key in the X-Api-Key header, and map the number and message fields from the previous node.

5

Test, then activate

Run the node with test data. The text leaves your phone and n8n shows the JSON answer with the message ID. Activate the workflow and it is live.

The HTTP Request node, setting by setting

This is the whole configuration. Copy the node once it works and reuse it.

Setting in n8nValue
MethodPOST
URLhttps://app.sms8.io/api/v1/messages
AuthenticationNone, the key goes in a header
HeaderX-Api-Key with your SMS8 API key
Send BodyOn, form fields or JSON
numberAn expression such as {{ $json.phone }}, in international format like +15551234567
messageYour text, with n8n expressions such as {{ $json.first_name }}
devicesOptional. The phone and SIM that should send, for example 182|0
ResponseJSON, and leave Never Error off so failed calls stop the workflow

Every optional field, the response shape and the error codes are in the API reference.

More you can do in the same request

Only the number and the message are required. Add these when a workflow needs them.

01

Personal messages

Build the message from n8n expressions: the first name, the order number, the tracking link, the code. Each run sends its own text.

02

Pick the sender

Use the devices field to choose one phone and SIM slot, where 0 is SIM 1 and 1 is SIM 2. Leave it out and your default phone sends. You can also rotate across all your phones to spread the load.

03

MMS

Set the type to MMS and add a public image link to send a picture with the text.

04

Priority for codes

Mark a message as priority and it goes ahead of others waiting on that phone. Use it for login codes and alerts, so they never sit behind a broadcast.

05

Send later

Give a future time and SMS8 holds the message until then, even if the workflow finished long before.

06

Many numbers at once

Pass several numbers in one call, or loop the node over a list. SMS8 queues them and the phone works through the queue at its own pace.

n8n SMS workflows people build

Each one is a trigger, a few n8n nodes and the same SMS8 request at the end.

01

Form submission to SMS

A Typeform or website form hits an n8n Webhook trigger. Edit Fields pulls out the name and phone, the HTTP Request node texts the prospect a next-step link, and a Slack node tells sales.

02

Schedule to a segment

A Schedule trigger runs at 09:00. The workflow reads unpaid invoices or tomorrow's appointments from Postgres or a sheet and sends each person a reminder.

03

Database change to SMS

A Postgres, MySQL, Airtable or Notion row changes its status to Shipped. An IF node checks the status, the request sends the tracking link, and a last node marks the row as notified.

04

Failed payment to SMS

Stripe sends invoice.payment_failed to your n8n webhook. A Switch node routes by event type, the customer gets a text with a link to update their card, and your CRM is updated.

05

Login codes

Your app asks n8n for a code. n8n generates it, sends it with priority and stores it for the check.

06

Ten more recipes

Lead alerts, abandoned carts, error pings, on-call rotation and calendar reminders, with nodes you can paste into n8n.

Route incoming SMS into n8n

SMS8 posts every incoming message to a URL you choose. Make that URL an n8n Webhook trigger.

1

Add a Webhook trigger

Create a new n8n workflow that starts with a Webhook node set to POST. Copy its production URL.

2

Register it in SMS8

Open the Webhooks page of your dashboard, paste the URL and pick the Received event. SMS8 gives the webhook its own signing secret.

3

Send a test text

Text the SIM in your paired phone from another phone. n8n receives the message with the sender, the text, the phone and SIM that got it, and the time.

4

Activate

Turn the workflow on. Every reply now starts it.

Check the signature first

Every webhook request from SMS8 carries an X-Signature header in the form sha256= followed by an HMAC-SHA256 of the raw body. It is made with that webhook's own secret, not your API key.

Put a Code node right after the Webhook trigger. Compute the same hash with the secret, compare the two, and stop the run if they do not match or the header is missing. Only signed requests reach the rest of the workflow.

Answer quickly. The trigger should respond with a 2xx status within 10 seconds, so set it to respond right away and do slow work, like CRM lookups or AI classification, after that. If n8n is down, SMS8 retries on a growing schedule and logs each attempt. Use the message ID as a unique key so a retried event is never handled twice.

Received is not the only event. You can also subscribe the same or another n8n workflow to sent, delivered and failed, to log every message or retry the ones that failed.

What to do with a reply

Once the message is inside n8n, it is a normal workflow.

01

Branch on a keyword

Switch on YES, HELP or a booking code and send the right answer back through another HTTP Request node.

02

Find the sender

Look the number up in your CRM or database and attach the reply to the right contact or deal.

03

Hand it to a person

Post the reply in Slack or open a ticket when a human needs to answer. Your team can also reply from the SMS8 inbox in the browser.

04

Respect STOP

When someone replies STOP, SMS8 adds the number to your blacklist, so your workflows do not text that person again.

When a workflow does not send

Most problems show up in the answer n8n gets back.

01

success is false

Open the error in the n8n output. A 401 means the API key is wrong or missing from the header. A 400 means a field is missing or malformed.

02

The number is rejected

Use the international format with the plus sign and country code. Add a Set or Code node to clean numbers that come from forms.

03

The message stays queued

The phone is offline, asleep or paused. Messages wait and send when it reconnects. Turn off battery optimization for the SMS8 app and keep the phone charging.

04

A big list is slow

That is the pacing. Each SIM sends one message every 10 to 30 seconds so the number stays in good standing. Add phones or a second SIM to send more in parallel.

05

Replies never reach n8n

Check that the workflow is active and that you pasted the production URL, not the test URL. The deliveries log in SMS8 shows each attempt and the status n8n returned.

What it costs

Plans are priced by the number of connected phones, and every plan includes unlimited messages and full API and webhook access. USD 29 a month for one phone, USD 89 for five and USD 229 for twenty. Yearly billing costs half: USD 14.50, 44.50 and 114.50 a month.

Every account starts with a 3-day trial with 30 messages, no card needed. There is no per-message fee on our side. Your carrier plan covers the texts.

If you prefer a no-code tool, the same account and plan work with Make, Zapier, Google Sheets and WordPress.

Common questions

Still unsure? We answer fast.

Add an HTTP Request node that posts to https://app.sms8.io/api/v1/messages with your API key in the X-Api-Key header and two fields, number and message. The text leaves your own paired Android phone. No Twilio account, no virtual number and no per-message billing.

You do not need one. The built-in HTTP Request node does the job, and it works on n8n cloud and self-hosted n8n alike.

Yes. Every call is a web request to app.sms8.io that returns JSON with a success flag and either the data or an error. It works from the HTTP Request node and from a Code node using fetch.

Create a Webhook trigger in n8n, copy its production URL and add it on the Webhooks page of your SMS8 dashboard with the Received event. SMS8 posts every incoming message to it, signed with an X-Signature header.

200 on success, 400 for missing or malformed fields and 401 for a wrong API key. Always read the success flag in the body too.

No. Every text leaves your own SIM on your own phone, person to person. A2P 10DLC covers application traffic through rented long codes, not texts from a real mobile.

Yes. Loop the request over your contacts or pass several numbers in one call. SMS8 paces each SIM at one message every 10 to 30 seconds. For large marketing lists, a campaign in SMS8 adds scheduling, quiet hours and opt-out handling.

Messages wait in the queue and send when the phone reconnects. To be strict about it, subscribe another workflow to the failed event and retry through the API.

SMS8 sends iMessage from a Mac you own with the SMS8 Gateway app, and those replies land in the same inbox. SMS8 paces iMessage to 50 new contacts a day per Mac. People you already talk to are not counted.

Yes. An AI Agent node can call the same HTTP Request as a tool. If you work in Claude or Cursor instead, the SMS8 MCP server gives the agent send and read tools directly.

Send your first n8n text today

Pair your phone, copy your API key and drop one HTTP Request node into n8n.