Resources · Make integration

Klippa Make integrationAutomate Klippa with Make.

Got documents piling up that someone still retypes by hand? The Klippa Make integration gives you 2 modules: one that parses a document and one that calls any Klippa API endpoint. This page shows you how to connect your API key and build a first scenario.

Try the Klippa integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Klippa Make integration do for you?

The Klippa Make integration links your Klippa account to Make so a document can be read and turned into data without anyone opening it. You send a file or a URL, Klippa extracts the data defined by your template, and Make passes the result to the next app in your scenario, the automation you build step by step.

Stop retyping scanned paperwork. A PDF lands in a shared folder or arrives as an email attachment through another app's module. Parse a Document reads it, and the extracted values flow on to a spreadsheet or a CRM record. The file can come straight from the previous module or through a URL.

Read phone photos, not just PDFs. Field staff often snap a picture instead of scanning. Klippa accepts GIF, PNG, JPG and HEIC/HEIF files too, so an iPhone photo goes through the same scenario as a clean PDF.

Reach the parts of Klippa the list does not cover. Only two modules exist. When you need another endpoint of the Klippa API, Make an API Call uses the same connection and lets you send that request yourself.

What Make does not give you here: no trigger. Klippa never starts a scenario on its own, so the first module always belongs to another app or to Make's schedule. If you also run n8n, the n8n vs Make page lays out how the two tools differ. To go further on the editor itself, see our Make training, or read the Make review before you commit.

Connect

How do you connect Klippa to Make?

  1. 01

    Copy your API key in Klippa

    You need an active Klippa account and an API key. In Klippa, open Settings from the main menu, go to the API Access tab, and copy the key shown on screen. Keep it at hand for the next step.

  2. 02

    Add a Klippa module in Make

    In your scenario, add Parse a Document and click Create a connection. A connection is your Klippa account linked to Make once; every Klippa module reuses it afterwards. You can type a label in Connection name if you manage several accounts.

  3. 03

    Paste the key and save

    Paste the API key you copied from Klippa into the credentials field and confirm. If Make shows other on-screen instructions, follow them. Once saved, the connection appears in the module's dropdown and you can fill in the rest of its settings.

First scenario

Build your first scenario with Klippa

GoalWhen a new file shows up in another app, Make sends it to Klippa and passes the parsed data on.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. Pick the app that holds your files, a storage or email app, and choose the module that watches for new items.

  2. 02

    Add Parse a Document

    Click the + on the right of that first module, search for Klippa and pick Parse a Document. Select the connection you created, or click Create a connection if you have not yet.

  3. 03

    Map the file

    Fill in the module: map the file coming from the first module, or a URL pointing to it. What comes back follows the Klippa template used, so make sure it fits this kind of document.

  4. 04

    Test with Run once

    Drop a sample document in the source app, then click Run once. Read the bundle Parse a Document returned, that is the item handed to the next module, and check the extracted values.

  5. 05

    Schedule and switch it on

    Click the clock on the first module to set its schedule, every 15 minutes by default. Add a module after Klippa to store the data where your team works, then switch the scenario on.

Modules

What the Klippa modules do

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

Klippa1

Make an API Call

Action

In Make“Makes a request using the Rest API standard.”

Call any endpoint of the Klippa API from your scenario, with the connection you already set up. The response comes back as a bundle.

When to use it
you need a Klippa feature that Parse a Document does not expose, and you have the Klippa API reference open to find the right endpoint.
Watch out
every call counts as an operation, one module run on your Make plan, so test it with Run once before you schedule it.
Klippa2

Parse a Document

Action

In Make“Parses a document locally or through a URL and extracts data based on the template used. Parses GIF, PNG, JPG, HEIC/HEIF or PDF files.”

Hand it a file and get back structured data, following the Klippa template used. It reads GIF, PNG, JPG, HEIC/HEIF and PDF, from a previous module or a URL.

When to use it
a scanned form or a phone photo enters your scenario and its content has to land in a spreadsheet or a CRM.
Watch out
the output depends entirely on the template, so a document parsed with the wrong one comes back with the wrong data. On the Free plan, files are capped at 5 MB.
Need help

Need help automating Klippa with Make?

A person reads every message.

FAQ

Klippa and Make: common questions

01Is the Klippa Make integration free?
Yes, on the Make side. Klippa is a standard app, so its modules are available from the Free plan, which allows 2 active scenarios, a minimum 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 lower the interval to 1 minute and count usage in operations per month. You still need your own Klippa subscription with API access, which Make does not include.
02What do you need to connect Klippa to Make?
An active Klippa account and an API key. You find the key in Klippa under Settings, in the API Access tab, and paste it when Make asks for it after you click Create a connection on any Klippa module. Naming the connection is optional but helps when you run several Klippa accounts. The same connection then serves both modules, Parse a Document and Make an API Call, so you only set it up once.
03Can Klippa start a Make scenario in real time?
No, Klippa has no trigger module in Make, so it never starts a scenario by itself. Your scenario opens on another app instead: a storage or email module that picks up the new file, or a scheduled start from Make, every 15 minutes by default and down to 1 minute on paid plans. Klippa then comes second, with Parse a Document reading the file the first module delivered, so the speed of the whole chain follows that first module.
04What if the Klippa module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Klippa API with the connection you already have, so you are not limited to Parse a Document. You write the request following the Klippa API reference, and the response comes back as a bundle you can map into the next module. If a result looks off, check the Klippa documentation directly: the Make doc for this app warns it was generated with AI and may contain mistakes.
05Should you use Make or n8n for Klippa?
It depends on the tool your team already runs. Many apps have a node in n8n as well as modules in Make, so check both catalogs for Klippa before you decide. In Make, you get Parse a Document for the everyday job and Make an API Call for the rest of the API, both on the Free plan. Pick the platform where your other scenarios and connections already live, so the parsed data joins the flows you maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations