Read Missive threads for context, then post updates and tasks with approval
Missive holds the shared inbox where incidents, vendor threads, and customer escalations actually get discussed. Luumen reads conversations, messages, comments, and drafts to see where a thread stands. When it needs to write back, it posts a comment, drafts a reply, or opens a task, and shows you the text before it sends. Luumen connects with an API key.
40 tools: 21 read, 19 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Missive 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.
Read actions answer immediately. Anything that writes — create analytics report, create missive contacts, create draft, create missive post, and more — is shown as a plan and requires approval by default, including the 4 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
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 Missive — 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.