Automate Pappers With Make: 4 Modules, Zero Code Needed

What you can automate

What can the Pappers Make integration do for you?

The Pappers Make integration links your Pappers account to Make, a tool where you chain apps together without writing code. Each automation you build there is a scenario: a row of modules, where every module is one brick that searches, reads or acts in one app. Pappers brings four of those bricks, all of them things you ask Pappers for.

Enrich a lead the moment it shows up. A company name arrives from a form or a CRM, Search for companies finds the match in Pappers, and Get a company information pulls its record so your sales team reads it next to the lead instead of opening another tab.

Keep company documents with the client file. Once a company is identified, Download a File retrieves a file from Pappers and hands it to the next module, which can store it in the folder or drive your team already uses.

Reach what the menu does not list. Four modules cover the common requests. For anything else the Pappers API offers, Make an API Call sends your own request with the connection you already set up.

Keep one limit in mind: Make itself says its Pappers documentation is incomplete, because little public information about the app exists. Test each module with real data before you rely on it. If you hesitate between tools, the n8n vs Make comparison lays out the criteria, and the Make review gives a wider look at the platform. The Make training is there when you want to go further.

Connect

How do you connect Pappers to Make?

01
Open the connection window
Add any Pappers module to your scenario, then click Create a connection. A connection is your Pappers account linked to Make once; every Pappers module in every scenario reuses it afterward.
02
Give it a clear name
Naming is optional, but a label such as "Pappers sales team" saves you guessing later if several accounts or colleagues end up sharing the same Make organization.
03
Authorize and save
Make then asks for access: either you approve it on a Pappers page, or you paste the key Pappers gives you. Follow whichever the window shows, then click Save to finish.

First scenario

Your first scenario with Pappers

GoalWhen a new company name reaches your pipeline, Make finds it in Pappers and brings back its record.

01
Create the scenario
On the Scenarios page, create a new scenario and click the + to add the first module. Pick the trigger of the app where your new leads appear, since Pappers has no trigger of its own.
02
Add the search
Click the + on the right, search for Pappers and choose Search for companies. Click Create a connection if this is your first Pappers module, then map the company name from the first module.
03
Pull the company record
Add Get a company information after the search and map the company it found. Make lists what it can read once the connection exists, so you pick values instead of typing them.
04
Test with Run once
Click Run once. Make runs the scenario one time and shows the bundles each module received, a bundle being one item passed along, here one company. Check that the right company came back.
05
Schedule and switch on
Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. From now on it runs without you.

Modules

What the Pappers modules do

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

Pappers1

Download a File

ActionIn the docs only

You get a file from Pappers delivered straight into your scenario, ready for the next module to store, attach or send. No manual download, no lost attachment in someone's inbox.

When to use it

after the company is identified, when your team wants the document filed next to the client record.

Watch out

on the Free plan Make handles files up to 5 MB, so a heavier document needs a paid plan.

Pappers2

Get a company information

ActionIn the docs only

This one gives you the record of a single company, so the details you usually look up by hand land in your CRM or sheet on their own. It acts on one company at a time.

When to use it

you already know which company you want, for instance right after a search found it, and you need its full profile.

Watch out

Make documents Pappers only partially, so run it once and read what comes back before mapping it anywhere.

Pappers3

Make an API Call

ActionIn the docs only

Here you reach any part of the Pappers API that the three other modules skip, reusing the connection you already created. It is the escape hatch when the menu comes up short.

When to use it

a request your team needs has no dedicated module, and you are comfortable reading the Pappers API documentation.

Watch out

you write the request yourself, so one wrong detail in it and the call fails; test it with Run once first.

Pappers4

Search for companies

SearchIn the docs only

With this search, a name or a partial lead turns into matching Pappers companies you can feed to the rest of the scenario. Unlike an action, a search can return zero, one or several bundles.

When to use it

a lead arrives with a company name but nothing more precise, and you need to find which company it is.

Watch out

several matches mean the following modules run once per company, and each run counts as an operation on your plan.

Need help

Need help automating Pappers with Make?

A person reads every message.

FAQ

Pappers and Make: common questions

01Is the Pappers Make integration free?

Yes, on the Make side. Pappers is a standard app, available from the Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between two scheduled runs, runs of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Make counts usage in operations, one per module per bundle. Your Pappers account itself is a separate matter that this page does not cover.

02What do you need to connect Pappers to Make?

A Pappers account and a Make account. Make's documentation lists no specific prerequisite for Pappers and gives no dedicated connection steps, so the generic flow applies: add a Pappers module, click Create a connection, name it if you like, then either approve access on a Pappers page or paste the key Pappers provides, and click Save. The connection is stored once and reused by every Pappers module you add later.

03Can a Pappers scenario start on its own in Make?

Not from Pappers itself, because the app has no trigger module. You start the scenario another way. Either you open it with the trigger of another app, such as the tool where your leads arrive, or you run it on a schedule set with the clock on the first module. A new scenario checks every 15 minutes by default; the Free plan does not go below 15 minutes, paid plans go down to 1 minute. Pappers modules then run in the middle of the flow.

04What if a Pappers module you need is missing in Make?

Use Make an API Call. It sends any request the Pappers API accepts, through the same connection as the other modules, so you are not limited to the 4 listed ones. You will need the Pappers API documentation to write the request. Also keep in mind that Make flags its own Pappers documentation as limited, for lack of public information. Testing each module with Run once before switching a scenario on is the safest habit.

05Should you use Make or n8n for Pappers?

It depends on your team rather than on Pappers. The facts on the Make side are simple: 4 Pappers modules, including Make an API Call for anything missing, and a visual editor where you test with Run once. n8n often offers a node for the same app, so check whether it covers the requests you need before choosing. Pick the tool your team already knows and where your other apps are connected.

Open the connection window

Give it a clear name

Authorize and save

Create the scenario

Add the search

Pull the company record

Test with Run once

Schedule and switch on

Need help automating Pappers with Make?