Resources · Make integration

Parsio Make integrationAutomate Parsio with Make.

What if the data Parsio pulls out of your documents landed in your other tools on its own? The Parsio Make integration gives you 6 modules, including 4 instant triggers and 2 actions. This page shows how to connect your account and build a first scenario, without code.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Parsio Make integration do for you?

The Parsio Make integration links your Parsio account to Make, so a parsed document, a new attachment or an extracted table can start a scenario (the automation you build in Make, a chain of modules). You pick the modules, Make carries the data from one app to the next.

Extracted data that travels on its own. As soon as Parsio finishes a document, Watch Document Parsed (Flattened) hands the result to Make with table fields laid out as columns, which is the easiest shape to write into a spreadsheet or a CRM.

Line items without the noise. When only the rows of a table matter, for instance the lines of a purchase order, Watch Table Parsed sends those rows and leaves out the other inbox fields.

Documents fed from anywhere. A file that shows up in another app can go to your Parsio inbox through Upload A Document for Parsing, and Parsio extracts its structured data. A second scenario can then start from the parsed result.

What stays outside the listed modules: there is no search module, and anything else the Parsio API offers goes through Make an API Call. If you are weighing other tools, the n8n vs Make comparison helps you choose, and the Make training covers the editor from scratch.

Connect

How do you connect Parsio to Make?

  1. 01

    Add a Parsio module

    In your Make account, add any Parsio module to a scenario. For a module with the instant tag, click Create a webhook first, then Create a connection. The connection is your Parsio account linked once to Make and reused by every Parsio module.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear name helps once several people or several Parsio accounts share the same Make organization. Something like the inbox or the team it serves works well.

  3. 03

    Enter your Parsio credentials

    Paste the credentials copied from your Parsio account: the email you log in with and your password, or follow the on-screen instructions. You need an active Parsio account and an API key to go further.

First scenario

Build your first scenario with Parsio

GoalWhen a file arrives in another app, Make sends it to your Parsio inbox so Parsio can extract its data.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. It belongs to the app where your files arrive, such as an email or storage tool.

  2. 02

    Set up the source module

    Connect that first app and fill its fields. Once the connection exists, Make lists the folders or mailboxes it can read, so you pick them instead of typing a path.

  3. 03

    Add the Parsio action

    Click the + on the right of the first module, search for Parsio and choose Upload A Document for Parsing. Create or pick your connection, then map the file coming from the previous module.

  4. 04

    Test with Run once

    Drop a sample file in the source app and click Run once. Make runs the scenario one time and shows the bundles (the items passed between modules) each module received.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Every file that shows up is now sent to Parsio for extraction.

Triggers

What Parsio events can start a scenario?

4 modules start a scenario when something happens in Parsio. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Parsio as soon as it happens.

Parsio1Watch Attachments

Watch Attachments

Instant trigger

In Make“Triggers when a new email attachment is received.”

This trigger gets you every new email attachment that reaches Parsio, the moment it lands, so the file itself can move on before or alongside the parsing.

How it fires
instant, Parsio calls Make through a webhook as soon as it happens. Make adds a lightning badge on the module.
When to use it
you want to archive the original PDF a supplier emailed in, next to the data Parsio will extract from it.
Watch out
this module is about the attachment, not the extracted fields; for the parsed values, use one of the Watch Document Parsed triggers.
Parsio2Watch Document Parsed

Watch Document Parsed

Instant trigger

In Make“Triggers when a document is parsed.”

Here you receive the full result of a document once Parsio has finished parsing it, ready to write into the next app of your scenario.

How it fires
instant, Parsio calls Make through a webhook as soon as the parsing is done.
When to use it
your document holds a table and you want to keep its structure, for example to loop over the lines with later modules.
Watch out
table fields are not flattened here; if you would rather get them passed as columns, pick the Flattened variant instead.
Parsio3Watch Document Parsed (Flattened)

Watch Document Parsed (Flattened)

Instant trigger

In Make“Triggers when a document is parsed. Table fields are flattened (passed as columns).”

With this one, each parsed document reaches Make with its table fields flattened into columns, which gives you one flat set of values that maps easily into a spreadsheet row.

How it fires
instant, Parsio calls Make through a webhook as soon as the document is parsed.
When to use it
invoices or order confirmations whose fields you copy into a sheet or a CRM record, one line per document.
Watch out
both Watch Document Parsed triggers fire on the same event, so choose the one whose data shape suits the next module before you map anything.
Parsio4Watch Table Parsed

Watch Table Parsed

Instant trigger

In Make“Triggers when a particular table is parsed. Provides parsed table rows without other mailbox fields.”

This trigger delivers only the rows of a specific table once Parsio has parsed it, without the other fields of the mailbox, so your scenario handles clean line items.

How it fires
instant, Parsio calls Make through a webhook as soon as that table is parsed.
When to use it
order lines, bank statement entries or timesheet rows that each need to become a record somewhere else.
Watch out
since the other mailbox fields are left out, add Watch Document Parsed in a separate scenario if you also need the document header.
Modules

What can Make do in Parsio?

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

Parsio1

Make an API Call

Action

In Make“Make an arbitrary call to Parsio's public API.”

This module lets you call any endpoint of Parsio's public API from your scenario, with the connection you already set up, so nothing the API offers is out of reach.

When to use it
the task you have in mind is not covered by the other five modules, for instance a lookup, since the app has no search module.
Watch out
you describe the request yourself, so keep the Parsio API documentation open while you build it.
Parsio2

Upload A Document for Parsing

Action

In Make“Imports a document into the inbox and extracts structured data.”

Send a file into your Parsio inbox and let Parsio extract its structured data, without anyone forwarding emails or uploading by hand.

When to use it
documents reach you through a form, a storage folder or a chat tool rather than by email, and you still want Parsio to read them.
Watch out
to act on the extracted values, build a second scenario that starts with a Watch Document Parsed trigger.
Need help

Need help automating Parsio with Make?

A person reads every message.

FAQ

Parsio and Make: common questions

01Is the Parsio Make integration free?
Yes, Parsio is a standard app in Make, so it is available from the Free plan. That plan allows 2 active scenarios, a minimum interval of 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, remove the cap on active scenarios and allow 40 minutes of execution. Make counts usage in operations, one module running on one bundle. Your Parsio subscription is separate and follows Parsio's own pricing.
02What is needed to connect Parsio to Make?
You need an active Parsio account and an API key, plus a Make account. In the editor, add a Parsio module and click Create a connection; for an instant module, click Create a webhook first. Then enter the credentials from your Parsio account, which are the email you log in with and your password. If you sign in to Parsio with Google, you have no password yet: log out, use the password reset page with your Parsio email and create one from the link you receive.
03Do Parsio triggers in Make fire in real time?
Yes. All 4 Parsio triggers are instant: Parsio calls Make through a webhook as soon as the event happens, whether that is a new attachment, a parsed document or a parsed table. You do not wait for a polling interval, which is what a scheduled trigger would do. Each instant module shows a lightning badge in the editor, and adding one asks you to create a webhook before the connection. The scenario still has to be switched on for Make to receive those calls.
04What if a Parsio module is missing in Make?
Use Make an API Call. It is part of the Parsio app in Make and lets you call any endpoint of Parsio's public API with the same connection as the other modules, so the gaps of the listed modules can be covered. This is also the answer for lookups, since Parsio has no search module in Make. Note that the official Make documentation for Parsio is marked as AI-generated from Parsio's own docs, so check important details with Parsio directly.
05Should Parsio be automated with Make or n8n?
It depends on the tool your team already uses. Parsio exists in Make with 6 modules, including 4 instant triggers, and the same app often has a node in n8n as well, so check both catalogs for your case. If your other automations already run in Make, keeping Parsio there means one place to follow every scenario and one set of connections. If they live in n8n, the same logic applies the other way. The comparison page linked earlier on this page walks through the differences between the two platforms.