Resources · Make integration

Docparser Make integrationAutomate Docparser with Make.

What if every parsed document moved on to your other tools by itself? The Docparser Make integration gives you 7 modules: 1 instant trigger, 3 actions and 3 searches. This guide shows how to link your account, build a first scenario and pick the right module for each job.

Try the Docparser integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Docparser Make integration do for you?

The Docparser Make integration links your Docparser account to Make, a visual tool where you build a scenario: an automation made of modules, each one a single brick such as a trigger, an action or a search. Docparser reads your documents, and Make carries the result wherever it needs to go, with no code.

Parsed data that leaves on its own. Watch Parsed Documents starts your scenario the moment Docparser finishes reading a document. The extracted data then flows to the next module as a bundle, one item passed along the chain, ready to land in a spreadsheet, a CRM or a message to the accounts team.

Files that reach Docparser without a manual upload. When invoices pile up in a mailbox or a shared folder, Upload a Document sends each one to Docparser from inside the scenario. If the file already sits behind a public link, Upload a Document from a URL does the same job from that address.

A quick check of what your account holds. List Document Parsers returns every parser linked to your account, and List Parsed Documents brings back documents already processed, which helps when you catch up on older files or audit a batch.

Make's documentation for this app lists no specific quota, so the limits that matter come from your Make plan. For anything the 7 modules leave out, Make an API Call reaches the rest of the Docparser API with the same connection. If you are weighing both tools, n8n vs Make lays out the criteria. New to the editor? Make training walks through the basics, and Make troubleshooting helps when a run stalls.

Connect

How do you connect Docparser to Make?

  1. 01

    Copy your Docparser API key

    In the Docparser dashboard, open Account, then API Access in the left menu, and copy the API key shown on screen. You need an active Docparser account for this, since the key is what lets Make act on your behalf.

  2. 02

    Add a Docparser module in Make

    Open your scenario, click the +, search for Docparser and pick a module. Then click Create a connection. A connection is your Docparser account linked to Make once, and every Docparser module reuses it afterward.

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you like (this field is optional), paste the API key you copied, and confirm. Make can now read and send documents for this account.

First scenario

Your first scenario with Docparser

GoalWhen a new file lands in another app, such as a mailbox or a storage folder, Make sends it to Docparser for parsing.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. That first module is the trigger of the app where your files arrive.

  2. 02

    Set the trigger of the source app

    Search that app by name, pick its module that watches for new files, and link your account with Create a connection. Make then lists the folders it can read so you can choose one.

  3. 03

    Add Upload a Document

    Click the + on the right of the first module, search Docparser and choose Upload a Document. Map the file coming from the previous module so each new file goes straight to Docparser.

  4. 04

    Test with Run once

    Drop a sample file in the source folder, then click Run once. Open the bubble above each module to read the bundles it received and confirm the file reached Docparser.

  5. 05

    Schedule and switch on

    Open the clock on the first module: a new scenario checks every 15 minutes by default, and the Free plan cannot go below that. Adjust it if your plan allows, then switch the scenario on.

Triggers

What starts a Docparser scenario

1 module starts a scenario when something happens in Docparser. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Docparser as soon as it happens.

Docparser1Watch Parsed Documents

Watch Parsed Documents

Instant trigger

In Make“Triggers when a new document is parsed.”

Watch Parsed Documents gives you the result of each parse the moment Docparser finishes it, so the extracted data can move on without anyone opening the dashboard. Each parsed document arrives as one bundle for the next modules.

How it fires
instant, meaning Docparser calls Make through a webhook as soon as a document is parsed. Make does not poll on a schedule here, so there is no interval to set.
When to use it
your team already sends invoices or forms to Docparser and wants the figures copied into a sheet or CRM right after parsing.
Watch out
when you add it, click Create a webhook before Create a connection, or the trigger will never receive anything.
Modules

What each Docparser module does

Docparser gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Docparser1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call is your way out when none of the other six modules covers the task: it sends a request to any endpoint of the Docparser API, reusing the connection you already set up, so no second key is needed.

When to use it
you need a Docparser feature that has no dedicated module in Make.
Watch out
you write the request yourself, so keep the Docparser API documentation open while you fill it in.
Docparser2

Upload a Document

Action

In Make“Uploads a document to parse.”

With Upload a Document, a file handled earlier in your scenario goes to Docparser for parsing, so nobody has to drag it into the dashboard by hand. It acts on one file per run of the module.

When to use it
invoices arrive as attachments or in a storage folder and you want them parsed without a manual step.
Watch out
map the actual file from the previous module, not just its name, or Docparser gets nothing to read.
Docparser3

Upload a Document from a URL

Action

In Make“Uploads a document that is stored under a publicly accessible URL.”

Upload a Document from a URL hands Docparser a link instead of a file, and Docparser fetches the document from that address itself. It saves a download step when the file already lives online.

When to use it
a form or a supplier portal gives you a link to each PDF rather than an attachment.
Watch out
the link must be publicly accessible; a page behind a login will not work, so pick Upload a Document in that case.
Docparser4

Get Parsed Document

Search

In Make“Retrieves a parsed document.”

Get Parsed Document fetches the result of one document Docparser has already processed, so a scenario can reuse that data later without waiting for a new parse. It is a search module, so Make treats what it finds as bundles.

When to use it
a later step, such as an approval, needs the figures of a document parsed earlier.
Watch out
if nothing matches, the search returns zero bundles and the modules after it simply do not run.
Docparser5

List Document Parsers

Search

In Make“Retrieves all Document Parsers linked to your account.”

This search returns every parser linked to your Docparser account, one bundle per parser. You get an overview of your setup straight inside the scenario, handy before sending files anywhere.

When to use it
you run several parsers, for invoices and for purchase orders say, and a scenario must pick the right one.
Watch out
each parser becomes a separate bundle, and every module placed after this search runs once per bundle, which adds operations.
Docparser6

List Parsed Documents

Search

In Make“Retrieves parsed documents.”

List Parsed Documents brings back documents Docparser has already processed, so you can work through a batch of past results in one scenario instead of one by one.

When to use it
you connect Docparser to Make after months of use and want older parses copied into your new sheet.
Watch out
a long list means many bundles, and every one of them counts operations in the modules that follow; test with Run once before switching on.
Need help

Need help automating Docparser with Make?

A person reads every message.

FAQ

Docparser and Make: common questions

01Is the Docparser Make integration free?
Yes, on the Make side. Docparser is a standard app, available from the Free plan. That plan lets you keep 2 active scenarios, with at least 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module run on one bundle. You also need your own active Docparser account, billed by Docparser.
02What do you need to connect Docparser to Make?
Two things: an active Docparser account and its API key. You find the key in the Docparser dashboard under Account, then API Access in the left menu, and copy it. In Make, add any Docparser module, click Create a connection, optionally name it, and paste the key. That connection is saved once and every Docparser module in your scenarios reuses it. For the Watch Parsed Documents trigger, click Create a webhook first, then Create a connection.
03Does the Docparser trigger in Make react in real time?
Yes. Watch Parsed Documents is an instant trigger: Docparser calls Make through a webhook as soon as a document is parsed, so the scenario starts right away instead of waiting for a scheduled check. You spot it in the editor by the lightning badge on the module. The only condition is the setup order: create the webhook when you add the trigger, then the connection. Other Docparser modules placed later in a scenario run whenever the scenario reaches them.
04What if a Docparser module is missing in Make?
Use Make an API Call. This module can call any endpoint of the Docparser API from your scenario, with the connection you already created, so a missing feature rarely blocks you. It asks for a bit more care, since you shape the request yourself using the Docparser API documentation. Make's documentation for Docparser does not state any specific limit on the 7 modules, so the ceilings you are most likely to meet are those of your Make plan: interval, execution time and file size.
05Should you use Make or n8n with Docparser?
It depends on the tool your team already works in. On Make, Docparser comes as a standard app with 7 modules, including an instant trigger and a Make an API Call module for everything else, and it is open from the Free plan. Many apps also have an n8n node, so if n8n is already in place, check there before adding a second platform. The deciding criteria are the modules you need and the platform your team already knows.
Same platform

Other docs you might need on this stack.

Browse all integrations