Sends documents in for parsing, explains why one came back stuck, reprocesses a batch after a template change, and routes the parsed data onward.
26actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro uploads an email or text document to Parseur for parsing. Support processes customer documents and extracts structured data automatically.
Ayro fetches full details of a parsed document from Parseur. Support confirms extraction succeeded and reviews the results with customers.
Ayro reprocesses a document in Parseur after template fixes. Support recovers failed extractions without requiring customers to upload again.
Each card is one request a support team gets, and the Parseur actions Ayro runs to close it.
Ayro uploads the email or text document to the right mailbox, retrieves it once processed with its parsed results and JSON, CSV, and XLS download URLs, and checks the schema those fields follow.
Ayro reads the processing logs on a document with each entry's status, source, and message, checks which templates the mailbox had to match against, and skips the one that was never going to parse.
Once a template is updated, Ayro lists the documents in the mailbox, re-parses the ones that failed against the new configuration, and copies a document to another mailbox when it landed in the wrong parser.
Ayro enables a paused webhook so document.processed events start firing again, changes its target URL or event type, and defines the CSV or XLS export listing exactly which fields leave the mailbox.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Parseur actions it has and picks the ones a request needs.
Authorize the Parseur account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Parseur actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freeParseur · Ayro
What can you do in Parseur without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Parseur.
Because only paused webhooks can be enabled. Enable Webhook works on entries in available_webhook_set; once enabled the webhook moves into webhook_set and starts POSTing to its target URL when its configured event fires, such as document.processed. Disable Webhook moves it back the other way.
All 26 actions your agent can call on Parseur, straight from the live MCP connection.
Copy a document to another mailbox.
Copy a mailbox (parser) in Parseur.
Create a custom download (export configuration) for a mailbox.
Create a new mailbox (parser) in Parseur.
Delete a custom download (export configuration) from a mailbox.
Delete a specific document by ID.
Delete a mailbox (parser) by ID.
Delete a specific webhook.
Disable a webhook for a mailbox.
Enables a paused webhook for a specified mailbox, allowing it to receive and forward parsed document events.
Retrieve bootstrap configuration data.
Retrieve full details of a specific document by ID.
Get document logs for a specific document.
Retrieve full mailbox (parser) configuration by ID.
Retrieve the JSON schema for a mailbox's parsed fields.
Retrieve custom downloads (export configurations) for a mailbox.
List documents within a specific mailbox.
List mailboxes (parsers) with full configuration details.
List all templates in a given mailbox.
Reprocess a document.
Retrieve details of a specific webhook.
Skip a document.
Update a custom download (export configuration) for a mailbox.
Update a mailbox (parser) configuration.
Update an existing webhook’s settings.
Upload an email or text document to Parseur for parsing.
Same connection, same setup. Pick the next one your team already uses.
Prices and places transcription orders against the prepay balance, returns finished transcripts in four formats, and cancels unstarted files for refund.
Creates, duplicates, and updates document automations, checks the generation queue, and reports where signing sessions stand.
Sends signature requests, reports where each signer stands, chases the ones still outstanding, and cancels or re-sends what went out wrong.
Merges documents into a print job, posts it as physical mail, tracks its progress, and cancels an unshipped job for a refund.
Converts files to PDF, fills form fields from JSON or XML, extracts embedded text, and decodes barcodes from an attached image.
Reads file info and custom metadata, imports files from URLs and stores them permanently, runs virus and moderation checks, and manages file webhooks.

Authorize the account and your agent has all 26 actions from the first conversation.
