The Bird app is now listed in Zapier's directory, so a Zap can send over Bird's channels and read Bird's records without an HTTP block and without an API key. Search for Bird in the Zap editor, click Connect, and give consent in Bird. The connection is OAuth, and what Bird mints is owned by the workspace rather than by the person who clicked, so it keeps working after they change teams. Nothing asks you which region you are in either: the access token carries it.

## Actions

**Send Email**, **Send SMS**, and **Send WhatsApp Message** cover the channels, template or free-form. **Start Verification** and **Check Verification Code** run a one-time passcode end to end, so a Zap can send the code and confirm the one the recipient types back.

## The trigger

**New Event** starts a Zap from any of the 53 public Bird webhook event types: an email delivered or bounced, an inbound SMS, a WhatsApp send that failed, a sending domain that finished verifying. Pick the events you care about and Zapier registers the webhook endpoint for you. Every delivery is signature-checked before your Zap sees it, and one that fails the check is refused.

One limit is worth knowing before you build on it: a single Zap per organization can use New Event today. Zapier issues each Zap its own target URL, and Bird's webhook endpoint quota starts at one per organization, so a second Zap on this trigger comes back with `WebhookTooManyEndpoints` (as does the first, if you already run a webhook of your own). Support can raise that quota for your organization. Actions and searches are unaffected.

## Searches

43 search steps read the records back: email messages, their events, recipients, stored content and attachments; inbound email down to the raw MIME; SMS messages, events, templates, keyword rules and suppressions; WhatsApp messages, events and media; voice calls; sending domains and their events; SMTP configurations; webhook endpoints and their delivery attempts. Email and SMS statistics get one search each, returning counts and rates rather than per-message records.

A search that matches nothing returns no results instead of failing the run, so a Zap takes its own no-match path rather than erroring out.

## Managing the connection

Every connection shows up on the **Integrations** page in your Bird workspace, with the scopes it was granted. Revoking it there stops every Zap built on it.

[Find Bird in Zapier's directory](https://zapier.com/apps/bird/integrations) and build the first Zap.