Parsio
for LuumenAI
Check parser output, fix field mappings, and push documents back through
Parsio turns incoming emails, PDFs, and attachments into structured fields. Connect it and Luumen can read your mailboxes, their parser configuration, and the parsed JSON on any document, so you can see exactly why an extraction came out wrong. Changes — uploading a file, editing mailbox settings, reparsing — are previewed and approved before they run.
The Parsio toolbox
10 tools: 5 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet DocumentGet one Parsio document and its mailbox-specific parsed JSON fields.
- ReadGet MailboxGet settings and parser configuration for one Parsio mailbox.
- ReadList DocumentsList and filter documents in a Parsio mailbox, one page at a time.
- ReadList MailboxesList the Parsio mailboxes available to the connected account so their IDs can be used for parsing and configuration tasks.
- ReadList Table FieldsList the extraction fields configured for a Parsio mailbox.
- WriteParse Text DocumentSubmit plain text or HTML to an existing template-based or GPT-powered Parsio mailbox, optionally waiting for the parsed result. Approval by default
- WriteReparse DocumentQueue an existing Parsio document to be parsed again. Approval by default
- WriteSkip DocumentsMark one or more documents in a Parsio mailbox as skipped. Approval by default
- WriteUpdate MailboxUpdate one or more settings on an existing Parsio mailbox. Approval by default
- WriteUpload DocumentUpload one file to a Parsio mailbox for parsing, optionally waiting for the parsed result. Approval by default
One prompt, start to finish
What a governed Parsio run looks like inside Luumen.
Questions
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 — parse text document, reparse document, skip documents, update mailbox, and more — is shown as a plan and requires approval by default, including the 2 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 Parsio — 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.
Often connected alongside
All integrations
Adobe Marketing Agent MCPAdobe Experience Platform context, sandbox switches, and async task status
AffindaRead parsed documents, collections, and annotations — change them with approval
Agent MailGive the agent its own mailbox for reading threads and sending updates
AI/ML APIInspect assistants, threads, and runs — and change them as approved stepsPut Parsio to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.