> ## Documentation Index
> Fetch the complete documentation index at: https://docs.famulor.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Email history

> Review assistant email conversations alongside calls.

Assistant emails appear in **History** as soon as an inbound message arrives. The complete exchange is grouped into one conversation row, like one call: customer → assistant → customer → assistant.

Replies are grouped through standard email threading headers and a reply-address fallback, so the full exchange stays together even across multiple messages.

## Email history table

Use **Type → Email** to show email only. Direction describes how the conversation started: an inbound customer message stays inbound after the assistant replies, while a standalone outbound email is outbound. Search matches email addresses, subjects, and plain-text bodies; the assistant and status filters work across calls and email.

Email reply states use the shared History statuses:

| Email state           | History status |
| --------------------- | -------------- |
| Reply pending         | `in_progress`  |
| Reply sent            | `completed`    |
| Outbound email        | `completed`    |
| Reply failed          | `failed`       |
| No assistant assigned | `skipped`      |

Open an email row to read every inbound message and assistant reply chronologically, plus sender, recipient, subject, assistant, latest reply state or error, and attachment information. Attachment contents are not retained. Search also matches every grouped reply. A new reply moves the conversation back to the top.

## API and MCP

* REST: `GET /api/v1/history` and `GET /api/v1/history/emails/{id}` (`calls:read`)
* MCP: `list_history` and `get_email_history_item`

The list endpoint supports `type`, `direction`, `status`, `assistant_id`, `campaign_id`, `search`, `from`, `to`, `limit`, and `offset`.

The email **channel itself** — sending/receiving domains, per-address assistant assignments, and the workspace default sender name and signature — is also fully manageable via API and MCP: `GET`/`POST /api/v1/email/domains`, `GET`/`DELETE /api/v1/email/domains/{id}`, `POST /api/v1/email/domains/{id}/verify`, `GET`/`POST /api/v1/email/addresses`, `PATCH`/`DELETE /api/v1/email/addresses/{id}`, and `GET`/`PUT /api/v1/email/settings` (`assistants:read`/`assistants:write`). MCP tools: `list_email_domains`, `connect_email_domain`, `get_email_domain`, `verify_email_domain`, `delete_email_domain`, `list_email_addresses`, `create_email_address`, `update_email_address`, `delete_email_address`, `get_email_settings`, `update_email_settings`.

See also [Conversation history](/monitoring/history) and [Email channel setup](/channels/email).