Move an Aurinko agent workflow to Bird Mailboxes

Use Bird when the task needs its own mailbox. Keep Aurinko where the product still needs to search, synchronize or act in an existing user account. These can remain separate parts of one application.

Aurinko's Email API provides access to connected providers, including Gmail, Microsoft accounts and IMAP. Its incremental synchronization includes updated and deleted streams with continuation tokens. See the Aurinko Email API.

For example, move requests sent to an agent-owned support address while keeping the user's inbox search in Aurinko. Save the routing decision with the case so retries do not choose a different provider.

Create a Bird mailbox and send it a test request. Confirm its address, receiving policy and application owner. Record the returned IDs instead of attempting to convert an old provider ID. The integration chooser helps separate this task from outbound-only email and existing-account access.

Start with the complete Node.js support inbox or Python support inbox. Each creates a mailbox, receives a message, records an application-owned support case and acknowledges it in the original thread. A later message updates that case; a repeated message does not send another acknowledgement.

The examples keep a small local checkpoint for development. Put the same case, incoming-message and outgoing-operation identities in your application's durable store before running multiple workers. Keep the business action separate from the email: acknowledging a refund request does not issue a refund.

Then add the signed event receiver and attachment workflow. Store the received-message ID with the case before acknowledging the event. Retrieve attachment metadata and bytes through the documented operations; keep any retained files under your application's access and retention rules.

Verify the dedicated mailbox receives a request, retrieves its attachment and replies in the correct conversation. Send a later reply and replay an earlier event; confirm the latest message is considered without repeating the business action. Test a lost send response and use the operation record to reconcile it.

Separately, confirm existing-account search and synchronization still work for the user. Keep each account's update/deletion checkpoints and any required archive. A successful Bird reply does not establish that the connected account finished synchronizing.

Move one address or customer cohort, then compare case creation and reply outcomes with your previous implementation. Pause the old dedicated-task worker for that cohort while leaving unrelated account synchronization running.

If you roll back, stop new Bird jobs first and resolve outstanding sends. Remove old account access only when the product no longer needs it; that decision is independent of provisioning a Bird mailbox.