Connect Bird to the workflows you run in n8n. React to a delivery event, protect the recipient and inspect the result before the next customer message.
Use the verified Bird node maintained by Bird. An instance owner or admin installs it when instance settings permit; an installed node still needs a scoped Bird API credential.
Use the plus control to find Bird. Members can use a node after an owner or admin installs it.
The Bird API credential owns the key. Its workspace read test does not establish permission for every operation.
Event subscriptions need webhooks permission; reading suppressions needs email_management:read. Check the current node fields and scopes.
Illustrative workflow. Inspect the result, then follow the setup below to run your own task.
A signed bounce arrives for reader@example.com. Inspect its classification and existing suppression records, then save the observed reason and category policy in your application.
Event: email.bounced · fictional signed delivery
Classification: hard bounce
Suppression read: existing automatic record
reason: hard_bounce · applies_to: all
Application finding: saved with source references
Manual suppression: not added
Illustrative task completed: the workflow reads Bird’s existing automatic suppression and saves its policy in the application. Bird already handles hard-bounce suppression. Preserve the original reason and message/recipient references; a manual addition would be a separate all-category restriction.
Read the maintained suppression policy ↗Inspect the original recipient’s terminal soft-class bounced outcome and the current suppression list without adding a manual restriction or sending a new message.
Event: email.bounced · bounce_type: soft
Suppression read: no matching record
Manual restriction: none
Application finding: soft-class bounce
Original recipient outcome: bounced · terminal
This email.bounced event establishes a terminal bounced outcome for the original recipient. The soft classification does not automatically suppress the address. By contrast, email.deferred is temporary and delivery remains pending. Record the bounced result without adding a manual all-category block or creating a fresh send.
Review bounce classification ↗Inspect a repeated signed event and reconcile the original application finding without repeating its business effect.
Signed event ID: evt_example_bounce
Recent duplicate: recognized by trigger
Trigger’s remembered IDs: bounded to 500
Earlier application finding: unknown
Downstream action: not repeated
The trigger acknowledges a recognized recent duplicate. Its bounded list is not durable business-operation deduplication or exactly-once processing. Reconcile the original application finding in your durable record before deciding recovery.
Review the supported workflow setup ↗n8n nimmt einen API-Schlüssel statt OAuth, und das ist bewusst so: Eine selbst hostbare Plattform bedeutet, dass jede Instanz eine eigene Redirect-URI bräuchte – ein Schlüssel ist also das Credential, das auf n8n Cloud und auf Ihrem eigenen Server gleich funktioniert.
Installieren Sie den Node auf n8n Cloud oder einer selbst gehosteten Instanz mit aktivierten verifizierten Community-Nodes. Danach steht er in Ihren Workflows zur Verfügung.
Senden Sie Nachrichten, verwalten Sie Kontakte und prüfen Sie die Zustellung mit Operationen, die aus der öffentlichen API generiert werden.
Messaging, Einrichtung und Reporting. Versand, Zustellstatus, Event-Timelines, Templates, Domains, Unterdrückungen, Statistiken und Lookup. Echtzeit-Publishing und -Subscriptions, Byte-Downloads und umleitungsbasierte Medienabrufe sind ausgenommen.
$ SMS
Ein Trigger, der sich selbst verifiziert. Subscribe to events and the node registers the webhook, checks each delivery's signature, and suppresses recent duplicate event IDs. Keep durable deduplication for the business action in your application.
$ Bird Trigger
Ein Schlüssel, kein Host. Das Präfix des Schlüssels enthält die Region, sodass dasselbe Credential auf n8n Cloud und selbst gehosteten Instanzen funktioniert – ohne weitere Konfiguration.
$ Bird API credential
Weiter mit der Dokumentation, Anleitungen und Beispielen zu diesem Thema. Die Ressourcen sind auf Englisch.
Prepare a verified sending domain and an eligible recipient. Authorize a test send in your own workflow, retain its message ID, then inspect the recipient’s outcome. Accepted is not delivered; delivered is not read.
For a conversational inbox, choose Agent Mailboxes. For a one-time passcode, follow Verification API setup and distinguish a sent code from a successful check.
FN–1042Thanks, Alex. Your order is confirmed.
Illustrative order FN–1042 contains one Everyday cup. This preview does not open a customer account or change an order.
Reuse an existing connection, check the workspace and prepare the first supported product task.
Current configuration, delegated permissions, transport limits and authentication recovery.
Use the CLI for workspace operations and email-audit to inspect public DNS without sending mail.
Create a Bird account, follow your client’s setup guide and prepare your first supported product task. Talk to our team about products, permissions and deployment needs.
Ein Test-API-Key steht Ihnen sofort zur Verfügung. Der Produktivzugang wird freigeschaltet, sobald Sie eine Zahlungsmethode hinzufügen und einen Absender verifizieren.
Dokumentation lesen