Skip to content

Start building

Integration · Docs and data

AI agents for Docparser

Send documents (PDFs, scans, Word files) at public links to a Docparser parser, follow their processing and read the extracted data: invoice fields, table rows and whatever the parser's rules pull out.

Actions
7
Read
5
Write
2

Actions

What your agents can do in Docparser

7 actions. Each one is a tool your agents can call and a step your workflows can run.

Read 5

Look things up. Nothing changes.

  • List parsers

    Lists the account's document parsers, each with id and label.

  • List a parser's layouts

    Lists the model layouts a parser has learned (one per document layout it was trained on), each with id and label.

  • Get a document's status

    Says where a document is in processing: importing_in_progress, processing_in_progress, processed_at (set once its data is ready), pages, filename, failed_jobs and webhook delivery.

  • Get a document's data

    Reads the data extracted from one document: the parser's fields (table rows as lists of objects) plus document_id, remote_id, file_name, page_count, uploaded_at, processed_at and links to the file.

  • List a parser's results

    Lists the extracted data of a parser's documents, most recently uploaded first, or only those uploaded or processed after a date, or with one remote_id.

Write 2

Create, change or send.

  • Send a document from a link

    Has Docparser download a document from a public link and parse it with the given parser, optionally tagged with your own remote_id (passed through to results).

  • Parse documents again

    Runs a parser's current rules over documents it already has, after its rules were changed.

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.

Connection

How it connects

Connect it once in the console, then give it to the agents and workflows that need it.

Username and key

Enter the API credentials from your Docparser account.

What you enter

  • Secret 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.

How we protect your data

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 Docparser data

    Ask a question in plain words. The agent can list parsers, list a parser's layouts or get a document's status in Docparser, then answers with what it found.

  • 02

    Let an agent update Docparser

    Have the agent send a document from a link in Docparser 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 Docparser and Slack: it can list parsers in Docparser and post a summary to a Slack channel in the same run.

FAQ

Docparser and MyDeepAgents

Can MyDeepAgents connect to Docparser?

Yes. The Docparser connector has 7 actions: 5 read and 2 make changes. Your agents can call them as tools, and your workflows can run them as steps.

How do I connect Docparser?

Enter the API credentials from your Docparser account. You'll need: Secret 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 Docparser without asking?

Only if you let it. Each of the 2 actions that change data can be set to wait for a person's approval before it runs.

Can I use Docparser in workflows as well as agents?

Yes. Every Docparser action also works as a step in a workflow, and the same connection serves your agents and your workflows.

Early access

Put Docparser to work

Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.