Integration · Docs and data
AI agents for Parseur
Extract data from emails and documents with Parseur.
- Actions
- 8
- Read
- 4
- Write
- 4
Actions
What your agents can do in Parseur
Extract data from emails and documents with Parseur: list mailboxes (parsers) and the fields they extract, send a file (PDF, image, spreadsheet) or text and HTML content to be parsed, list and read documents with their parsed results, reprocess and delete documents.
Read 4
Look things up. Nothing changes.
List mailboxes
Lists the account's mailboxes (each one a parser for one kind of document), optionally searching names.
Get a mailbox's fields
Reads the JSON Schema of what a mailbox extracts: every field's name and type, tables as arrays of objects.
List documents
Lists a mailbox's documents, newest first by default, optionally with one status.
Get a document and its data
Reads one document: name, status, received and processed times, the template that matched, credits used, result (the extracted data as a JSON string), content.
Write 4
Create, change or send.
Send text to be parsed
Sends text or HTML (an email, a pasted order, a web page) to a mailbox as a new document, addressed to the mailbox's email address (email_prefix@in.parseur.com from list_mailboxes).
Send a file to be parsed
Uploads a document file (a PDF, an image, a spreadsheet; a person's attachment or another tool's answer, passed as its file reference fil_…, at most 25 MB) to a mailbox as a new document.
Reprocess a document
Parses a document again with the mailbox's current templates and fields, after they were changed or a parse failed.
Delete a documentDeletes data
Permanently deletes a document and its parsed data.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste an API key from your Parseur account.
What you enter
- API key
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Parseur data
Ask a question in plain words. The agent can list mailboxes, get a mailbox's fields or list documents in Parseur, then answers with what it found.
- 02
Let an agent update Parseur
Have the agent send text to be parsed or send a file to be parsed in Parseur as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Parseur and Slack: it can list mailboxes in Parseur and post a summary to a Slack channel in the same run.
FAQ
Parseur and MyDeepAgents
Can MyDeepAgents connect to Parseur?
Yes. The Parseur connector has 8 actions: 4 read and 4 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Parseur?
Paste an API key from your Parseur account. You'll need: API key. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Parseur without asking?
Only if you let it. Each of the 4 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.
Can I use Parseur in workflows as well as agents?
Yes. Every Parseur action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Parseur to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.