Resources · Make integration

Airparser Make integrationAutomate Airparser with Make.

What happens to a document after Airparser reads it? The Airparser Make integration gives you 4 modules: 1 instant trigger and 3 actions. This page shows how to link your account, build a first scenario and pick the right module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Airparser Make integration do for you?

The Airparser Make integration links your Airparser account to Make, a tool where you build automations called scenarios without writing code. Make can send documents to Airparser for extraction, then react the moment a document is parsed and pass the extracted data to another app.

Feed the parser without opening Airparser. A supplier invoice arrives as an attachment in another app. Upload a Document for Parsing pushes the file into your Airparser inbox, where the extraction runs. Nobody has to drag files by hand anymore.

Send clean data where the team works. Watch Document Parsed starts a scenario as soon as Airparser finishes a document. The next module, from a spreadsheet or a CRM, receives the extracted values. A related guide: the Airtable Make integration.

Reach what the list does not cover. Only 3 actions exist. When you need another part of the Airparser API, Make an API Call uses the same connection to call it.

Limits to know: the Make documentation for Airparser warns that its content is AI-generated from the vendor docs, so check important details with Airparser. On the Free plan, files are capped at 5 MB. Airparser often has an n8n node too; to weigh the two tools, read n8n vs Make, and for costs, see Make pricing.

Connect

How do you connect Airparser to Make?

  1. 01

    Add an Airparser module

    Log in to Make, open your scenario and add any Airparser module. Then click Create a connection. A connection is your Airparser account linked to Make once, and every Airparser module reuses it afterwards.

  2. 02

    Name the connection

    The Connection name field is optional. A clear name still helps when several people or several Airparser accounts share the same Make organization, because you pick the right one from a list later.

  3. 03

    Enter your Airparser credentials

    Airparser asks for an active account and an API key. For the basic credentials, use the email you log in to Airparser with and your Airparser password, then follow the instructions on screen to finish.

First scenario

Your first scenario with Airparser and Make

GoalWhen a new file shows up in another app, Make sends it to Airparser, which extracts its data.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where your files arrive, such as your mailbox or your cloud storage, and choose its trigger module.

  2. 02

    Add the Airparser module

    Click the + on the right of that first module, search Airparser and pick Upload a Document for Parsing. Link your account with Create a connection if it is your first time.

  3. 03

    Map the file

    Fill the module fields. Make lists what it can read once the connection exists, and you map the file coming from the first module. Each item passing between modules is a bundle: here, one file.

  4. 04

    Test with Run once

    Click Run once and drop a sample file into the source app. Open the bundles each module received to confirm the document reached Airparser and came back with data.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module. A new scenario runs every 15 minutes by default. Then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Triggers

What starts an Airparser scenario

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

Airparser1Watch Document Parsed

Watch Document Parsed

Instant trigger

In MakeTriggers when a document is parsed.

Your scenario starts with the extracted data in hand, right after Airparser finishes reading a document. Every parsed document becomes a bundle that the next modules can use, so the values reach your spreadsheet, CRM or team chat without a copy and paste.

How it fires
instant, Airparser calls Make through a webhook as soon as a document is parsed.
When to use it
documents land in Airparser from several sources and you want one place that routes their data onward.
Watch out
when you add this module, click Create a webhook before Create a connection, or Make has nothing to listen to.
Modules

What Airparser can do in Make

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

Airparser1

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Gives you access to any endpoint of the Airparser API from your scenario, with the connection you already set up. It fills the gaps left by the other modules.

When to use it
the action you need is in the Airparser API but none of the 3 listed modules does it.
Watch out
you write the request yourself, so keep the Airparser API documentation open while you build it.
Airparser2

Upload a Document for Parsing

Action

In MakeImports a document into the inbox and extracts structured data.

Hands a file to Airparser and gets structured data out of it. The document goes into your Airparser inbox, where the extraction runs, so an invoice or a form turns into values you can map.

When to use it
files arrive in another app and you want them parsed without uploading them by hand.
Watch out
on the Free plan, Make handles files up to 5 MB, so check the size of large scans before you rely on this module.
Airparser3

Upload a Document for Parsing (Async)

ActionIn the docs only

Judging by its name, it also sends a document to Airparser, in an Async variant. The Make documentation gives it no description, so what it returns is not documented.

When to use it
you have tested it with Run once and the bundle it returns suits your flow better than the regular upload.
Watch out
read that test bundle carefully before you map anything, since nothing in the docs says what it contains.
Need help

Need help automating Airparser with Make?

A person reads every message.

FAQ

Airparser and Make: common questions

01Is the Airparser Make integration free?
Yes, on the Make side. Airparser is a standard app, available from the Free plan, which is one of the 3,000+ standard apps offered on every plan. The Free plan allows 2 active scenarios, a minimum of 15 minutes between two 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 allow 40 minutes of execution. Airparser itself needs an active account with its own subscription, described on the Airparser pricing page.
02What do you need to connect Airparser to Make?
You need an active Airparser account and an API key, plus a Make account. In any Airparser module, click Create a connection, give it a name if you like, then enter your credentials. The basic credentials are the email you use to log in to Airparser and your Airparser password. If you sign in with Google, log out and reset your password to create one first. For the instant trigger, click Create a webhook before Create a connection.
03Does the Airparser trigger in Make react in real time?
Yes. Watch Document Parsed is an instant trigger: Airparser calls Make through a webhook as soon as a document is parsed, instead of Make checking on a schedule. The scenario starts right after the extraction, with the parsed document as a bundle. The upload modules are actions, so a scenario that only uses them needs a first module to start it, such as a trigger from another app, or a schedule set on the first module, every 15 minutes by default.
04What if an Airparser module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Airparser API with the connection you already have, so an action outside the 3 listed modules is still possible. You build the request yourself from the Airparser API documentation. Also note that the Make documentation for Airparser is AI-generated from the vendor docs and may contain mistakes, so check important details with Airparser directly before you rely on them in a live scenario.
05Make or n8n for Airparser?
It depends on the tool your team already uses. Airparser often has an n8n node as well, so both can usually connect it. In Make, you get 4 ready modules, including an instant trigger for parsed documents and a universal API call, and you build without code in a visual editor. If your other automations already run in one of the two tools, keeping Airparser there is usually the simplest choice. Compare the features you need rather than the brand.