# How to give an AI agent its own email address

> Give an agent its own construct-agent.xyz address or one on your domain, or let it send from your Gmail. Limits by plan, signature, stop links, approvals.

By Nischal Naik, published Oct 8, 2026, updated Nov 19, 2026. Topics: Email, AI agents.

Give the agent a mailbox of its own, so the mail it sends is signed as an agent and the mail it reads can't touch your personal inbox. In Construct each agent can have one mailbox: an address at construct-agent.xyz, or an address on your own domain, like assistant@acme.com. It can also send from your Gmail or Outlook as you. Sending from an agent's mailbox comes with a paid plan, up to 50 emails a day on Lite, 150 on Starter and 500 on Pro, counted per recipient, and every email it writes in a chat waits for your OK before it goes. Mail from an agent's mailbox ends with two lines saying an AI agent wrote it for you, with a link the recipient can use to stop it.

The [email page](https://construct.computer/use-cases/email/) has the short version of what an agent does with a mailbox.

## Why give an agent its own address?

Three things get easier. You can hand the agent work by forwarding an email, the way you would to a colleague. The people it writes to can tell an agent wrote the message. And a mistake stays inside the agent's mailbox instead of your own.

That last one has happened. In February 2026, Meta AI security researcher Summer Yue posted that an OpenClaw agent she had asked to suggest what to archive or delete in her inbox started deleting her email instead and ignored her stop commands from her phone. "I had to RUN to my Mac mini like I was defusing a bomb," she wrote. She put it down to the agent compacting its context on her large real inbox, after the same setup had worked on a small test one. TechCrunch, which reported it, couldn't verify it independently ([TechCrunch, February 23, 2026](https://techcrunch.com/2026/02/23/a-meta-ai-security-researcher-said-an-openclaw-agent-ran-amok-on-her-inbox/)).

## Which mailbox should the agent use?

| Option                                 | Sends as                                         | What starts work                                                                               | Good for                                                                                       |
| -------------------------------------- | ------------------------------------------------ | ---------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| Its own address at construct-agent.xyz | The agent, signed as an AI agent working for you | Mail from senders it knows starts work as it arrives; a new sender's first email waits for you | Vendor questions, quotes, invoices and reports, where the recipient can know an agent wrote it |
| An address on your own domain          | The agent, at your domain, signed the same way   | The same, with new mail fetched every 2 minutes                                                | A mailbox made for the agent, like assistant@ or orders@ on your company's domain              |
| Send from your Gmail or Outlook        | You                                              | Nothing: the agent works in your inbox when you ask or on a schedule                           | Replies in your own threads, and sorting the inbox you already have                            |

Built-in addresses all live on construct-agent.xyz. For an address on your own domain, make the mailbox at your mail provider and type its address into Construct, which looks up where the domain's mail lives. On Google Workspace or Microsoft 365 you sign in as that mailbox; anywhere else you give it an app password, and Construct signs in over encrypted IMAP and SMTP only. Proton mailboxes and personal Gmail and Outlook.com addresses can't be connected this way.

## How do you set up an agent's own address?

### 1. Get the address

Open the agent's settings, go to its Email tab, type a name under An address of its own and choose Get address. If you ask an agent without a mailbox to email someone, a card in the chat offers the same choices. Pick the part before the @: 3 to 32 characters, starting with a letter, using lowercase letters, numbers, dots, dashes and underscores. Names that read as staff, mail systems, billing or a big brand, such as support, billing, admin, noreply and ceo, are reserved.

### 2. Agree to the email rules

Before the first address, you agree to three rules, because your agents email people on your behalf:

- "No spam: nothing bulk, cold or unwanted to people who didn't ask for it."
- "No phishing, scams or pretending to be someone else."
- "Nothing illegal or harmful, and follow the email laws where you and the people you write to are."

Breaking them can get the address, the workspace's email or the account suspended. Agent addresses are for operational mail to people who expect it: suppliers, customers who wrote first, your own team. They aren't for newsletters or cold outreach.

### 3. Tell it the job

Say what the mailbox is for and how you want replies handled. The agent's email tools treat an email's words as information, never as instructions, so a stranger can't hand it work by writing to it.

> **Prompt:**
>
> You have your own email address now. Every weekday at 8, check it for supplier quotes, save each attachment to a Quotes folder in Files, and tell me here what arrived and how each price compares with last time. Draft replies where a supplier asked a question, and don't send anything without asking me.

### 4. Approve what goes out

Every email the agent writes waits on a card that shows exactly what will go, the signature included. Send sends it; Not now keeps it as a draft. Only the person who asked for the email can approve it. In a workflow run the run waits for you, unless the workflow sends only to you or to addresses you gave when you saved it. Drafts also wait in Mail under Waiting for you, where you can send one, ask for changes or discard it.

## What do the people your agent emails see?

Under the agent's sign-off, Construct adds two lines to every email from an agent's mailbox, on construct-agent.xyz or your own domain:

```
--
Atlas, an AI agent working for Maya
Made with Construct Computer. Sent 19 Nov, 09:30 UTC. Stop or report: <a link of their own>
```

The send time keeps Gmail from folding the lines away as repeated text in a long thread, and the From name says it too, like Atlas (Maya's AI agent). In a team, the first line names the team. Each recipient gets their own copy with their own link, and mail apps that support one-click unsubscribe show it there too. On the link's page at construct-agent.xyz they can stop this agent, or every agent in your workspace, from emailing them, or report the email.

Once someone stops an agent, any email to them is refused before it reaches your approval card. A stop on one agent lifts if they write to that agent themselves; a stop on every agent stays until they undo it.

Reports move in steps, and only reports made from the link in a real email count. One report does nothing on its own. Reports from at least 2 people and 0.3% of the people an address emailed in a week slow it to 10 new people a day for 7 days, and reports from at least 3 people and 1% hold it to people it has already written to. A report of phishing, malware, impersonation or harassment holds everything the address sends until someone at Construct looks, which is due within 4 hours (24 for other holds). The 0.3% line is Google's: its sender guidelines say to "avoid ever reaching a spam rate of 0.30% or higher" ([Google, email sender guidelines](https://support.google.com/a/answer/81126)).

## How many emails can an agent send?

|               | Free start | Lite | Starter | Pro  |
| ------------- | ---------- | ---- | ------- | ---- |
| Price a month | Free       | $9   | $49     | $259 |
| Emails a day  | None       | 50   | 150     | 500  |

The limit is per workspace, over any 24 hours, and counts each recipient, so one email to three people counts as three. A paid plan's first 7 days send up to 10 a day, whichever plan it is. One email goes to at most 10 people and carries up to 5 files from Files, 10 MB together, and an agent sends at most three emails in one turn. A workspace can take as many new construct-agent.xyz addresses a month as its plan has agents, Construct included, and can give an agent back an address it had before at any time.

On the free start an agent can have an address and read what comes in, and sending from it waits for a plan. [Pricing](https://construct.computer/pricing/) has the rest of each plan.

## What happens when mail comes in?

For an agent's own mailbox, on construct-agent.xyz or your domain, mail from a sender the agent knows, and whose domain vouches for them, starts work as it arrives, in a chat for that email's thread. The agent knows someone you've let in, someone it has written to, and someone whose mail already reached it. Everything else waits:

- The first email from a new sender is held until you let them in. That includes the first one you forward from your own address.
- Mail whose sender can't be verified is held with its words hidden, from the agent too.
- Out-of-office replies, bounces and newsletters never start work.
- Blocking a sender sends their mail straight to Trash, where deleted mail stays for 30 days.

A mailbox on your own domain is checked every 2 minutes, and the first check takes in what was already there without waking the agent. A mailbox starts work at most 20 times a day. A workflow can also listen for up to ten senders, and their mail starts that workflow instead, as [AI workflow automation](https://construct.computer/blog/ai-workflow-automation/) explains.

Your own Gmail or Outlook gets plenty of mail you already read, so nothing there is screened and new mail doesn't wake the agent. It works through that inbox when you ask, or on a schedule you set.

## When should you use your own Gmail or Outlook instead?

Use your own mailbox when the message has to come from you: a reply in a client's existing thread, or anything where the person expects your name. Use it when the job is your inbox itself, like finding last month's invoices or drafting replies to customers. Choose Send from your Gmail or Send from your Outlook on the agent's Email tab. The agent then works in that inbox as you, set to Ask first, and every send still waits for your approval.

Connecting your mailbox is different from Gmail's own delegation, which Google describes plainly: "A delegate is someone who can read, send, and delete emails in your account for you" ([Google, Gmail delegation](https://support.google.com/mail/answer/138350)). An agent with that access can do the same, so keep it on a mailbox it can't damage, and keep sends behind an approval.

For newsletters, cold outreach and anything in bulk, use an email service built for marketing, with its own consent and unsubscribe handling. Construct's rules forbid that mail from agent addresses.

## What about AgentMail and other email APIs?

AgentMail is an email API for developers: you create inboxes through its API and build the agent around them. Its plans, checked on [its pricing page](https://www.agentmail.to/pricing) on November 19, 2026:

| Plan      | Price a month | Inboxes | Emails                      | Custom domains |
| --------- | ------------- | ------- | --------------------------- | -------------- |
| Free      | $0            | 3       | 3,000 a month, 100 a day    | 1              |
| Developer | $20           | 10      | 10,000 a month, 1,000 a day | 10             |
| Startup   | $200          | 150     | 15,000 a day                | 150            |

AgentMail is the better pick when you're building your own product or agent, or need many inboxes across many domains. Construct is the pick when you want an agent that already reads, drafts, saves to Files and asks before it sends, without writing code.

---

The Markdown copy of https://construct.computer/blog/ai-agent-email-address/. Everything Construct Computer publishes is listed in https://construct.computer/llms.txt.
