Skip to content
🚀 EDDI 6.7.0

19 LLM providers, knowledge bases that crawl your site and read your files, and conversations that follow compatible agent versionsWhat's new

Managed Cloud Get Started
All integrations
ChannelsIMAP · SMTP

Email

Connect a mailbox to an agent. Every new mail starts an agent turn or a group discussion, and in conversation mode the agent replies in the thread, only to a sender whose mail passed DKIM and DMARC.

What you get

  • Trigger mode for process mailboxes (invoices, orders, CVs, claims): the agent acts through its tools and never replies to anyone
  • Conversation mode for a small team's support or info mailbox: replies in the same thread over SMTP, and the sender's answer continues the same conversation
  • Attachments handed to the agent as files, with allowed types you choose
  • Exchange Online and Microsoft 365 through OAuth (XOAUTH2), or any IMAP host with an app password
  • A daily cost budget and a per-sender daily cap, so a flood of mail cannot run up the bill

How it works in EDDI

  1. Create a SERVICE connection for the mailbox. Its baseUrlAllowlist must name the IMAP origin (imaps://host), and in conversation mode the SMTP origin too. The secret stays in the vault.
  2. Create a channel integration with channelType: "email", the mailbox address, a mode and the agent or group it routes to. Saving creates the poll schedule.
  3. Restrict who can trigger it: requireAuthentication and a senderAllowlist. The save returns warnings when anyone could make the agent run, or when the agent has tools but no approvals.
  4. Send a test mail after the first poll. Mail that was already in the folder when the integration was created is not processed.

Configuration

Taken from the EDDI documentation. Placeholders such as your-agent-id are yours to replace.

POST /connectionstore/connectionsA mailbox connection for Exchange Online with OAuth client credentials. The client secret is a vault reference.
{
  "name": "exo-invoices-mailbox",
  "authType": "OAUTH2_CLIENT_CREDENTIALS",
  "binding": "SERVICE",
  "oauth": {
    "tokenUrl": "https://login.microsoftonline.com/<tenant-id>/oauth2/v2.0/token",
    "clientId": "<application-id>",
    "clientSecret": "${vault:exo-invoices-client-secret}",
    "scopes": ["https://outlook.office365.com/.default"]
  },
  "baseUrlAllowlist": ["imaps://outlook.office365.com"]
}
POST /channelstore/channelsA trigger-mode integration that only accepts authenticated mail from two supplier domains and stores PDF and image attachments.
curl -X POST http://localhost:7070/channelstore/channels \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Invoice intake",
    "channelType": "email",
    "platformConfig": {
      "mode": "trigger",
      "transport": "imap",
      "connection": "exo-invoices-mailbox",
      "host": "outlook.office365.com",
      "address": "invoices@contoso.com",
      "processedAction": "move:EDDI/Processed",
      "senderAllowlist": "*@supplier-a.com,*@supplier-b.de",
      "requireAuthentication": "true",
      "attachments": "store",
      "attachmentMimeTypes": "application/pdf,image/png,image/jpeg",
      "dailyCostBudgetUsd": "20"
    },
    "targets": [ { "name": "intake", "type": "AGENT", "targetId": "your-agent-id" } ],
    "defaultTargetName": "intake"
  }'

Governance

  • Mail is untrusted input. Give an email agent the fewest tools it needs and put tool approvals on every tool that changes something. When a turn pauses for approval, the sender is told that a person must approve the next step, never which tool or arguments.
  • The model never chooses a recipient. Trigger mode sends nothing, and conversation mode answers only the authenticated sender, at most five replies per thread per hour by default, with an AI disclosure appended to every reply.
  • Every refused mail and every sent, failed or bounced reply leaves an audit-ledger entry with the sender only as a domain and a hash. No raw mail is stored, and erasure by address reaches the conversations and the ledger rows.
  • Mail servers are reached by DNS name only, never on private or metadata addresses, with TLS always verified.

Good to know

  • EDDI is not a mail server. It logs in to an existing mailbox like a mail client: no MX record and no public ingress.
  • Gmail and Google Workspace are not supported yet, and neither is an on-premises Exchange on a private address. Replies are plain text.
  • If a helpdesk such as Zendesk or Freshdesk already receives the mail, keep it: trigger EDDI through the signed webhook channel and answer through the helpdesk API.

Need it built and run for you?

EDDI Solutions builds and maintains connectors, runs EDDI as a managed or co-operated instance, and supports you in your own cloud or on-premises.

Talk to EDDI Solutions ↗

Related integrations

Configuration and behavior on this page follow the EDDI documentation, checked on 2026-11-06. Field names and defaults can change between releases, so confirm them in the docs for your version.