How do I use Bird from a low-code tool like n8n or Zapier?

A form submission can trigger a confirmation email without a custom service. The workflow still needs to handle a bounce that arrives after its send step finishes.

How do I connect Bird to n8n?

Install Bird's verified node from the nodes panel on n8n Cloud or a self-hosted instance with verified community nodes enabled.

1. Create a new workflow.
2. Open the nodes panel by selecting + or pressing Tab.
3. Search for Bird.
4. Select Install to install the node for your instance.
5. The Bird node is now available in your workflows.

For self-hosted n8n, match the runtime requirements before installing. If community nodes are unavailable in the panel, open Settings > Community Nodes > Install. Enter @messagebird/n8n-nodes-bird as the package name.

Create the key under API keys in the Bird dashboard. Add a Bird API credential in n8n containing that workspace API key.

Grant the scopes listed by the credential for your selected operations, so the workflow can make those requests.

Select a resource and operation in the Bird node. It supports email, SMS, WhatsApp and verification, alongside setup and reporting operations.

The node excludes Realtime publishing and subscriptions because its credential cannot hold the required app key and secret.

Byte downloads and redirect-based media fetches are also excluded. The node expects JSON results for workflow items. Use an appropriate client or HTTP request for those operations.

How do I connect Bird to Zapier?

Select Bird in Zapier. Click Connect. Authorize the connection in Bird.

Zapier stores the OAuth connection, so you do not paste an API key. The connection belongs to the workspace and survives the authorizing person changing teams.

Manage its access on the workspace's Integrations page. Revoking the connection stops the Zaps that use it.

Choose Send Email, Send SMS or Send WhatsApp Message for a send step. Start Verification and Check Verification Code handle passcode verification.

Search steps retrieve messages and their events. The Zapier integration describes the available actions and searches.

How do I start a workflow from a delivery event?

Use Bird Trigger in n8n or New Event in Zapier. Select the events your workflow needs.

The integration registers a webhook endpoint for the workflow. It checks delivery signatures before passing events into your automation.

Each event-triggered workflow needs its own endpoint. Bird's endpoint quota starts at one per organization, so an existing webhook can prevent another trigger from being created.

Ask support to raise the quota before adding more event-triggered workflows. Send actions and searches do not each need their own webhook endpoint.

What does a successful send step prove?

It proves that Bird accepted the send request. It does not establish the later delivery outcome.

Store the returned message ID. Use delivery and failure events to update the record that triggered the send.

A WhatsApp free-form message can fail if the customer service window closes before dispatch. That later failure arrives after the send step succeeds. Use an approved template when messaging outside the customer service window.

n8n's Bird node sends a stable Idempotency-Key for each operation, so a workflow retry does not send twice. Zapier sends no idempotency key, so a platform replay can duplicate a send.

When should I use low-code or write a service?

Use low-code when sending belongs to a process already managed by your workflow tool. Use a service when you need to own durable retry and delivery state.

An n8n email or SMS batch can queue up to 100 messages in one call. A 250-message job takes three calls when grouped, rather than 250 individual requests.

For a tool without a Bird integration, use its HTTP block. Import Bird's OpenAPI spec if the tool supports client generation from it.

1. n8n: configure the Bird node with a workspace API key.
2. Zapier: authorize the Bird app. Select its actions or event trigger.
3. HTTP block: supply the request details when no Bird integration exists.
4. Custom service: own the stored delivery state and retry policy yourself.