Route Bird customer messages to a webhook routine

How this helps you

Customer messages trigger the Bot instantly instead of waiting for a schedule, and you still approve what goes out.

✦ Try it

Create a webhook routine for incoming [Apple Messages / mailbox emails] from Bird. For each event, read the message, look up the customer in [where you keep customer info], and save a reply as a draft in Bird. Never send a reply, refund or booking change without my approval. Tell me the webhook URL and sender key when it's ready.

Fill in: [Apple Messages / mailbox emails] is the channel you connect. [where you keep customer info] could be a sheet, Shopify or your CRM.

What they did

Bird (formerly MessageBird) announced a Grok Bot plugin and published a setup page. You add the Bird plugin and connect it in your browser, with no API key. Then you ask Grok Bot to create a webhook routine, copy its webhook URL and sender key, and paste them into a Grok Bot webhook in Bird that fires on incoming Apple Messages for Business or mailbox emails. Their examples are a booking desk on Apple Messages and an email support desk where replies are saved as drafts by default. Grok Bot's changelog confirms that a webhook routine receives the request body and that its menu shows the URL and key.

Who it's for: Businesses that already use Bird for customer messaging and want a Bot drafting replies the moment a message arrives.

Before you start

A Bird account with Apple Messages for Business or a Bird mailbox set up.
Permission to add plugins in Grok Bot (on a team, your admin may need to allow it).
A Bot that owns customer replies, with your tone and policies in its description.

How to try it

In Grok Bot, open Connect apps, find Bird in the Marketplace and connect it in your browser.
Ask the Bot for a webhook routine using the prompt below.
Open the routine's menu and copy the webhook URL and sender key.
In Bird, create a Grok Bot webhook for incoming Apple Messages or mailbox emails and paste in the URL and key.
Send a test event from Bird and check the routine ran.
Read the first drafts closely before letting anything send.

What to expect

Bird's page shows an Apple Messages booking desk and an email support desk with draft replies, plus prompts like writing a welcome email, auditing a sending domain and checking delivery failures.

Common mistakes

Letting replies send on day one. Bird's own support example saves drafts by default; keep it that way until you trust it.
Sharing the sender key in chat or a doc. Anyone with the URL and key can wake the routine.
Pointing every message type at one routine. Busy channels add up against the 200 runs an hour limit per routine.

Related tips

Make routines cheaper: events, slow schedules, change checks: A 5-minute routine wakes 8,640 times a month. Use an event trigger, the slowest schedule that works, and a cheap change check.
How the team uses its own Bot on support: It spots incidents and answers related tickets; a human approves the batch.
Triage and reply to email from the chat: Ask for a brief of emails that need replies, then answer them in one line each.
Forward new leads to your Bot's inbox: A Gmail filter forwards leads to a tagged Bot address; a routine on that tag researches each one before you reply.
From support form to fix: a webhook, a Bot and a Cursor cloud agent: A support form posts to a webhook, a Bot picks up the ticket, and for bugs it starts a Cursor cloud agent that reproduces the issue, adds a failing test and opens a pull request for an engineer to review.
Route every meeting transcript to the right Bot with a webhook: When your note taker finishes a call, a webhook wakes your Chief of Staff Bot, which reads the transcript and hands it to the Bot that owns that work.