Part of the guide SMS Integrations: Zapier, Make, n8n, WordPress, Google Sheets
On this page
The short version
- n8n's HTTP Request node can call SMS8's
/api/v1/messagesendpoint directly, no Twilio account, no custom community node. - For ten very common use cases (lead alert, error ping, abandoned cart, OTP, calendar reminder, oncall rotation, scheduled blast, two-way auto-reply, daily digest, escalation ladder) the workflow is under 5 nodes.
- Total stack cost in 2026: n8n free self-hosted or $20/mo Cloud, plus SMS8 at $29/mo flat with $0 per-message charge.
- Inbound SMS triggers an n8n Webhook node via SMS8's webhook callbacks: full two-way conversation flows are possible without leaving n8n.
Why n8n + SMS in 2026
n8n's growth chart in 2026 looks like a Zapier kill shot. The combination of self-hostable, AI-node-native (built-in OpenAI / Anthropic / Ollama nodes), and fair-source license got it into engineering team after engineering team this year. The thing it still does not ship natively is good SMS support. SMS8 fills that gap: one HTTP Request node sends from your own phone and SIM, on a flat plan with no per-message fee.
The official Twilio node works but assumes you pay Twilio. The handful of community SMS nodes are either abandoned or wrapping someone's API. What does work, beautifully and forever, is the HTTP Request node pointed at SMS8. Your Android phone is the carrier; n8n is the orchestrator. The setup itself is on our n8n SMS integration page, and the other no-code options (Zapier, Make, GoHighLevel) are on the SMS8 integrations page.

The one HTTP node you need to know
Every SMS in this post starts from the same building block. Paste this once into n8n and you have the foundation for all ten recipes.
| Field | Value |
|---|---|
| Method | POST |
| URL | https://app.sms8.io/api/v1/messages |
| Header | X-Api-Key = {{ $credentials.sms8.apiKey }} |
| Body Content Type | JSON |
| Body Parameters |
number = {{ $json.phone }},
message = {{ $json.message }}
|
Store the API key as an n8n Credential (Credentials → Create New → Header Auth, name X-Api-Key). That keeps it out of the workflow JSON when you export to git.
Or as a raw curl from any Code/Function node:
const res = await fetch('https://app.sms8.io/api/v1/messages', {
method: 'POST',
headers: { 'X-Api-Key': $env.SMS8_API_KEY, 'Content-Type': 'application/json' },
body: JSON.stringify({
number: items[0].json.phone,
message: items[0].json.message,
}),
});
return [{ json: await res.json() }];
That is it. Every recipe below assumes you have this one node set up. Now the ten automations.
The 10 recipes
Recipe 01: SMS me every new high-value lead
- Trigger: Webhook / HubSpot / Pipedrive
- Nodes: 3
- Build time: 7 min
You log into your CRM eight times a day. A high-intent lead from a $20K+ company should not wait that long for you to reply. This workflow watches your CRM for new contacts above a threshold (annual revenue, employee count, or a custom score) and SMS-es you the name + company so you can act in 60 seconds.
Flow: HubSpot trigger → IF (deal value > $5000) → HTTP Request to SMS8.
Message body example:
HOT LEAD: {{ $json.firstName }} from {{ $json.company }}
({{ $json.annualRevenue }})
{{ $json.email }}
Open: app.hubspot.com/contacts/{{ $json.contactId }}
Why it works: response time correlates with close rate harder than any other input. Replying in 5 minutes wins 100x more deals than 24-hour follow-ups.
Recipe 02: SMS when production goes down
- Trigger: Cron / health-check / log monitor
- Nodes: 4
- Build time: 10 min
Slack notifications die at 11pm. SMS notifications wake you up. A cron node hits your /health endpoint every minute; if it returns non-200 or times out, an SMS fires to the on-call number.
Flow: Cron (every 1 min) → HTTP Request to /health → IF (status !== 200) → HTTP Request to SMS8.
Include the exact failing endpoint and status code in the SMS so on-call can triage without opening a laptop:
PROD ALERT: api.acme.com/health returned 503
3rd consecutive failure
Last good: 14:21 UTC
Logs: grafana.acme.com/d/api
Add an n8n Wait node and a deduplication step so you do not get 60 SMSes for a 1-hour outage. One initial alert, then one every 15 minutes until it recovers.
Recipe 03: Abandoned cart SMS, 30 minutes after the user left
- Trigger: WooCommerce / Shopify webhook
- Nodes: 5
- Build time: 20 min
The single highest-ROI SMS automation in e-commerce, full stop. Timing matters most: send it 30 to 45 minutes after the cart is abandoned, while the purchase is still on the shopper's mind.
Flow: Shopify "cart abandoned" webhook → Wait (30 min) → HTTP GET cart (check if still abandoned) → IF abandoned → HTTP Request to SMS8.
Make the message specific to the cart. Generic "You left items behind" gets ignored:
Hey {{ $json.firstName }}, your {{ $json.itemName }}
is still waiting. {{ $json.discountCode ? 'Use code ' + $json.discountCode + ' for 10% off' : 'Finish checkout' }}: {{ $json.checkoutUrl }}
Add a STOP-keyword reply handler (Recipe 08) so users can opt out without you getting reported.
Recipe 04: OTP for a Google Form / Tally / Typeform signup
- Trigger: Form submission webhook
- Nodes: 4
- Build time: 15 min
Forms that ask for a phone number get junk numbers. Adding an OTP step kills fake submissions almost entirely. Use SMS8's dedicated otp-send.php endpoint: n8n does not store the code, SMS8 does.
Flow: Form submission → HTTP Request to SMS8 otp-send.php → Return verification URL → User submits code → HTTP Request to SMS8 otp-verify.php.
# Send step (form-urlencoded body)
POST https://app.sms8.io/ajax/otp-send.php
api_key={{ $credentials.sms8.apiKey }}
phone={{ $json.phone }}
length=6
expires_in=600
# Verify step (called from your form's verify page)
POST https://app.sms8.io/ajax/otp-verify.php
api_key={{ $credentials.sms8.apiKey }}
phone={{ $json.phone }}
code={{ $json.userSubmittedCode }}
# returns { "success": true, "verified": true } or verified false with a reason
The full reference is on the SMS8 OTP API page.
Recipe 05: Calendar reminder 1 hour before any meeting
- Trigger: Google Calendar / Cal.com
- Nodes: 4
- Build time: 12 min
Push notifications fail when you have Do Not Disturb on. SMS reaches the lock screen no matter what. Pair this with a Cal.com booking flow and you double the show-rate on calls scheduled by strangers.
Flow: Cron (every 5 min) → Google Calendar Get Events (start time in next 60-65 min) → Loop over events → HTTP Request to SMS8.
Reminder: {{ $json.summary }} in 1 hour
{{ $json.hangoutLink || $json.location }}
Reply RESCHEDULE to move.
For booking flows, route the SMS to both you and the attendee. A text is far harder to miss than an email reminder.
Recipe 06: On-call rotation with escalation ladder
- Trigger: PagerDuty / Opsgenie alert
- Nodes: 7
- Build time: 30 min
This is the workflow that replaces a $50/user/month PagerDuty seat for small teams. n8n holds the rotation schedule in a Google Sheet, fires SMS to whoever is on-call this week, and escalates after 5 minutes of no acknowledgment.
Flow: Alert webhook → Read on-call sheet → HTTP Request to SMS8 (primary) → Wait 5 min → Webhook listener for ACK → IF no ACK → HTTP Request to SMS8 (secondary).
The ACK channel is the SMS8 webhook. The user replies "ACK" or "1" and that POSTs to the n8n Webhook trigger, which sets a flag in your database that the alert was claimed.
Recipe 07: Scheduled bulk SMS from a Google Sheet
- Trigger: Cron at scheduled time
- Nodes: 4
- Build time: 15 min
You want to send a 500-person update on Tuesday at 10am local time. n8n reads the sheet, throttles the sends so you do not hammer the SMS gateway, and writes back a "sent at" timestamp per row.
Flow: Cron (Tuesday 10:00) → Google Sheets Read → Loop with Wait (10 to 30 seconds between sends on each SIM) → HTTP Request to SMS8 → Sheets Update.
Always include a STOP instruction in bulk SMS even if you are not in the US:
{{ $json.firstName }}, our {{ $json.eventName }} starts Tuesday 10am.
RSVP: {{ $json.rsvpUrl }}
Reply STOP to opt out.
For bigger sends (5,000+) split across multiple paired phones using SMS8's device routing.
Recipe 08: Two-way auto-reply: STOP / INFO / HELP keywords
- Trigger: SMS8 webhook (inbound SMS)
- Nodes: 5
- Build time: 18 min
Once you send any volume of marketing or transactional SMS, you will get replies. STOP must work or you violate carrier rules. HELP must give a useful answer. n8n can handle both fully automatically.
Setup: in your SMS8 dashboard, create a webhook pointing at https://your-n8n.com/webhook/sms-inbound.
Flow: n8n Webhook trigger → Switch on uppercase trimmed body → cases for STOP, HELP, INFO → HTTP Request to SMS8 reply + write to your suppressions database.
// Switch node expression
const body = $json.body.data[0].message.trim().toUpperCase();
if (body === 'STOP' || body === 'UNSUBSCRIBE' || body === 'CANCEL') return 'stop';
if (body === 'HELP' || body === 'INFO') return 'help';
return 'default';
For STOP, write the phone to your suppression list and send a confirmation. Skip the next 24 hours of campaigns for that number. For HELP, send your support phone + email + business hours.
Recipe 09: Daily SMS digest of your business KPIs
- Trigger: Cron daily at 7:30am
- Nodes: 6
- Build time: 25 min
One SMS, every morning, on your lock screen. Three numbers and a delta. Better than a dashboard you never open.
Flow: Cron (7:30am) → Three parallel HTTP Requests (Stripe revenue, GA sessions, support tickets open) → Merge → Set node formats the message → HTTP Request to SMS8.
Yesterday at SMS8:
Revenue: ${{ $json.revenue }} ({{ $json.revenueDelta }})
Signups: {{ $json.signups }} ({{ $json.signupsDelta }})
Open tickets: {{ $json.tickets }}
Keep it to 160 characters so it stays a single SMS segment.
Recipe 10: AI-powered SMS responder for inbound questions
- Trigger: SMS8 webhook
- Nodes: 5
- Build time: 25 min
This is the workflow that makes 2026 n8n feel new. An incoming SMS hits a webhook, n8n passes the message to an OpenAI / Anthropic / Ollama node along with your business FAQ as context, the model writes a reply, n8n sends it back.
Flow: Webhook (SMS in) → Anthropic Messages node (with system prompt = your FAQ) → HTTP Request to SMS8 (send reply) → Append to Google Sheets log.
System prompt for the model:
You are a customer support agent for ACME Corp.
Reply ONLY based on the FAQ below.
If the question is not covered, reply: "Let me get a human, give me an hour."
Keep replies under 320 characters (two SMS segments).
FAQ:
- Office hours: 9am-6pm PT, Mon-Fri
- Refund policy: 30 days, no questions asked
- Shipping: 3-5 business days US, 7-14 international
- Returns: hello@acme.com with order #
{{ rest of your FAQ... }}
For escalation, branch on a "needs human" tag the model adds. If present, page the on-call human via Recipe 06.
Picking the right SMS gateway under n8n
n8n is gateway-agnostic. You can point the HTTP Request node at anything. The choice usually comes down to cost-per-SMS and how fast you want to be live.
| Gateway | Setup time | Per-SMS cost (US, as listed on their sites, November 2026) | n8n integration |
|---|---|---|---|
| SMS8 (Android phone + your SIM) | 3 min | $0 + $29/mo | HTTP Request node, no community node needed |
| Twilio | Days to weeks (10DLC vetting) | $0.0083 + carrier fees | Native Twilio node |
| Plivo | Days to weeks (10DLC vetting) | $0.0077 + carrier fees | HTTP Request |
| Telnyx | Days to weeks (10DLC vetting) | $0.004 + carrier fees | HTTP Request |
For steady workflow traffic, SMS8 is the cheapest and the fastest to get running; the Twilio alternatives comparison has the full price breakdown. For more volume, pair more phones and SMS8 spreads the workflow traffic across them.
Common gotchas
SMS arriving truncated
Anything over 160 GSM-7 characters splits into multiple segments. Some phones reassemble them, some show two separate messages. Keep transactional messages to one segment when possible.
Unicode (emoji, accented chars) drops the limit to 70 characters
The moment you include one emoji, the SMS shifts from GSM-7 to UCS-2 encoding and you can only fit 70 characters per segment. SMS8 will still send, just billed as multi-segment if you are on a per-segment carrier.
Rate limiting on bulk sends
SMS8 campaigns pace each SIM at one message every 10 to 30 seconds to stay carrier-safe. When you loop sends from n8n, keep a similar gap with an n8n Wait node, or split across multiple paired phones.
STOP must always work
Even outside the US, the moment you do any marketing-style SMS, "STOP" replies must remove that phone from future sends. Recipe 08 covers it. Do not skip it.
Wrap-up
The combination of n8n's visual flow and a $0-per-message SMS gateway is one of the cheaper, faster automation stacks you can build in 2026. Ten workflows above cover most of what teams actually do with SMS. Agencies running these for clients should read how agencies package SMS as a retainer, and WordPress shops the WordPress SMS plugin comparison. The pattern is the same in all of them: one HTTP Request node calling SMS8, optionally combined with a webhook trigger for two-way flows.
Start with Recipe 02 (production alerts). It is the highest leverage one and you will know in a week whether the stack pulls its weight. From there, abandoned cart and OTP recover their own setup time within a month.
The SMS8 side is set up in a few minutes from the Play Store install. n8n self-hosts in a Docker one-liner. There is no good reason not to ship one of these recipes this afternoon.
Why choose SMS8 for n8n SMS
SMS8 is the SMS node n8n is missing: one HTTP Request, your own number, no meter.
- Automations without code. Official Zapier and Make apps, an n8n HTTP Request node recipe, and a Google Sheets add-on all send through the same phone.
- Your own number. Texts leave from the SIM in your own Android phone, so customers see a number they know and can reply to.
- A flat price with unlimited messages. USD 29 a month for one phone or Mac, USD 89 for five and USD 229 for twenty, with unlimited SMS and MMS and no per-message fee. Yearly billing is half the price.
- A developer-friendly API.
POST https://app.sms8.io/api/v1/messageswith anX-Api-Keyheader, signed webhooks retried for up to 30 days, andnpm install sms8-sdkfor the SDK and thesms8CLI. - No A2P 10DLC filing. Texts go person-to-person from your SIM, so there is no brand, campaign or monthly campaign fee to manage.
Start the 3-day trial with 30 messages and no card, or compare plans on the SMS8 pricing page.