Send iMessages from n8n
The short answer
Yes, you can send iMessages from n8n. n8n doesn't ship a native iMessage node, but Blue Reacher gives any workflow one: add an HTTP Request node pointed at the Blue Reacher API and your automation sends real blue-bubble texts from a dedicated iMessage line, no A2P registration required. Replies, opt-outs, and per-message delivery states come back through a standard Webhook node. B2B sales teams use it because iMessage gets read, and read messages turn into 2-3x more booked appointments.
Key takeaways
- iMessage is the thread B2B buyers actually read: blue bubble, read receipts, typing indicators, the place they text colleagues and family.
- Outbound: an HTTP Request node calls the Blue Reacher API and sends an iMessage.
- Most teams send their first workflow message within a week.
How a message falls back
Why do n8n teams switch their texting channel to iMessage?
iMessage is the thread B2B buyers actually read: blue bubble, read receipts, typing indicators, the place they text colleagues and family. Blue Reacher customers book 2-3x more appointments where a booking funnel is the motion from the same lists because the message looks like it came from a person.
- Second reason: A2P 10DLC. Blue Reacher requires no A2P registration, no brand vetting, no campaign approval, no carrier waiting. You get a dedicated iMessage line with unlimited sends (50 opted-in / 30 cold new contacts a day), and automatic RCS then SMS fallback.
What does the Blue Reacher n8n integration actually do?
Outbound: an HTTP Request node calls the Blue Reacher API and sends an iMessage. Inbound: replies, delivery states, and opt-outs post back to a Webhook node, so follow-up logic can be triggered by a prospect texting back.
- Personalize with n8n expressions: {{ $json.firstName }} works exactly as expected. It runs on n8n Cloud and self-hosted n8n identically. If you're building AI agents in n8n, Blue Reacher ships an MCP server for agents to send and read texts as a tool.
How it sends
- Texting from n8n today
- Twilio node, Send SMS/MMS/WhatsApp message
- With Blue Reacher
- HTTP Request node calling the Blue Reacher API
What prospects see
- Texting from n8n today
- Green SMS from an unfamiliar 10-digit number
- With Blue Reacher
- Blue-bubble iMessage from a dedicated line
Registration
- Texting from n8n today
- A2P 10DLC brand and campaign registration before sending
- With Blue Reacher
- No A2P registration required
Volume
- Texting from n8n today
- Per-segment pricing plus carrier filtering
- With Blue Reacher
- Unlimited iMessages (50 opted-in / 30 cold new contacts a day) per line, RCS then SMS fallback
Replies and opt-outs
- Texting from n8n today
- Build your own inbound handling
- With Blue Reacher
- Replies, delivery states, and STOP opt-outs post to your Webhook node
Rich content
- Texting from n8n today
- MMS attachments
- With Blue Reacher
- Photos, video, voice memos, tapbacks, group messaging
Outcome
- Texting from n8n today
- Reply rates you apologize for
- With Blue Reacher
- 2-3x more booked appointments
How long does setup take?
Most teams send their first workflow message within a week. One onboarding call covers implementation and message intent. Your dedicated line is stood up and API credentials drop into an n8n credential like any other service.
- $249 per line per month, unlimited iMessages, or $1,949 per year (about $162.50/month with activation waived). Lines pace at 50 opted-in / 30 cold new contacts a day; replies never metered.
- One onboarding call: implementation consultation plus message intent configuration
- Dedicated iMessage line, managed for you, sending within a week for most teams
- $249 per line per month, unlimited iMessages (50 opted-in / 30 cold new contacts a day), $449 activation waived on annual billing
- Optimization check-ins after launch so results climb instead of flatten
Frequently asked questions
Does n8n have a native iMessage node?
No. n8n lists 500+ integrations, and none of them send iMessage. Blue Reacher fills the gap with its API: an HTTP Request node sends blue-bubble texts, and a Webhook node receives replies, delivery states, and opt-outs. From your workflow's point of view it behaves like any other node pair.
Can I send texts from n8n without Twilio or A2P registration?
Yes. Blue Reacher requires no A2P registration, no brand vetting, no campaign approval, no carrier waiting. You get a dedicated iMessage line with unlimited messages (50 opted-in / 30 cold new contacts a day), and automatic RCS then SMS fallback for contacts who can't receive iMessage.
Does this work with self-hosted n8n?
Yes. Self-hosted n8n and n8n Cloud work identically here. The integration needs two things: outbound HTTPS from your instance to the Blue Reacher API, and a webhook URL Blue Reacher can reach for inbound events. If your self-hosted instance already receives webhooks from other services, you're set.
How do replies and delivery states get back into my workflow?
Through a standard Webhook node acting as your trigger. Blue Reacher posts every inbound reply, delivery state, and STOP opt-out it detects automatically. Branch follow-up logic on real signals: route hot replies to an AE, pause sequences on opt-out.
What does Blue Reacher cost for an n8n setup?
$249 per line per month, unlimited iMessages, or $1,949 per year (about $162.50/month with activation waived). Lines pace at 50 opted-in / 30 cold new contacts a day; replies never metered. The n8n side costs nothing beyond your existing instance.
See it running on your n8n account
Book a demo and bring your n8n instance. We'll wire a live workflow on the call: an HTTP Request node sending a real blue-bubble text to your phone, with the reply landing back in your Webhook node seconds later. White-glove setup, public pricing, and most teams are sending within a week.