> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.messageblue.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.messageblue.ai/_mcp/server.

# Zapier MessageBlue Integration

MessageBlue lets you send and receive iMessages from your business workflows. With the Zapier integration you can connect MessageBlue to over **7,000 apps** — HubSpot, Google Sheets, Slack, Airtable and the rest — without writing any code.

A **Zap** is an automated workflow in Zapier. When someone sends you an iMessage, a Zap can log them in your CRM, alert your team in Slack, and text them back — automatically.

#### [Set it up](/zapier-messageblue-integration-setup)

Get your credentials, connect Zapier, and build your first Zap step by step.

#### [Something not working?](/zapier-messageblue-integration-troubleshooting)

Every error the connection can return, what causes it, and the fix.

## What you can do

The integration provides one trigger and one action. Together they cover both directions of a conversation.

#### New Inbound iMessage

**Trigger.** Fires when a new iMessage arrives at your MessageBlue number, giving later steps the sender, text, timestamp and attachments.

#### Send iMessage

**Action.** Sends an outbound iMessage to a phone number from any Zap, optionally from a specific one of your numbers.

Because MessageBlue can be both the trigger *and* an action in the same Zap, a complete two-way workflow — receive, process, reply — is a single Zap.

## Before you begin

#### An active MessageBlue account with a connected number

You need at least one iMessage-enabled phone number connected through the [MessageBlue Mac agent](/concepts#numbers-devices-and-the-mac-agent).

#### A Zapier account

Free or paid. Sign up at [zapier.com](https://zapier.com) if you do not have one.

#### Admin access to MessageBlue Settings

Credentials are generated in [Settings → Zapier CRM](/settings#zapier-crm), which requires access to your app's settings.

Your **Mac agent must be online** for outbound messages to send and for inbound messages to arrive in real time. A Zap that tests fine but never fires live is very often an offline agent — check the green **Online** indicator on your [dashboard](/dashboard#phone-numbers).

## Trigger reference

### New Inbound iMessage

Fires when a new iMessage is received on your MessageBlue-connected number. These fields are available to every later step in the Zap:

| Field                   | Description                                    |
| ----------------------- | ---------------------------------------------- |
| **From** / From Phone   | The phone number that sent the message         |
| **To**                  | Your MessageBlue number that received it       |
| **Text** / Message Text | The content of the message                     |
| **Timestamp**           | When the message was received (Unix timestamp) |
| **Message GUID**        | Unique identifier for the message              |
| **Chat GUID**           | Unique identifier for the conversation         |
| **Attachments**         | List of attachments, if any                    |

**Chat GUID** is the field to use when you need to group messages into a conversation in the destination app — **Message GUID** is unique per message and changes every time.

## Action reference

### Send iMessage

Sends an outbound iMessage through MessageBlue.

| Field           | Required | Description                                                                         |
| --------------- | -------- | ----------------------------------------------------------------------------------- |
| **To**          | Yes      | Recipient phone number in E.164 format, e.g. `+15551234567`                         |
| **Text**        | Yes      | The message body to send                                                            |
| **From**        | No       | Which of your MessageBlue numbers to send from. Leave blank for automatic selection |
| **Attachments** | No       | Optional file attachments                                                           |

Phone numbers must be entered in **E.164 format** — a leading `+`, the country code, then the national number, with no spaces, dashes or brackets. For example `+15550109988`. The app rejects anything else before it reaches the gateway.

## Example use cases

#### Auto-reply

Send an instant acknowledgement when someone texts your business number.

#### CRM logging

Create or update a contact in HubSpot, Salesforce or another CRM when an iMessage arrives.

#### Team notifications

Post inbound message details to a Slack channel so your team sees them.

#### Lead capture

Append the sender's number and message to a Google Sheet or Airtable.

#### Follow-up sequences

Trigger a multi-step Zap that sends a timed iMessage reply after an inbound message.

#### Two-way workflows

Receive an iMessage, process it in another app, then reply — all in one Zap.

## How it relates to the rest of MessageBlue

Zapier is one of three ways to work with your messages. They are complementary, not alternatives:

| Route                                    | Best for                                                           |
| ---------------------------------------- | ------------------------------------------------------------------ |
| **Zapier**                               | Connecting to other SaaS tools with no code                        |
| **[Webhooks + API](/settings#webhooks)** | Your own server, full control over payloads and retries            |
| **[AI Agent](/ai-agent-studio)**         | Replying automatically in natural language from your own knowledge |

A Zap and the AI agent can both be active at once. If the agent is deployed it answers the customer, while your Zap logs the conversation elsewhere — they do not conflict, but do check you are not sending two replies to the same message.

Ready to build one? Continue to [setting up Zapier](/zapier-messageblue-integration-setup).