Robotomail

What is Robotomail?

Robotomail provides email infrastructure for AI agents, letting you create agent-controlled mailboxes and send or receive emails through a REST API. Its core purpose is to give agents real email addresses and a programmatic way to send outbound messages and process inbound messages as part of an automated workflow.

Instead of relying on interactive browser-based flows, Robotomail is set up for API-first usage. You can create mailboxes, send messages, and handle inbound delivery events so your agents can parse and respond within threads.

Key Features

• Create mailboxes via API: A single API call creates a mailbox for your agent, giving it a real email address to send from and receive at.
• Send email with REST endpoints: Use POST requests to send messages (including subject and body text). The API response includes message identifiers and status.
• Inbound email delivery notifications: Inbound messages can be handled via webhooks, SSE streaming, or polling, enabling near-real-time processing.
• HMAC-signed inbound payloads with retries: Inbound event payloads are HMAC-signed, and the system includes automatic retries for delivery handling.
• Threaded conversation support: Robotomail resolves threads automatically using email threading signals such as In-Reply-To and subject matching, helping agents maintain conversation context across replies.
• Custom domains with DNS verification: You can send from your own domain with auto-configured DKIM, SPF, and DMARC, plus guided DNS setup and verification.
• File attachments via secure storage: Attachments are supported by uploading to secure cloud storage and sending outbound messages with presigned download URLs for inbound.
• Per-mailbox usage controls: The product includes daily and monthly send limits, storage quotas, and suppression lists on a per-mailbox basis.

How to Use Robotomail

1. Create a mailbox: Sign up for a mailbox (the site mentions an agent skill onboarding path at robotomail.com/skill) or create one directly via the API.
2. Send an email: Call the REST endpoint to POST a message to the target mailbox’s messages endpoint, providing recipient(s), subject, and body text.
3. Receive inbound messages: Configure how you want to be notified (webhooks, SSE, or polling). Process the inbound event payload in your service.
4. Reply and keep context: When your agent generates a response, send a follow-up message; Robotomail supports automatic threading so replies stay connected.

Use Cases

• Agent-generated report delivery: An AI agent drafts a report and emails it to a user; when the user’s inbox receives it, your system can capture inbound replies and respond.
• Automated support triage: An operations agent receives inbound emails in a mailbox and routes or replies based on message content, using inbound event notifications and threading.
• Tool- or workflow-triggered notifications: A pipeline runs, then sends a status or result email through the API; inbound messages can be handled as follow-ups.
• Domain-aligned agent identity: Teams that need emails to originate from their own domain can set up DKIM/SPF/DMARC and send from configured addresses while still using agent mailboxes.
• Document exchange with attachments: Agents can include files by uploading to secure storage and attaching via presigned links, enabling automated back-and-forth document sharing.

FAQ

• Do I need SMTP or OAuth to use Robotomail? The site describes Robotomail as having “no SMTP” and “no OAuth.” Email operations are performed via REST API.

• How do I get notified when an email arrives? The product supports inbound handling via webhooks, SSE event streaming, or polling.

• Does Robotomail support conversation threading? Yes. It resolves threads automatically using headers such as In-Reply-To and subject matching.

• Can I use my own sending domain? Yes. The site states that custom domains are supported with guided DNS setup and auto-configured DKIM, SPF, and DMARC.

• Is there a free tier and a trial policy? The page mentions a “5,000 emails/mo free” tier and a “30-day money back” guarantee on paid plans.

Alternatives

• Gmail/Outlook with user-based OAuth + inbox APIs: These are designed around human access and typically involve interactive consent flows; they may not fit automated agent workflows that need mailbox provisioning.
• Transactional email services that focus on sending (outbound-only): Some providers support sending but not receiving via an agent mailbox model. Robotomail is positioned for both send and receive.
• Generic email inbox parsing + custom send integration: You can combine an inbound email parser (for receiving) with a separate sending provider, but it’s typically more complex to recreate mailbox lifecycle and threading behavior for agents.
• Workflow automation platforms with email steps: These can automate email-based tasks, but they may not provide the same API-native mailbox creation and inbound event handling tailored for AI agents.