Apply recipient allow and block lists at the correct scope
Combine send, receive and reply policies without assuming an inbox setting overrides a broader restriction.
Lupin field guides
Inboxes, threads, delivery and dependable email workflows for agents.
25 published articles
Assign an inbox to an agent without sharing your mailbox
Choose a dedicated inbox, preserve its identity and give an agent only the access its workflow needs.
Build an email draft lifecycle with explicit state transitions
Create, update and retire drafts while preserving source messages and separating drafting from sending.
Build an email webhook receiver that queues work safely
Authenticate inbound events, isolate tenant routing and acknowledge only after durable acceptance.
Build an email-to-tool pipeline with an approval boundary
Turn verified inbound events into proposed actions while keeping sender content separate from account authority.
Choose reply, reply-all or forward by the intended audience
Understand conversation and recipient behavior before an agent responds or shares a message.
Extract useful context from inbound email without losing evidence
Build bounded, attributable model input from new text, conversation history and attachment metadata.
Handle email attachments as bounded untrusted files
Inspect metadata, download bytes deliberately and keep attachment content out of automatic tool execution.
Isolate multiple email agents with inboxes, projects and keys
Choose the isolation boundary that matches agent responsibility and customer ownership.
Keep API message IDs separate from email threading headers
Preserve conversation references without treating subjects or external identifiers as ownership proof.
Keep email prompt injection from becoming tool authority
Treat sender content, attachments and quoted conversations as untrusted data throughout an agent workflow.
Move an email agent from a shared mailbox to a dedicated inbox
Migrate new inbound work gradually while preserving old records and acknowledging the limits of mailbox and thread portability.
Paginate email messages with durable processing checkpoints
Walk a mailbox safely, preserve cursors and prevent repeated work when new messages arrive.
Plan email retention around content expiry and durable accounting
Understand what expires, what remains and how storage settings affect an agent’s ability to revisit messages.
Prevent duplicate agent emails when a request times out
Persist a send identity before submission and separate definitive failures from uncertain provider outcomes.
Read email threads without losing conversation context
Retrieve a conversation, interpret its messages and keep source references in an agent summary.
Report email acceptance, rejection and delivery as separate states
Build status tracking around actual event evidence rather than treating a successful send response as a read receipt.
Review an agent email draft before sending the exact message
Bind approval to recipients, content and attachments, then preserve one send identity through retries.
Schedule email drafts with realistic timing and failure handling
Use send_at as a durable schedule while accounting for cron cadence, permissions and failed sends.
Set up a custom email domain and diagnose DNS verification
Publish the returned records, distinguish verification failures and avoid confusing ownership with deliverability.
Test an email agent with fixtures instead of live recipients
Build a focused offline suite for parsing, permissions, retries and review boundaries.
Understand recipient restrictions before sending agent email
Separate autonomous registration, human-email verification and recipient lists so denied sends have a clear remedy.
Use email labels without bypassing spam visibility controls
Separate workflow labels from system states and account for protected messages in searches and summaries.
Use parsed email fields and raw MIME for different jobs
Keep normal agent reading simple while retaining a path to inspect original MIME structure and headers.
Verify email webhook signatures against the raw request body
Check signatures, timestamps and event identity without trusting parsed or reconstructed payloads.