Rilasciati di recente.

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.

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 and build the first Zap.

The messaging preference store is now a public API. Preferences are stated consent grants and opt-outs, keyed by channel and handle (an email address or phone number), and they already decide delivery for every send: an opt-out blocks marketing traffic, and one recorded for all messages blocks transactional traffic too.

What's new

• GET/POST /v1/preferences and GET/DELETE /v1/preferences/{preference_id} are available to API keys carrying the new preferences scope. Recording a grant with consented_at evidence is also the documented way to resume mailing someone after an unsubscribe.
• The bird preferences CLI group and matching MCP tools cover the same operations, and all four SDKs gain a preferences resource with typed results.
• Four webhook event types are now public: preference.granted, preference.revoked, preference.deleted, and whatsapp_suppression.created. Each fires only when a statement actually changes a record.

Statements are ordered by when they were made rather than when they arrive, so an out-of-order write answers applied: false with the surviving statement instead of applying. A statement the recipient made themselves, such as an unsubscribe or a stop keyword, cannot be deleted through the API; it ends only when they opt back in.

Read more in the webhooks guide and the API reference.