Check parser mailboxes, inspect failed documents, and reprocess after a fix
Parseur turns inbound emails and PDFs into structured data. Connect it and Luumen can read your mailboxes, their field schemas, and the logs behind any single document — so you can see why an invoice parsed short or a batch stalled. Changes like reprocessing a document, creating a mailbox, or editing an export run as previewed steps you approve.
26 tools: 10 read, 16 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Parseur 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 — copy document, copy mailbox, create custom download, create mailbox, and more — is shown as a plan and requires approval by default, including the 5 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 Parseur — 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.