AgentMailer examples
Copyable, named examples for common AgentMailer workflows. Every example is a self-contained directory with a README and equivalent Python and TypeScript implementations.
Architecture boundary
These examples are agent applications, not jobs hosted by AgentMailer. AgentMailer supplies durable identity, inboxes, messages, threads, drafts, attachments, events, delivery state, A2A protocol exchange, and communication policy. The example process or its production runtime owns model calls, tools, schedules, checkpoints, event deduplication, business approvals, and internal workflow state.
For email automation, verify and durably record the signed AgentMailer event in your application before doing expensive work. Correlate application state with the AgentMailer message or thread ID, and use stable idempotency keys for every mailbox mutation. A2A task state is shared protocol state between peers, not an AgentMailer worker queue.
Getting started and infrastructure
Productivity and operations
Sales, recruiting, and communications
Support, finance, legal, and development
Each TypeScript example is an independent workspace package. Validate them all without calling AgentMailer:
Python examples install the local generated SDK from this repository. From an
example’s python/ directory:
The existing client snippets remain available as terse API references. Start with a named example when you want a complete communication pattern for an agent application.
Safety conventions
- Read operations are the default.
- Email and A2A writes require an explicit environment-variable opt-in.
- Agent execution state and external side effects remain outside AgentMailer.
- Signup stops at the human approval boundary.
- Support automation creates a draft instead of sending a reply.
- Webhook examples verify the raw request body before parsing it.
- Secrets, customer content, and
.envfiles must never be committed.
Inkbox workflow coverage
The Browser Use, Kernel, signup, webhook, and CLI mailbox journeys from Inkbox’s examples are covered. AgentMailer does not expose an encrypted credential vault, TOTP generation, phone-number provisioning, calling, or a general-purpose public tunnel. Those Inkbox-specific operations are intentionally not imitated here; use a dedicated provider with separately scoped credentials when a workflow needs them.