AgentMail Connector
Connector status: In progress Being built. Not verified yet.
Illustration · sample data
Sync example
Source
AgentMail
Connector status: In progress
Destination
Your other tool
Connector status: Custom tool
Field mapping
| Source field | Destination field | Sample value |
|---|---|---|
record.id | source_id | record_1042 |
record.updated_at | updated_at | 2026-10-18T08:00:00Z |
record.value | value | sample_value |
- Draft
- Review one record
- Approve this version
Statuses describe individual connectors; they do not guarantee this sync is ready. Illustrative fields. Review the actual schema and permissions before a sync runs.
Connector implementation
Build the AgentMail integration
Email inboxes for AI agents: create inboxes, send and receive mail, threads, labels, webhooks
Implementation Overview
Implement an AgentMail connector that authenticates to the vendor surface, normalizes source records in Tajo, and activates eligible data in Brevo.
Treat this as an implementation guide. Build and validate the auth, mapping, sync, and operations paths before production use.
mcp.agentmail.to/mcp
| Property | Value |
|---|---|
| Integration surface | API + MCP |
| Status | In progress |
| Category | Email Infrastructure |
| Setup complexity | medium |
| Vendor documentation | docs.agentmail.to |
| Allowed host | Not recorded |
| Base URL | Not recorded |
| OpenAPI schema | docs.agentmail.to/openapi.json |
| MCP server | mcp.agentmail.to/mcp |
| Last researched | 2026-10-30 |
Official OpenAPI 3.1 document (cut to the operations the connector calls, SHA-256 pinned). Bearer organisation key (am_…); page_token paging; threads and messages filter on after and before. A hosted MCP server exists for agents’ own mail; Tajo’s connector is the sync side. Free plan: 3 inboxes, no card; an agent can sign itself up through POST /v0/agent/sign-up.
Authentication
-
Use docs.agentmail.to/openapi.json to generate or validate typed API clients and request models.
-
Validate the MCP server endpoint at mcp.agentmail.to/mcp and document required headers, auth grants, and tool availability.
-
Keep docs.agentmail.to linked from the connector runbook so operators can confirm vendor behavior during incidents.
-
Store credentials per Tajo workspace and keep tenant-specific secrets out of connector configuration files.
-
Add a credential smoke test that verifies read access to a harmless resource before running backfills or enabling webhooks.
Data To Sync
Start with these inferred data domains, then confirm exact vendor resources and permissions from the source documentation:
- Events, webhooks, and behavioral activity
- Campaign, messaging, or audience state
- Tickets, conversations, and support context
The connector should make source records idempotent by keeping a stable key such as a vendor object ID, email address, event ID, ticket ID, order ID, or campaign ID. If the vendor only exposes list APIs, Tajo should store the cursor strategy and replay policy explicitly.
Sync Shape
| Resource | Direction | Conflict handling |
|---|---|---|
contacts | inbound | n/a |
threads | inbound | n/a |
inboxes | inbound | n/a |
Mapping To Tajo/Brevo
contacts → Brevo contact
Requires: workspace api key.
| Source field | Brevo destination | Via | Note |
|---|---|---|---|
email | email | — | |
name | attributes.FULL_NAME | — | |
id | attributes.AGENTMAIL_ID | — |
Read for context and not projected: threads, inboxes.
The conventions that apply to every connector — stable external IDs, normalization, backfill and sync strategy, error handling, and the builder checklist — are documented once under “Applies to every connector” on the connector catalog.