Resources · Make integration

Rossum Make integrationAutomate Rossum with Make.

Can invoices reach Rossum without anyone dragging files around? The Rossum Make integration gives you 2 action modules: one sends an invoice in, one exports an annotation out. This page shows how to link your account and build a first working scenario.

Try the Rossum integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Rossum Make integration do for you?

The Rossum Make integration lets a Make scenario, the automation you build in Make as a chain of modules, hand invoices to your Rossum account and export the annotations Rossum holds. Each module is one brick of that chain. Rossum has no trigger of its own in Make, so something else starts the run.

Invoices that file themselves into Rossum. When a supplier invoice lands in another tool your scenario watches, Upload Invoice passes the file to Rossum so nobody uploads it by hand. The other app's trigger does the watching; Rossum receives.

Annotations that leave Rossum on their own. Export an Annotation pulls an annotation out of Rossum so the next module can store it where your finance team works, for example a base covered on our Airtable Make integration page.

Both steps in one flow. You can chain the two modules with other apps around them, each one working on one bundle, which is one item passed from module to module.

Know the limits before you start. The integration has 2 modules and no search, no trigger and no Make an API Call module, so anything beyond uploading an invoice and exporting an annotation is out of reach from this app alone. The Rossum documentation gives no numeric limit either.

If you are weighing tools, the same app often exists as an n8n node too; our n8n vs Make comparison lays out the criteria, and the Make pricing page explains what each plan includes.

Connect

How do you connect Rossum to Make?

  1. 01

    Add a Rossum module

    In your scenario, add Upload Invoice or Export an Annotation, then click Create a connection. A connection is your Rossum account linked to Make once and reused by every Rossum module afterward. You need an existing Rossum account for this.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, which helps when several accounts live side by side. Then authorize Make on the Rossum page that opens, or paste the key Rossum gives you, depending on what the window asks for.

  3. 03

    Save and reuse

    Click Save. The connection now appears in the dropdown of every Rossum module, so the second module you add picks it straight away instead of asking you to log in again.

First scenario

Build your first scenario with Rossum

GoalWhen an invoice shows up in another app, Make sends it to Rossum with Upload Invoice.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Since Rossum has no trigger, pick the trigger of the app where your invoices arrive.

  2. 02

    Add Upload Invoice

    Click the + on the right of that first module, search for Rossum and choose Upload Invoice. Select your connection or click Create a connection.

  3. 03

    Map the invoice file

    Fill the module fields and map the file coming from the first module. Once connected, Make lists what it can read in your Rossum account, so you choose rather than type.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open each module's bubble to read the bundles it received and confirm the invoice reached Rossum.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. From then on, invoices travel to Rossum without you.

Modules

What the Rossum modules do

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

Rossum1

Export an Annotation

Action

In Make“Exports an annotation.”

You get an annotation out of Rossum and into the rest of your scenario, where the next module can store it, send it or pass it to another tool your team already uses.

When to use it
after Rossum has worked on a document and you want its annotation to land in your accounting sheet or database without copying anything.
Watch out
the module acts on one annotation per bundle, and each run of it is one operation, the unit Make counts on your plan.
Rossum2

Upload Invoice

Action

In Make“Uploads an invoice.”

This one saves you the manual upload: an invoice file coming from an earlier module is pushed into your Rossum account so Rossum can start working on it.

When to use it
a supplier emails a PDF or drops it in a shared folder, and you want it in Rossum the moment your scenario picks it up.
Watch out
on the Free plan Make handles files up to 5 MB, so keep an eye on the size of scanned invoices before they reach this module.
Need help

Need help automating Rossum with Make?

A person reads every message.

FAQ

Rossum and Make: frequently asked questions

01Is the Rossum Make integration free?
Yes, Rossum is a standard app, so it works from the Free plan onward. That plan comes with limits worth knowing: 2 active scenarios, at least 15 minutes between 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, remove the cap on active scenarios and allow 40 minutes of execution. Whatever the plan, Make counts your usage in operations per month, and you still need your own Rossum account to create the connection.
02What do you need to connect Rossum to Make?
You need a Rossum account and a Make account, nothing more. The Rossum documentation does not publish specific connection steps, so the generic Make flow applies: add a Rossum module, click Create a connection, optionally give it a name, authorize Make on the Rossum page or paste the key Rossum provides, then click Save. That connection is stored once and reused by both Rossum modules, Upload Invoice and Export an Annotation. If the authorization fails, check which Rossum account is signed in and try again.
03Does the Rossum Make integration react in real time?
No, because Rossum has no trigger module in Make, so nothing in Rossum can start a scenario on its own. You start it in one of two ways. Either a trigger from another app opens the scenario, for example the app where invoices first arrive, and the Rossum modules follow it. Or you rely on the scenario's scheduling, the clock on the first module, which runs every 15 minutes by default and can go down to 1 minute on a paid plan. In both cases Rossum only acts when the scenario reaches its module.
04What if a Rossum module is missing in Make?
It depends on what you need. The Rossum app offers exactly 2 actions, Upload Invoice and Export an Annotation, with no search, no trigger and no Make an API Call module to reach other parts of Rossum. If your need fits those two actions, build around them and let other apps handle the rest of the flow. If it does not, the app alone will not cover it, and the team can look at your case to find another route through other Make apps or a different setup.
05Should you use Make or n8n for Rossum?
It depends on the tool your team already runs. On Make, Rossum gives you two clear actions, sending an invoice in and exporting an annotation, a connection made once, and a visual editor where each run is tested with Run once. The same app often has an n8n node too, so the useful check is which module list covers your exact steps and which editor your team is comfortable maintaining. Compare the available operations side by side on both before committing, rather than choosing on habit alone.
Same platform

Other docs you might need on this stack.

Browse all integrations