> 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.

# Set up the Zapier MessageBlue Integration

Setting up takes four stages: get your credentials from MessageBlue, connect the account once in Zapier, build a Zap, then publish it. You only do the first two once — every later Zap reuses the same connection.

## 1. Get your credentials

Connecting requires **two values** from MessageBlue.

| Credential        | What it is                                     | Where to find it                                                           |
| ----------------- | ---------------------------------------------- | -------------------------------------------------------------------------- |
| **App ID**        | Your unique MessageBlue application identifier | [Settings → Zapier CRM](/settings#zapier-crm)                              |
| **Zapier Secret** | A dedicated password for Zapier connections    | [Settings → Zapier CRM](/settings#zapier-crm) → **Generate Zapier secret** |

You do **not** need an Account ID. The Zapier CRM tab displays one for reference, but Zapier's connection form asks only for App ID and Zapier Secret — MessageBlue resolves your account from the App ID automatically. Pasting an Account ID where the secret belongs is a common cause of a failed connection test.

#### Open Settings → Zapier CRM

Log in to the MessageBlue web app, open **Settings** from the left rail, and select the **Zapier CRM** tab.

#### Copy your App ID

Use the copy button next to the value.

#### Generate the Zapier secret

Click **Generate Zapier secret** — or **Regenerate Zapier secret** if one already exists. If regenerating, confirm the action.

#### Copy the secret immediately

When the secret appears, click **Copy secret** and store it in a password manager.

The Zapier secret is **shown only once**. The field afterwards reads *"Secret on file — regenerate to reveal a new value"* — there is no way to view it again. Losing it means regenerating, which breaks every existing connection until you update them.

## 2. Connect MessageBlue in Zapier

You connect once and reuse that connection across every Zap.

#### Start a Zap

Sign in at [zapier.com](https://zapier.com), click **Create**, then **Create Zap**.

#### Choose MessageBlue as the trigger app

Search for **MessageBlue** in the app search box and select it. Choose the trigger event — **New Inbound iMessage** — and click **Continue**.

#### Sign in to MessageBlue

Under **Choose account**, click **Sign in to MessageBlue** (or **Connect a new account**). A connection form appears with two fields:

* **App ID** — paste the App ID from Settings → Zapier CRM
* **Zapier Secret** — paste the secret you copied

#### Test the connection

Click **Yes, Continue to MessageBlue** (or **Test & Continue**) and wait for the green checkmark, then **Continue**.

If the test fails, the overwhelmingly common cause is a **stray space** copied along with a value. Check both fields before anything else, then see [troubleshooting](/zapier-messageblue-integration-troubleshooting).

## 3. Build your first Zap

A good starter Zap: when an iMessage arrives, reply to it automatically.

### Part A — the trigger

#### Configure the trigger

In the Zap editor, select **MessageBlue** → **New Inbound iMessage** → **Continue**, then pick your connected account and **Continue** again.

#### Test the trigger

Click **Test trigger** to fetch a recent inbound message, review the result, select a real record if one is offered, then **Continue with selected record**.

The test pulls recent inbound messages so you can preview the fields — sender, text, timestamp — that later steps can use.

If you see placeholder data with the ID **`sample_123`**, no recent inbound messages were found for your account. That is expected on a quiet number, and you can still finish setup — just send a real message once the Zap is live to confirm it works end to end.

### Part B — the action

#### Add the action step

Click **+** below the trigger, search for **MessageBlue**, choose **Send iMessage**, and select the same account connection.

#### Map the fields

* **To** — click the field and pick **From Phone** from the trigger step, so the reply goes back to whoever messaged you
* **Text** — your reply, e.g. *"Thanks for your message! We will get back to you shortly."*
* **From** *(optional)* — leave blank to use your default number, or enter a specific number you own

#### Test the step

Click **Test step**. This sends a **real** iMessage — use a number you can check.

**Test action sends a genuine message.** Unlike the trigger test, which only reads data, testing the action delivers an actual iMessage to whatever number is mapped into **To**. Point it at your own phone the first time.

### Part C — name it

Click **Untitled Zap** at the top-left and give it something descriptive, e.g. *"MessageBlue — Auto Reply to Inbound iMessages"*. Press Enter.

## 4. Publish and turn it on

A Zap only runs when it is **published and ON**. Draft Zaps and test-only setups do not process live messages — this is the single most common reason a working setup "does nothing".

#### Publish

Review both steps and click **Publish** in the bottom-right.

#### Turn it on

Click **Publish & Turn On**, then confirm the Zap shows **ON** (green) in your Zaps list.

#### Verify live

Send a real iMessage to your MessageBlue number from another phone, wait a few seconds, then open **Zap History** in Zapier's left sidebar and confirm the run succeeded.

### What turning it on actually does

Switching a Zap ON registers a **webhook** with Zapier. From that point, every inbound iMessage triggers the Zap. Turning it OFF or deleting it removes that registration and the Zap stops.

This is why reconnecting an account requires a toggle: if you disconnect and reconnect MessageBlue in Zapier, turn the Zap **OFF and then ON again** so the webhook is re-registered against the new connection. Skipping this leaves a Zap that looks enabled but never fires.

## Rotating your Zapier secret

Rotate the secret if it may have been exposed, or on whatever schedule your security policy sets.

#### Regenerate in MessageBlue

**Settings → Zapier CRM → Regenerate Zapier secret**, confirm, and copy the new value immediately.

#### Update every Zapier connection

For each Zap using MessageBlue: open the MessageBlue step → click the account name → **Reconnect**. Paste the new secret. The **App ID stays the same**.

#### Toggle each Zap

Turn each affected Zap **OFF, then ON** again.

Regeneration takes effect **immediately** and there is no grace period — the confirmation says so: *"The current Zapier secret stops working immediately. Any active Zaps using it will fail until you update the connection."* Rotate when you have time to update every Zap, not at the end of the day.