How to Send iMessage from n8n: The 2026 Automation Guide

Everything here uses Blooio, an iMessage API that manages the Apple side for you. There's no Mac mini to babysit, and because iMessage rides Apple's network, there's no A2P/10DLC registration, no DUNS number, and no campaign approval to wait on.

What you'll build

A single, practical workflow you can adapt to almost anything:

1. A trigger fires (a new CRM lead, a form submission, a scheduled time).
2. n8n checks whether the number can receive iMessage.
3. It sends a personalized blue-bubble iMessage — with a typing indicator for a human touch.
4. When the contact replies, a webhook pushes the message back into n8n so you can route it to your CRM or an AI node and reply automatically.

Prerequisites

• An n8n instance — n8n Cloud or self-hosted (v1.60+ for the community node).
• A Blooio account and an API key from Settings → API Keys in the dashboard. No credit card required to start.
• A phone number you can test against (your own phone is fine).

Option A: The native Blooio node (recommended)

Blooio ships an official community node, n8n-nodes-blooio, that's built by Blooio and verified by n8n. It exposes messages, chats, contacts, reactions, polls, typing indicators, and webhooks as first-class n8n operations — so you get dropdowns and autocomplete instead of hand-rolled HTTP calls.

1. Install the node

In n8n, go to Settings → Community Nodes → Install, enter n8n-nodes-blooio, and confirm. Because it's an n8n-verified node, an instance owner does this one-time setup and then everyone on the instance can use it. (See n8n's community node installation guide if you're self-hosting behind a proxy.)

2. Add your API key credential

Create a new Blooio API credential and paste the API key from your dashboard. n8n stores it encrypted and reuses it across every Blooio node in your workflows.

3. Send a message

Add a Blooio Messaging node, choose Resource: Message and Operation: Send, then set:

• Chat — the recipient, as an E.164 phone number (+15551234567), an email, or a group ID. The node URL-encodes it for you.
• Text — your message body. Drop in expressions like Hi {{ $json.firstName }}, thanks for booking! to personalize from earlier nodes.
• Options — optionally turn on Show Typing Indicator, set an Idempotency Key to prevent duplicate sends on retries, or attach a send-with-effect like confetti.

Execute the node and you'll get back a message_id and a status of queued — the iMessage is on its way.

Option B: The HTTP Request node (works anywhere)

Every Blooio operation is a normal REST call, so you can do all of this with n8n's built-in HTTP Request node — no community node required. This is the way to go on n8n Cloud or in tightly governed environments.

Configure an HTTP Request node like this (note the %2B — the + in the phone number must be URL-encoded, which is the single most common cause of a silent 400):

The response is a 202 Accepted:

Check capability before you send (iMessage vs SMS)

Not every number is on iMessage. If you want blue bubbles with a clean SMS fallback, check capability first with the Contact → Check Capabilities operation (or a GET to the contacts capabilities endpoint), then branch with an IF node: iMessage-capable numbers get the rich blue-bubble path, everyone else routes to your SMS provider.

Receiving replies: the inbound webhook

Sending is half a conversation. To build a two-way flow, register a Blooio webhook that points at an n8n Webhook node. Create the subscription once (via the Blooio node's Webhook → Create operation, or a POST /webhooks) with your n8n production webhook URL and a type of all.

From then on, every inbound message arrives at your n8n Webhook node as JSON:

external_id is the contact's number and text is what they said — everything you need to thread the reply into your CRM, tag the contact, or hand off to an AI node. Other events you can act on include message.sent, message.delivered, message.read, and message.failed.

Add AI: a blue-bubble agent in n8n

This is where n8n shines in 2026. Take the text from the inbound webhook, feed it into an AI/LLM node (OpenAI, Anthropic, or n8n's AI Agent node) with your product context, then pipe the model's answer straight back into a Blooio Send node aimed at the same external_id. In about five nodes you've built an iMessage AI agent that qualifies leads, books appointments, or answers FAQs — all in blue bubbles. For deeper patterns, see our guide on building an iMessage AI bot.

Production gotchas worth knowing

• URL-encode the phone number. +15551234567 becomes %2B15551234567. This bites everyone exactly once.
• Use idempotency keys. Pass a key derived from your domain entity (e.g. order-123-shipped) so an n8n retry never double-sends.
• Don't build your own rate limiter. Blooio queues and paces outbound sends to protect the underlying number — you don't need a Wait node throttling your workflow.
• Warm new numbers up. Start with low volume and real conversations before scaling cold outbound, exactly as you would with any messaging channel.
• Fall back gracefully. If a number isn't on iMessage, route to SMS instead of assuming a blue bubble.