Resources · Make integration

Natif.ai Make integrationAutomate Natif.ai with Make.

What if every incoming document came back as clean, structured data without anyone opening it? The Natif.ai Make integration gives you 5 action modules to send files for processing and collect the results. This page shows how to connect your API key and build a first working flow.

Try the Natif.ai integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Natif.ai Make integration do for you?

The Natif.ai Make integration lets a Make scenario, the automation you build in Make, hand documents to Natif.ai and receive their contents as structured data. Each step of that automation is a module. Natif.ai offers 5 of them, all actions, so the flow always starts with another app or with a schedule set in Make.

Turn uploaded files into rows of data. When a document lands in your storage app or arrives through a form, Upload a Document sends it to Natif.ai and passes the structured values it returns to the next module, for example a spreadsheet or your CRM.

Keep the processed PDF next to the data. After processing, Retrieve PDF Document fetches the PDF Natif.ai generated, and Retrieve Sub PDFs collects the smaller PDFs it produced along the way, so an archive folder can hold both the file and its data.

Share a result with someone outside the flow. Generate Share Token asks Natif.ai for a share token, which the scenario can then pass along in an email or a message.

What Make does not give you here: there is no trigger, so Natif.ai never starts a scenario on its own. For anything the listed modules skip, Make an API call reaches the rest of the Natif.ai API with the same connection. Natif.ai also often has a counterpart in n8n; the n8n vs Make comparison helps you pick a tool, and the Make pricing page explains how runs are counted.

Connect

How do you connect Natif.ai to Make?

  1. 01

    Create an API key in Natif.ai

    In your Natif.ai account, open the API Keys section of the API Hub and click New API key. Give it a name you will recognize, pick an expiration date, click Create and copy the key shown in the window.

  2. 02

    Add a Natif.ai module in Make

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

  3. 03

    Paste the key and save

    Type a label in Connection name if you want one (it is optional), paste the API key you copied, and confirm. The module is then ready to fill.

First scenario

Your first scenario with Natif.ai

GoalWhen a new file shows up in another app, Make sends it to Natif.ai and then collects the processed PDF.

  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 a cloud storage folder, and choose its module that outputs the file.

  2. 02

    Add Upload a Document

    Click the + on the right of that first module, search for Natif.ai and pick Upload a Document. Click Create a connection and paste your API key.

  3. 03

    Map the incoming file

    In the Upload a Document fields, map the file coming from the first module. Each file travels as one bundle, a single item handed from one module to the next.

  4. 04

    Fetch the processed PDF

    Add Retrieve PDF Document after it and map the document information returned by Upload a Document, so Make knows which processed document to fetch.

  5. 05

    Test with Run once

    Drop a test file in the source app and click Run once. Read the bundles each module received and check that the structured values look right.

  6. 06

    Schedule and switch on

    Set the clock on the first module (a new scenario checks every 15 minutes by default, 15 minutes is also the shortest interval on the Free plan) and switch the scenario on.

Modules

What each Natif.ai module does

Natif.ai gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Natif.ai1

Generate Share Token

Action

In Make“Request a share token to be generated”

You get a share token from Natif.ai without leaving the scenario, ready to hand to the next module in an email, a chat message or a record in your CRM.

When to use it
a document has been processed and a colleague or client outside Make needs access to the result.
Watch out
check in your Natif.ai account what a token gives access to before you send one outside your team.
Natif.ai2

Make an API call

Action

In Make“Performs an arbitrary authorized API call.”

This module gives you the rest of the Natif.ai API from inside Make, reusing the connection you already created, so no second key is needed.

When to use it
the four other modules do not cover the request you need, and you know which Natif.ai endpoint handles it.
Watch out
you write the request yourself here, so keep the Natif.ai API documentation open while you set it up.
Natif.ai3

Retrieve PDF Document

Action

In Make“Retrieve the pdf generated during document processing”

Once Natif.ai has processed a file, this module brings back the PDF generated during that processing, so you can store it or attach it wherever the data goes.

When to use it
right after Upload a Document, when your archive should keep the processed PDF next to the extracted values.
Watch out
it only works on a document that has already been processed, so place it after the upload in the flow.
Natif.ai4

Retrieve Sub PDFs

Action

In Make“Retrieve the sub pdf generated during document processing”

Processing can produce several smaller PDFs besides the main one. This module collects those sub PDFs, so each piece can be filed or sent on its own.

When to use it
you care about the individual parts Natif.ai produced rather than the single processed file that Retrieve PDF Document returns.
Watch out
as with the full PDF, it needs a document Natif.ai has already processed earlier in the scenario.
Natif.ai5

Upload a Document

Action

In Make“Returns structured data and values of the input document.”

This is the heart of the app in Make: you send a file and receive its structured data and values, ready to map into a spreadsheet, a database or a CRM.

When to use it
a new document arrives in another app and you want its contents as fields instead of reading it by hand.
Watch out
each document processed counts as an operation, one run of one module that Make counts on your plan.
Need help

Need help automating Natif.ai with Make?

A person reads every message.

FAQ

Natif.ai and Make: frequent questions

01Is the Natif.ai Make integration free?
Yes, on the Make side. Natif.ai is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes 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. Natif.ai itself needs an active account, and its own subscription is described on the Natif.ai pricing page.
02What do you need to connect Natif.ai to Make?
An active Natif.ai account and an API key. In Natif.ai, open the API Keys section of the API Hub, click New API key, give it a name and an expiration date, then click Create and copy the key. In Make, add any Natif.ai module, click Create a connection, optionally name it, and paste the key. That single connection then serves all five Natif.ai modules in your scenarios. Keep an eye on the expiration date you chose: when the key expires, create a new one and update the connection.
03Does the Natif.ai Make integration have a real-time trigger?
No. Natif.ai has no trigger module in Make, so it cannot start a scenario by itself. You start the flow in one of two ways: with a trigger from another app, such as the storage folder or form where your documents arrive, or with a schedule set on the first module, every 15 minutes by default. The Natif.ai modules then run as actions further down the scenario. The first Natif.ai module you add is usually Upload a Document, which receives the file from that starting app.
04What if the Natif.ai module you need is missing in Make?
It depends on the request. The app includes Make an API call, which reaches any endpoint of the Natif.ai API with the connection you already set up, so a missing action does not mean a dead end. You will write the request yourself, so keep the Natif.ai API documentation at hand. Note that the Make documentation for this app is marked as AI-generated and asks readers to verify important details with Natif.ai directly.
05Should you use Make or n8n for Natif.ai?
It depends on the tool your team already runs. Natif.ai often has a node on the n8n side too. On Make, you get the five modules described here, including Make an API call for everything else, and a visual editor with a Run once button to test each step. Pick the platform where your other automations live, so your document flows stay in one place. The n8n vs Make comparison linked earlier on this page lays out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations