# Automate Bird from Zapier

Connect once with OAuth and Bird's five actions, 43 searches and event trigger are available to every Zap. There is no API key to paste and no region to pick: the connection carries both.

## Connect once, not per Zap

Consent mints a workspace-owned Integration rather than a personal one, so the connection outlives whoever authorized it. Endpoint management rides on user-role scopes, which is what makes the trigger possible at all.

**Zapier editor**

Add a Bird step → Connect → Sign in to Bird

- Consent screen: Zapier wants access to your workspace
- Connection name: Bird (Acme Production · eu1)

The connection names itself after your workspace and region, which is how you tell two apart.

**what the app exposes**

- Actions: Send Email, Send SMS, Send WhatsApp Message, Start Verification, Check Verification Code
- Searches: 43, over the public read surface
- Trigger: New Event, 48 event types

**Zapier editor**

Trigger → Bird → New Event → Pick events

- Per Zap: one webhook endpoint
- Org quota: 1 endpoint by default

Past the quota the create fails with WebhookTooManyEndpoints. Ask support to raise webhook_subscriptions_max.

## What a Zap can do with Bird. The channels the app sends over, plus the reads behind them. Mailbox, Realtime, number provisioning and contacts are separate products and are not in this app.

- Send on any channel. Email, SMS and WhatsApp each have their own action. A send is accepted, not delivered, so pair it with a search or the trigger to know it landed.
- Verify a number. Two actions, one to send the code and one to check it, so a signup flow fits in a single Zap.
- Start on a Bird event. 48 event types, from a delivery to a bounce to an inbound message. Every delivery is signature-verified, and one that will not verify is refused.

### Zaps worth building

- Email a confirmation when a form is submitted.
- Text the customer when an order moves to shipped.
- Verify a phone number before creating the account.
- Log every bounce to a spreadsheet, with the reason.
- Open a ticket when an inbound message arrives.
- Post yesterday's email statistics to a channel each morning.