What’s new.
What’s next for you.

You can now connect your Bird account to Vercel and let the integration set up your API credentials. It creates a Bird API key and saves it with your workspace's regional API endpoint in your selected Vercel projects, so you don't have to copy either value between dashboards.

During setup, choose your Bird workspace, Vercel projects, and Preview or Production environment. Bird saves BIRD_API_KEY and BIRD_API_BASE_URL as encrypted environment variables. Finish the installation in Vercel, then redeploy your app to use them.

Connect Bird to Vercel.

Verify can now send passcodes from an SMS Sender ID or WhatsApp number in your workspace. Choose a sender for each channel on Configure > Channels, then override it for a destination on the Countries page. Your verification requests do not change.

For SMS, select an existing Sender ID that is registered and permitted for authentication messages in the countries you serve. If your default Sender ID cannot be used in a destination country, Verify sends from Bird Verify there instead. A Sender ID selected for a specific country does not get that sender fallback; if it cannot send, Verify moves to the next channel in the verification plan.

For WhatsApp, select a connected number and an existing approved authentication template from its WhatsApp Business Account. Verify inserts the passcode into that template. You can manage numbers, Sender IDs, and templates from the sender menus in the dashboard.

Senders and branding explains the requirements and fallback behavior. Country configuration shows how to set a destination-specific sender.

Your organization can now set up single sign-on. Members sign in through your own identity provider instead of keeping a separate Bird password, and you decide whether that is optional or required.

Setup runs from the Single sign-on page on your organization. Verify an email domain by DNS record, configure a SAML 2.0 or OpenID Connect connection, run a test sign-in against your provider, and activate it. A connection can grant new members a default role on their first sign-in, so someone arriving from your directory lands with the access you intended rather than none.

Turning on the requirement takes effect immediately, on every request. A member whose current session did not come through your identity provider signs in again through it, so plan the change around your team's day. Organization Owners keep access with their Bird password, which is what stops a misconfigured connection locking everyone out.

Credential rotation, suspend and resume, and deletion are all in the surface, and every one of those actions is recorded in your audit log.

The field names differ in each provider, and each has one setting that refuses every sign-in when it is wrong, so start from the guide for yours:

• Set up SSO with Okta
• Set up SSO with Google Workspace
• Set up SSO with Microsoft Entra ID

SSO and provisioning covers the parts that are the same whichever provider you use.

Bird is now an approved app in Attio's app directory. Install it to send messages and see recent messaging activity alongside your CRM records.

Send SMS and email from a person record, or choose recipients from the people associated with a company or deal. To reach several people at once, select their records and compose a message to send to each recipient.

In Attio Workflows, add Bird steps to send SMS, WhatsApp, and email. Use messaging events to start a workflow when a message arrives, delivery succeeds or fails, or a recipient opens or clicks an email. Add the Bird conversation widget to a person record to see recent messaging activity and delivery status, including messages sent through other Bird tools.

To connect the app, you'll need an Attio workspace admin and a Bird workspace configured for the channels you want to use. After connecting, set your default senders in the app's settings and select Test connection.

Install Bird in Attio.

Our official Bird node is now verified by n8n. Send email, SMS, and WhatsApp messages, manage contacts, and run verification steps directly from your workflows.

A form submission can send a welcome email. An order update can send an SMS using a template stored in Bird. Choose a resource and operation in the Bird node, then map data from an earlier step into its fields. You can also look up message delivery status and use the result in the next step.

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

Install the Bird node

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.

Once installed, create an API key under API keys in the Bird dashboard, with the scopes your workflow needs. Paste it into a Bird API credential in n8n.

For installation settings, see n8n's verified-node guide.

Send a test email

Select your Bird API credential, set Resource to Email, and choose Send. Under Additional Fields, add Subject and Text, then fill in:

Field	Value
From	onboarding@messagebird.dev
To	delivered@messagebird.dev
Subject	Your workflow is connected
Text	This message was sent through Bird from n8n.

Execute the node. A successful response includes a message ID. This example uses Bird's shared onboarding sender and a sandbox recipient that simulates delivery without sending to a real inbox. The first-email guide explains how to check the result and the onboarding sender's limits.

To email customers, verify your sending domain and use an address on that domain in From.

Build your workflow

• Follow the Bird setup guide for configuration and supported resources.
• Import the welcome-email workflow to connect a form submission to an email.
• Try the order-shipped workflow to send an SMS from a stored template.