Zapier MessageBlue Integration Troubleshooting
Connection errors
These come back from MessageBlue when Zapier tests or uses the connection. Match the code or the wording Zapier shows you.
ZAPIER_SECRET_NOT_CONFIGURED is the one new users hit most: it means the App ID is correct but you skipped generating the secret. It is a setup step, not a failure — the message even tells you where to go.
Symptoms
Test Trigger shows only sample data (sample_123)
No recent inbound messages were found for your account, so MessageBlue returned a placeholder record so you can continue setup.
Send a real iMessage to your MessageBlue number, wait a moment, then click Find new records in Zapier and test again. If it still shows sample_123 after a genuine inbound message, check that your credentials belong to the app that owns the receiving number.
Outbound test works but the inbound trigger never fires live
Two likely causes, in order:
- The Zap is in Draft or OFF. Testing a step is not the same as running a Zap. Publish it and confirm the status shows ON (green).
- The Mac agent is offline. Inbound messages cannot reach MessageBlue at all if the device behind your number is disconnected. Check the Online indicator on your dashboard.
The Zap worked before and stopped
Almost always a regenerated secret. Every existing connection keeps using the old value and fails.
Update the connection with the new secret, then turn the Zap OFF and ON so the webhook re-registers. See rotating your secret.
Messages send slowly or fail
Outbound iMessages are delivered by your Mac agent, so they depend on it being running and connected. Check the device in Analytics → Agents — status should read online.
I reconnected the account and now nothing triggers
Reconnecting creates a new connection, but the existing webhook registration still points at the old one. Turn the Zap OFF and then ON to re-register it.
I cannot find MessageBlue in Zapier's app search
Search the full name MessageBlue — one word, no space. If it still does not appear, you may be looking at a Zapier account that is restricted by an admin policy; try from a personal Zapier account to confirm, then ask your Zapier administrator.
Frequently asked questions
Do I need to enter an Account ID?
No. Only App ID and Zapier Secret. MessageBlue resolves your account from the App ID. The Account ID shown in Settings is for reference and support, not for the Zapier connection form.
Do I need a paid Zapier plan?
Zapier’s free plan works, with a limited number of tasks per month. MessageBlue triggers and actions count toward that allowance. See zapier.com/pricing for current limits.
Can I connect more than one MessageBlue account?
Yes. Create a separate Zapier connection for each MessageBlue app, using that app’s own App ID and Zapier Secret pair.
Can MessageBlue be both the trigger and the action in one Zap?
Yes, and it is the most common pattern: receive an iMessage, process it in another app, then send a reply.
What phone number format should I use?
E.164, with the country code — +15551234567. See the format note.
How quickly do inbound messages trigger a Zap?
Typically within a few seconds, depending on Mac agent connectivity and Zapier’s own processing time.
What happens if I delete my Zap?
The webhook registration is removed and inbound messages no longer trigger it. Other Zaps on the same connection are unaffected.
Does the AI agent still reply if I have a Zap running?
Yes — they are independent. If your agent is deployed it answers as normal while your Zap runs alongside it. If you also send a reply from the Zap, the customer receives two messages.
Getting help
For credentials, account linking, and connection problems.
For general Zapier questions about Zaps, tasks and plans.
When contacting MessageBlue support, include:
- Your App ID — never your Zapier Secret
- A description of what you expected and what happened
- Any error message or code shown in Zapier
- Whether it fails during testing or on a live Zap
Never paste your Zapier Secret into a support ticket, email or chat. Support never needs it, and sharing it means it must be regenerated — which breaks every Zap using it.