Resources · Make integration

DocuPipe Make integrationAutomate DocuPipe with Make.

What if every document DocuPipe reads could land in the right tool on its own? The DocuPipe Make integration gives you 4 modules: 1 instant trigger and 3 actions. This guide connects your account and walks you through a first working scenario.

Try the DocuPipe integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the DocuPipe Make integration automate?

The DocuPipe Make integration links your DocuPipe account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that runs on a schedule or when an app calls Make. Each module is one brick, such as a trigger or an action. DocuPipe brings four of them, so the data it pulls out of your documents can move on without copy and paste.

Pick up every finished document. Watch New Standardizations starts a scenario as soon as DocuPipe has turned a document into standardized JSON, whether the upload came from Make, from the API or from someone using DocuPipe by hand. The JSON then flows to whatever module you add next.

Extract the fields you defined. Extract Data from Document using a Schema sends a PDF or a scan to DocuPipe and returns JSON shaped by your own schema, which you create in your DocuPipe dashboard. Tables, handwriting and odd layouts are part of what it handles.

Hand a file to a DocuPipe workflow. Run a Document through Workflow is there when you already run a workflow inside DocuPipe and want Make to feed it.

For anything the listed modules leave out, Make an API Call reaches the rest of the DocuPipe API with the same connection. If you are still weighing tools, the n8n vs Make comparison lays out the differences, the Make review covers the editor in depth, and Make troubleshooting helps when a run fails.

Connect

How do you connect DocuPipe to Make?

  1. 01

    Copy your API key

    You need an active DocuPipe account and an API key. In DocuPipe, open Settings, choose General in the menu, and copy the API key shown in that section. Keep the tab open, you will paste it in a moment.

  2. 02

    Open the connection window

    In Make, add any DocuPipe module to your scenario and click Create a connection. A connection is your DocuPipe account linked to Make once, then reused by every DocuPipe module you add later.

  3. 03

    Paste the key and save

    Give the connection a name in the Connection name field if you like, since it is optional. Paste the API key you copied, or follow the on-screen instructions, and save. The module can now talk to your account.

First scenario

Your first scenario with DocuPipe

GoalWhen a new file arrives in another app, Make sends it to DocuPipe and gets back JSON shaped by your schema.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to add the first module. This first module decides when the whole scenario starts.

  2. 02

    Start from your file source

    Pick the app where your documents arrive, such as a cloud folder or a mailbox, and choose its module that watches for new files. Connect that account the same way you will connect DocuPipe.

  3. 03

    Add the DocuPipe extraction

    Click the + on the right, search for DocuPipe and pick Extract Data from Document using a Schema. Click Create a connection, paste your API key, map the file from the first module and choose your schema.

  4. 04

    Test with Run once

    Drop a sample document in the source, then click Run once. Open the bubble above the DocuPipe module to read the bundle it returned: the JSON built from your fields.

  5. 05

    Schedule and switch on

    On the first module, keep the default schedule of every 15 minutes or change it, then switch the scenario on. Each new file now goes through DocuPipe without you touching it.

Triggers

What starts a DocuPipe scenario?

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

DocuPipe1Watch New Standardizations

Watch New Standardizations

Instant trigger

In Make“Triggers when a document has been successfully transformed into a standardized JSON. This captures both upload made with make.com and API events, as well as events driven by manual usage of DocuPanda.io.”

You get the finished result of every document DocuPipe processes, handed to your scenario as standardized JSON the moment it is ready. It reacts to uploads made through Make, to API calls, and to documents someone processes by hand in DocuPipe, so nothing slips past.

How it fires
instant: the app calls Make through a webhook as soon as it happens.
When to use it
your team drops invoices into DocuPipe and the extracted totals should reach your accounting sheet without anyone exporting them.
Watch out
because it also catches manual uploads, add a filter after it if only some documents should go further.
Modules

What can DocuPipe do inside a scenario?

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

DocuPipe1

Extract Data from Document using a Schema

Action

In Make“Convert your document (PDF, scan) into a JSON using your own definition of fields you want to extract. Handles tables, handwriting, and any layout. You can use your dashboard on docupanda.io to create a new custom schema and handle your own unique documents.”

Turns a PDF or a scan into JSON that follows your own list of fields, so a delivery note or a form arrives as clean data. Tables, handwriting and unusual layouts are covered.

When to use it
a file lands in another app and you want its key fields extracted right away, in the shape your schema defines.
Watch out
the schema is built in your DocuPipe dashboard, so create it there before you pick it in Make.
DocuPipe2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the whole DocuPipe API to your scenario, using the connection you already set up, so you are not limited to the listed modules.

When to use it
you need an endpoint that no dedicated module covers and would rather not build a separate HTTP request with its own authentication.
Watch out
you write the path and the request body yourself, so keep the DocuPipe API documentation open next to the editor.
DocuPipe3

Run a Document through Workflow

ActionIn the docs only

Judging by its name, this lets Make hand a document to a workflow you run inside DocuPipe, so the processing you already set up there happens without a manual upload.

When to use it
your document handling already lives in a DocuPipe workflow and you only want Make to deliver the files to it.
Watch out
Make publishes no description for this module, so open it in the editor and check its fields before relying on it.
Need help

Need help automating DocuPipe with Make?

A person reads every message.

FAQ

DocuPipe and Make: common questions

01Is the DocuPipe Make integration free?
Yes, on the Make side. DocuPipe is a standard app, so it works from the Free plan onward. That plan allows 2 active scenarios, 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 drop the interval to 1 minute and remove the cap on active scenarios. DocuPipe itself needs an active account and its own subscription, which is covered on the DocuPipe pricing page. Make counts every module run as an operation on your plan.
02What do you need to connect DocuPipe to Make?
An active DocuPipe account and its API key. You find the key in DocuPipe under Settings, then General, where it is displayed and ready to copy. In Make, add a DocuPipe module, click Create a connection, optionally give it a name, and paste the key. For the instant trigger, click Create a webhook before creating the connection. One connection is enough for every DocuPipe module you add afterwards, so you only do this once per account.
03Does the DocuPipe trigger in Make work in real time?
Yes. Watch New Standardizations is an instant trigger: DocuPipe calls Make through a webhook as soon as a document has been turned into standardized JSON. You do not wait for a polling interval, unlike scheduled triggers, which Make checks every 15 minutes by default. The trigger fires for uploads made through Make, for API events and for documents processed by hand in DocuPipe, so a filter placed right after it is useful when only some documents matter.
04What if a DocuPipe action is missing in Make?
Use Make an API Call. It reaches any endpoint of the DocuPipe API from your scenario and reuses the same connection, so there is nothing new to authenticate. The three dedicated actions cover schema extraction, workflows and that open call, with only one trigger. If something still behaves oddly, the Make documentation for DocuPipe is AI-generated from the vendor docs, so double-check important details directly with DocuPipe before building around them.
05Should you use Make or n8n for DocuPipe?
It depends on where your automations already live. In Make, DocuPipe arrives as a ready app with 4 modules, an instant trigger and Make an API Call for the rest, all set up through the visual editor. Many apps also have an n8n node, so check whether DocuPipe has one if your team works in n8n today. Compare the modules each side offers for your documents, the tool your team already knows, and how each one counts runs on its plan.
Same platform

Other docs you might need on this stack.

Browse all integrations