# Agent Email Inboxes — 官方帮助文档存档

> 来源：https://docs.gumloop.com/core-concepts/agents_email.md
> 抓取日期：2026-05-30
> 状态：✅ 完整

---

## Overview

This feature provides an agent with a dedicated email address so anyone can interact with it by sending a message. Four key benefits:

- **Dedicated Inbox**: Each agent receives a unique address at `@gumloopagents.com`
- **Threaded Conversations**: Email replies maintain threading, agent retains full conversation history
- **Works with Attachments**: Files sent as attachments can be processed by the agent
- **Control Access Anytime**: Email alias can be updated or inbox disabled

## Enabling (3 Steps)

1. Open Email Inbox page (sidebar → External Channels → Email Inbox)
2. Click "Enable Email Inbox" — auto-generates `your-agent-name@gumloopagents.com`
3. Start sending emails — agent processes and replies, interactions appear in chat history

## Customizing Alias

- Length: 3–64 characters
- Only alphanumeric + hyphens
- Must start/end with letter or number
- Old address stops immediately when changed

## How It Works (9 steps)

1. Email received → routed to Gumloop's email processing service
2. Agent lookup by email alias
3. Sender verification via DKIM signature (must match Gumloop account)
4. Permission check (same access control as chat)
5. Thread resolution via `References`/`In-Reply-To` headers
6. Attachment processing (decoded and passed as file inputs)
7. Agent execution (same AI engine, all configured tools/ integrations)
8. Reply sent as HTML email (file outputs included as attachments)
9. Conversation persisted (visible in Gumloop UI and future email threads)

## DKIM Authentication

- DKIM signature verified on every inbound email
- Emails without valid DKIM are rejected (bounce message: "Address not found")
- Personal Gmail/Outlook/iCloud: DKIM already enabled by default
- Workspace/corporate domains: Admin must enable DKIM
- DNS propagation can take up to 48 hours

## Threading

- New emails = new conversation
- Replies = continue existing conversation (agent has full history)
- CC recipients preserved in agent's reply
- Uses standard email headers (works across Gmail, Outlook, Apple Mail)

## Credentials

- Sender's personal credentials used for integrations
- If sender hasn't authenticated a service, agent notifies in reply
- Team credential settings apply same as chat
- Sender's email MUST match Gumloop account email

## Rate Limits

- Same concurrency limits as other agent channels
- Enterprise: automatic queuing with queue position notification
- If processing time exceeded: error reply

## Permissions

- Managing email inbox requires Editor access
- Viewers/Use-Only cannot enable/disable/change alias
- Organization admins can restrict via policy controls

## FAQ Highlights

- Who can send? Anyone with Gumloop account + read access + matching email + DKIM
- Custom domain? Not currently. All use @gumloopagents.com
- Attachments? Yes, agent can also send files back
- Proactive emails? No — inbound-only. Use Gmail/email MCP for outbound
- Multi-channel? Yes, agent can be on Slack + email + chat simultaneously
- File size limits? Keep attachments under 25 MB