Skip to Content
DocsAgent Email Aliases

Agent Email Aliases

Agent Email Aliases let you attach an email address to any Airo agent. When someone emails that address, the message is routed to the agent, which can draft a reply or respond automatically.

Any agent kind can have an alias — a custom agent, a pipeline agent, a daily briefing. The alias is just a trigger mechanism.

Requirements

Aliases require an account on your own domain. If you connect alex@company.com, you can attach any address on company.com — support@company.com, sales@company.com, alex+billing@company.com.

Accounts on shared email providers — Gmail, Outlook.com, Yahoo, iCloud and similar — can’t use aliases. Holding alex@gmail.com says nothing about who owns support@gmail.com, so there’s no way to establish that an address there is yours.

This is also why the alias must be on your domain rather than any domain: connecting an account on company.com proves you control a mailbox there, which is what makes support@company.com provably yours. There is no separate verification step — ownership follows from the connected account.

How It Works

Aliases ride on top of your existing Gmail or Outlook infrastructure. No DNS changes, no MX record migration, no third-party email service. Messages arrive in your existing mailbox and Airo routes them to the right agent based on the recipient address.

  1. Open Settings in Airo
  2. Go to Agents and select (or create) an agent
  3. Under Email aliases, enter an address on your domain
  4. The alias is active immediately

Example

If your email is alex@company.com and you add support@company.com to a custom agent:

  • Mail to support@company.com lands in your mailbox
  • Airo intercepts it and routes it to the agent
  • The agent processes the message based on its configuration

To and Cc behave differently

An address in To is treated as the agent’s own mail and is handled by the agent alone.

An address in Cc is treated as an ordinary thread you copied the agent on. The agent still sees it, but the message also keeps its normal triage — smart filters, garnishes and needs-reply all still apply.

Setting Up the Address

The alias needs to actually deliver to your mailbox. Common approaches, all on your own domain:

Google Workspace alias (admin required):

  1. Go to admin.google.com 
  2. Navigate to Directory > Users > your account
  3. Under Alternate email addresses, add the alias

Google Group:

  1. Create a Group in Google Workspace admin (e.g. support@company.com)
  2. Add yourself as a member with email delivery enabled

Plus-addressing: alex+support@company.com works with no setup at all, since it’s already your own mailbox on your own domain.

Email forwarding: forward the address to your inbox by any mechanism you prefer.

Agent Configuration

Each agent’s behavior is configured through its own settings — not on the alias. The alias just routes messages to the agent. Configure your agent with:

SettingDescription
System promptInstructions for the AI (how to respond, what to escalate)
Agent kindThe type of agent processing the messages
EnabledWhether the agent is active

API Reference

List Aliases

GET /agent_email_aliases?user_email=you@company.com&agent_id=agntd_xxx

Create Alias

POST /agent_email_aliases
{
  "agent_id": "agntd_xxx",
  "user_email": "you@company.com",
  "alias_address": "support@company.com"
}

alias_address must be on the same domain as user_email, and that domain must not be a shared email provider. Anything else returns 400.

Delete Alias

DELETE /agent_email_aliases/:id

Security

  • Ownership by domain: An alias must be on the connected account’s own domain. You can’t connect an account on a domain you don’t control, so an address on that domain is provably yours.
  • Shared providers excluded: Personal email providers are rejected, because their namespace is shared by millions of unrelated people.
  • Agent ownership: You must own both the agent and the email account to create an alias.
  • Automated mail is never answered: Bounces, out-of-office autoresponders and mailing list traffic are detected and skipped, so an agent can’t get into a reply loop.

Limitations

  • Custom domains only: Accounts on Gmail, Outlook.com and other shared providers can’t use aliases.
  • Your own domain only: You can’t attach an address on a domain you haven’t connected an account for.
  • Gmail and Outlook only: Aliases work with Google Workspace and Microsoft 365 accounts.
  • One agent per address: Each alias maps to exactly one agent.
Introduction