Resources · Make integration

Klippa DocHorizon Make integrationAutomate Klippa DocHorizon with Make.

Can Make read bank statements, payslips and ID documents for you? The Klippa DocHorizon Make integration adds 13 action modules that parse documents inside an automation. This page shows how to link your account, then walks you through a first working flow.

Try the Klippa DocHorizon integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Klippa DocHorizon Make integration do?

The Klippa DocHorizon Make integration lets a Make scenario, the automation you build as a chain of modules, send a document to Klippa DocHorizon and get its content back as data. A module is one brick of that chain, and every Klippa DocHorizon module here is an action: something else has to start the scenario.

Payslips checked before payroll closes. An HR team drops payslips in a shared folder; that folder's trigger starts the scenario and Parse a Salary Slip hands the content to the next module, a sheet or a message to the payroll manager.

Customer onboarding without retyping IDs. Parse an Identity Document reads the ID a new client uploads, so the account manager gets the details in the CRM instead of copying them from a scan.

Odd documents handled too. When a file fits no dedicated module, Parse a Document Using a Custom Prompt Builder lets you state what to extract, and Make an API call covers any request the parse modules leave out.

What Make does not give you here: a trigger inside Klippa DocHorizon, and full documentation, since Make flags its own guide for this app as limited for lack of public information. Many apps also exist as an n8n node; the n8n vs Make comparison helps you pick a tool. To learn the editor properly, see Make training, and keep Make troubleshooting close when a run fails.

Connect

How do you connect Klippa DocHorizon to Make?

  1. 01

    Add a Klippa DocHorizon module

    In your scenario, click the +, search for Klippa DocHorizon and pick any of its modules. Then click Create a connection: the connection is your Klippa account linked to Make once, reused by all 13 modules afterwards.

  2. 02

    Name the connection

    Giving the connection a name is optional, yet it pays off when a colleague or a second Klippa account joins later. A name such as "Klippa finance" tells everyone at a glance which account a module is using.

  3. 03

    Authorize and save

    Depending on what Make asks, either approve access on the Klippa DocHorizon page that opens, or paste the key that Klippa DocHorizon gives you. Click Save, and the module can now use your account.

First scenario

Your first scenario with Klippa DocHorizon

GoalWhen a financial document lands where your team stores files, Make sends it to Klippa DocHorizon and passes the parsed content on.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the trigger of the app where your financial documents arrive, a cloud folder or a mailbox, and connect it.

  2. 02

    Add Parse a Financial Document

    Click the + on the right of the first module, search for Klippa DocHorizon and choose Parse a Financial Document. Click Create a connection if this is your first Klippa module.

  3. 03

    Map the document

    Fill the module fields and map the file from the previous module. Each file flows as a bundle, one item passed from module to module, so each document gets parsed on its own.

  4. 04

    Test with Run once

    Drop a real document in the source, then click Run once. Open the bubble above Parse a Financial Document to read the bundle it returned before you add a sheet or a CRM after it.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Modules

What each Klippa DocHorizon module does

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

Klippa DocHorizon1

Make an API call

ActionIn the docs only

Make an API call gives you access to any endpoint of the Klippa DocHorizon API from your scenario, reusing the connection you already created.

When to use it
the parse modules below do not cover the request you need, or a setting you want is missing from their fields.
Watch out
you write the request yourself and Make's limited guide for this app will not tell you what to send, so check the result with Run once.
Klippa DocHorizon2

Parse a Bank Statement

ActionIn the docs only

Parse a Bank Statement turns a statement your scenario received into content the next modules can map, so nobody retypes lines by hand.

When to use it
an accountant collects client statements by email and wants them in a spreadsheet without copying rows.
Watch out
the documentation says nothing about the output, so click Run once on a real statement and read the bundle before mapping.
Klippa DocHorizon3

Parse a Bank Statement Async

ActionIn the docs only

You get a second way to process bank statements; the Async suffix marks this module as the asynchronous variant of Parse a Bank Statement.

When to use it
you tested the standard module and want to see how the other variant hands its result to the next step.
Watch out
Make does not document the difference between the two, so test both on the same statement before choosing.
Klippa DocHorizon4

Parse a Document Using a Custom Prompt Builder

ActionIn the docs only

Here you describe yourself what should be pulled out of a document, instead of relying on a fixed document type chosen by Klippa.

When to use it
the file is neither a bank statement, a payslip, an ID nor a financial document, say a delivery note or a lease.
Watch out
the prompt builder settings are not documented, so rely on the fields Make shows once the connection exists.
Klippa DocHorizon5

Parse a Document Using a Custom Prompt Builder Async

ActionIn the docs only

Your custom prompt also runs in an asynchronous flavor, as the Async suffix of this module's name signals.

When to use it
you already shaped your prompt with the standard version and want to try the other variant on the same file.
Watch out
nothing in the documentation explains how their results differ, so compare the bundles of both after a Run once.
Klippa DocHorizon6

Parse a Financial Document

ActionIn the docs only

Bookkeeping flows start from this one: it gives the rest of your scenario the content of a financial document, so entry by hand disappears.

When to use it
supplier documents land in a shared folder and the finance team wants them logged in one place.
Watch out
the documentation does not list which document types it recognizes, so try it on your own files with Run once before activating.
Klippa DocHorizon7

Parse a Financial Document Async

ActionIn the docs only

A second option for financial paperwork: this module is the variant of the financial document parser flagged Async in its name.

When to use it
your finance scenario works with the standard module and you want to measure how the other variant behaves on the same files.
Watch out
keep a single variant per scenario once you decide, or each document is parsed twice and costs two operations.
Klippa DocHorizon8

Parse a Generic Doument

ActionIn the docs only

Files that fit no specialized module still get read: this is the general parser of the app, spelled exactly this way in Make.

When to use it
a mixed inbox receives letters, forms and scanned pages that no dedicated module targets.
Watch out
type the module name with its real spelling, Doument, when you search, or the list in Make may look empty.
Klippa DocHorizon9

Parse a Generic Doument Async

ActionIn the docs only

The general parser also exists as an asynchronous variant, which the Async suffix points out, and it keeps the same Doument spelling.

When to use it
your catch-all flow already runs with Parse a Generic Doument and you want to compare with the other variant.
Watch out
both variants look alike in the module list, so check the full name before you save the scenario.
Klippa DocHorizon10

Parse a Salary Slip

ActionIn the docs only

Payroll checks get faster when the payslip content reaches your scenario as data rather than as a PDF someone has to open.

When to use it
HR receives payslips from a payroll provider and wants to review them in one sheet before payday.
Watch out
payslips hold personal data, so keep test files and the bundles you read after Run once to people allowed to see them.
Klippa DocHorizon11

Parse a Salary Slip Async

ActionIn the docs only

This one reads payslips too, as the asynchronous variant of Parse a Salary Slip that its Async suffix announces.

When to use it
you want to compare both payslip modules on the same file before building the whole HR flow on one of them.
Watch out
the documentation gives no detail on what the variant changes, so base your choice on what Run once shows.
Klippa DocHorizon12

Parse an Identity Document

ActionIn the docs only

Customer and staff onboarding stops depending on copy and paste: the module reads an ID document and hands its details to the next step.

When to use it
a new client uploads an ID through a form and the account manager wants the record filled in the CRM.
Watch out
ID scans are sensitive, so restrict who can open the scenario and its test bundles.
Klippa DocHorizon13

Parse an Identity Document Async

ActionIn the docs only

ID documents can also go through this asynchronous variant, marked by the Async suffix, instead of Parse an Identity Document.

When to use it
your onboarding flow works and you want to test the other variant on the same scans before settling.
Watch out
the gap between the two is undocumented, so compare the bundles of both after a Run once rather than guessing.
Need help

Need help automating Klippa DocHorizon with Make?

A person reads every message.

FAQ

Questions about Klippa DocHorizon and Make

01Is the Klippa DocHorizon Make integration free?
Yes, on the Make side. Klippa DocHorizon is a standard app, so its 13 modules are available from the Free plan. That plan allows 2 active scenarios, at least 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 (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and allow 40 minutes of execution. Your Klippa DocHorizon account is a separate matter, and this page gives no price for it.
02What do you need to connect Klippa DocHorizon to Make?
A Klippa DocHorizon account and a Make account; the documentation lists no other prerequisite. Add any Klippa DocHorizon module, click Create a connection, name it if you like, then either approve access on the Klippa page or paste the key Klippa gives you, and save. The connection is created once and reused by all 13 modules. Since Make flags its guide for this app as limited, a quick Run once is the fastest way to confirm the connection works.
03Does Klippa DocHorizon trigger scenarios in real time?
No, because the app has no trigger module in Make: all 13 modules are actions. The scenario has to start from something else. The first option is the trigger of the app where your documents arrive, such as a cloud folder or a mailbox, followed by a Klippa DocHorizon module. The second is a schedule on the first module: a new scenario runs every 15 minutes by default, the minimum on the Free plan, while paid plans go down to 1 minute.
04What if a Klippa DocHorizon module is missing in Make?
Use Make an API call. This module calls any endpoint of the Klippa DocHorizon API from your scenario, with the same connection as the other modules, so a request the parse modules do not offer stays within reach. Make also warns that its documentation for this app is limited for lack of public information, so test each request with Run once and read the bundle it returns before building on it. On the Free plan, keep the 5 MB file limit in mind when you send scans.
05Make or n8n for Klippa DocHorizon?
It depends on the tool your team already uses and on the document you need to read. In Make, Klippa DocHorizon comes with 13 modules: six parsers for specific or custom documents, each in a standard and an Async version, plus Make an API call. Many apps also have a node in n8n, so check whether Klippa DocHorizon is one of them before deciding. Compare what each tool offers for your exact document type rather than choosing on reputation.
Same platform

Other docs you might need on this stack.

Browse all integrations