Give the agent its own mailbox for reading threads and sending updates
Agent Mail gives Luumen a real inbox of its own. It can list inboxes, read a thread in full, and pull the details you need mid-incident without you switching to a mail client. When something has to go out — a status note, a reply to a vendor, a handoff summary — Luumen drafts it and sends it once you approve. Connected with an API key.
5 tools: 3 read, 2 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Agent Mail run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as create inbox, send email. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Agent Mail — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.