Back to Blog

How to Give an OpenClaw Agent Its Own Email Address

To give an OpenClaw agent an email address, run openclaw plugins install clawhub:@openmail/openclaw then openclaw channels add --channel openmail --api-key <key>. The channel creates the inbox — the full setup takes about 2 minutes.

March 29, 2026

OpenClawAI Agent EmailOpenMail CLIEmail InfrastructureAgent Setup+5WebSocket Bridge, Inbox Provisioning, Agentic Workflows, Real-Time Email Delivery, SPF DKIM DMARC

OpenClaw can browse the web, run code, and call APIs. It can't receive a vendor reply or confirm an account - not without an email address. Here's how you fix that.

TL;DR

  • -OpenMail: dedicated inboxes for AI agents, structured JSON events, real-time delivery.
  • -One command installs the channel plugin: openclaw plugins install clawhub:@openmail/openclaw.
  • -Three modes: tool (on demand), notify (alerts you), channel (replies autonomously).
  • -SPF, DKIM, DMARC, and reputation are fully managed.

What agents actually need from email

Not much. A real address. Inbound events as structured data. Thread history as JSON, not formatted HTML.

Most email services are optimized for humans reading at a screen. That's the wrong fit for an agent. OpenMail delivers inbound email as a structured JSON event - sender, subject, parsed body, attachments already extracted - forwarded in real time. No polling. No raw MIME. No SMTP server to run.

Install the plugin

OpenMail is a native OpenClaw channel plugin, @openmail/openclaw, on ClawHub and npm. It runs inside the gateway like any other channel and bundles the CLI:

openclaw plugins install clawhub:@openmail/openclaw
openclaw channels add --channel openmail --api-key <key>
openclaw gateway restart

With an account key, channels add creates the inbox, mints an inbox-scoped key for it, and stores only that. The gateway holds the WebSocket; there is no separate bridge process. The full guide is at docs.openmail.sh/integrations/openclaw.

Pass --mode to choose how inbound mail reaches the agent:

Tool

The agent sends and reads email when you ask. No background activity. Good for agents that send email as part of a task and check for replies on demand.

Notify

The agent alerts you the moment new email arrives. You decide what to do. Good when you want awareness without automation.

Channel

The agent reads incoming email from people and replies autonomously, without you in the loop. Automated mail is announced, not answered. Who may write to the inbox is set by OpenMail's sender rules. Good for support inboxes or anything where speed matters more than review.

Change modes at any time with channels.openmail.mode in openclaw.json.

What it actually enables

The technical side is just plumbing. What matters is what the agent can now actually do in the world.

Close loops that start in someone's inbox

The agent sends an email - a quote request, a meeting confirmation, a follow-up - and when the reply arrives, it acts on it. No polling. No human in the middle. The whole thread stays in the agent's inbox, not yours.

Sign up, verify, and confirm - unattended

The agent registers for a service using its own address, receives the verification email, extracts the confirmation link, and clicks it. The full account-creation flow, without you touching it.

Handle a conversation, not just a message

It can read the full thread history in order, reply in context, and keep a back-and-forth going across days. Not just fire-and-forget - actual correspondence.

Run multiple identities

Need a support address, a billing address, a project-specific mailbox? The agent provisions them on demand via the API. Live immediately. No DNS changes.

One command, one live inbox

One command installs the plugin. OpenClaw handles the rest - inbox provisioning, real-time mail delivery, everything. Deliverability, authentication, and storage are handled.

You can start for free. No credit card required.

Frequently asked questions

How do I give an OpenClaw agent an email?

Install the @openmail/openclaw channel plugin with openclaw plugins install clawhub:@openmail/openclaw, then run openclaw channels add --channel openmail --api-key <key>. With an account key, channels add creates a dedicated inbox and stores an inbox-scoped key. No DNS changes or SMTP configuration required.

What is OpenMail?

Email infrastructure built for AI agents. Dedicated inboxes on your domain, real-time WebSocket delivery as structured JSON, and a fully managed deliverability stack - SPF, DKIM, DMARC - with no SMTP server to configure.

What is OpenClaw?

An AI agent that can browse the web, run code, and call APIs. It supports channels and plugins installed via ClawHub. The @openmail/openclaw plugin gives it full email send and receive.

How long does it take to set up OpenMail for OpenClaw?

About 2 minutes. Run openclaw plugins install clawhub:@openmail/openclaw, then openclaw channels add --channel openmail --api-key <key>, then restart the gateway.

Does setup require DNS changes?

No. OpenMail manages all DNS records, SPF, DKIM, DMARC, and sending reputation. You only need to install the plugin and add the channel.

How fast does inbound email arrive at OpenClaw?

Under 500ms. The OpenClaw gateway holds a WebSocket to OpenMail and each message.received event wakes the agent in real time. No separate bridge process.

Can the agent manage multiple email addresses?

Yes. Call POST /v1/inboxes directly. New addresses are live immediately. No DNS changes, no manual configuration.

Every AI agent deserves its own inbox.

Install the CLI, run setup, and you're sending email from your agent in minutes.

More posts

Developer

How to give your AI agent its own email address

Four ways to give an AI agent an email address, compared. Why Gmail and transactional APIs break, and how to create a dedicated agent inbox with an API call.

Sep 22, 2026
SUSPENDED
gmail
Analysis

The Gmail suspension wasn't the problem. The architecture was.

Gmail suspensions for AI agents aren't random. The automation patterns that cause them look identical to spam. Here's what you've actually lost, why recovery rarely works, and how to move to something built for agents.

July 2, 2026
Analysis

OpenMail vs Nylas

Nylas connects to your users' existing inboxes. If your AI agent needs its own address, here's how Nylas Agent Accounts and OpenMail compare on limits, pricing, and code.

June 29, 2026
Shared infrastructure: three agents with dedicated IPs, rate-limited pools, and circuit breakers
Analysis

What Email Infrastructure for AI Agents Should Look Like

If you had to design email from scratch for AI agents, you wouldn't build Gmail. Here's what purpose-built infrastructure looks like — inbox-as-API, real-time delivery, threading, MIME parsing and IP warming/routing.

June 5, 2026
01Postmarksend-only
02Resendsend-only
03OpenMailagent-native▶
04AgentMailagent-native
05Mailgunbuild it
06Amazon SESbuild it
Analysis

Best email API for AI agents in 2026

Eight email APIs compared on receiving, threading, per-agent inboxes, reputation isolation, EU data residency and price. We run one of them, so we put ourselves first and tell you why.

May 14, 2026
Analysis

OpenMail vs Mailgun vs Amazon SES

Mailgun sends. SES is cheap. Neither was built for agents that receive, thread, and parse attachments. Here’s what’s actually different between all three.

May 6, 2026
ASCII art render of the Creation of Adam — two hands reaching toward each other, one human, one digital
Analysis

Why Every Email Option Falls Short for AI Agents

Gmail bans agents. Proton has no API. Outlook is a maze. Resend can't receive. A look at why every email option falls short for AI agents and what the risks are.

Apr 13, 2026
eu
News

We're EU-Based. That's Not a Footnote — It's the Point.

OpenMail is built in the EU, runs in the EU, and every customer is covered by GDPR — not as a checkbox, but as a legal guarantee.

Mar 16, 2026
audience
Founder insights

This Is Not for Human Eyes

We noticed that AI agents were finding OpenMail before we'd fully built for them. Here's what we saw — and what we built next.

Mar 12, 2026