Resources · Make integration

finaX Make integrationAutomate finaX with Make.

Need ZUGFeRD PDFs to appear without anyone opening finaX? The finaX Make integration gives you 3 action modules and no trigger. This guide is for teams that already use finaX: it shows how to link your API key, which module to pick and how to run a first scenario.

Try the finaX integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the finaX Make integration do?

The finaX Make integration lets a Make scenario ask finaX to produce a ZUGFeRD PDF for you. A scenario is the automation you build in Make, a chain of modules; a module is one brick of that chain. finaX brings three of them, all actions, so the data always comes from somewhere else first.

A PDF built from data you already have. Put a module from another app, or a Make schedule, at the start, then add Create a ZUGFeRD PDF (Simple). Each bundle, meaning one item passed from module to module, becomes a request to finaX, and you map its values into the finaX fields.

More control when the simple version is not enough. finaX also lists Create a ZUGFeRD PDF (Expert). The documentation gives no detail on how the two differ, so open both in the editor and compare the fields each one asks for before you choose.

Anything else the finaX API offers. Make an API Call reaches any endpoint of the finaX API with the same connection, which is how you cover what the two PDF modules leave out.

What the integration does not do: it has no trigger, so finaX never starts a scenario by itself, and the documentation lists no other limits. For the wider picture, read the Make review and check Make pricing before you plan volume. If you are weighing both tools, n8n vs Make sets out the criteria.

Connect

How do you connect finaX to Make?

  1. 01

    Copy your API key in finaX

    You need an active finaX account and an API key. Log in to finaX, go to the dashboard, open the API section and copy the key shown on screen. Keep it at hand for the next step.

  2. 02

    Add a finaX module in Make

    In your scenario, add one of the finaX modules and click Create a connection. A connection is your finaX account linked to Make once, then reused by every finaX module. The Connection name field is optional.

  3. 03

    Paste the key and save

    Paste the API key you copied from finaX, or follow the instructions Make shows on screen, then confirm. The connection now appears in the list of every finaX module you add later.

First scenario

Your first scenario with finaX

GoalWhen new data arrives from another app, Make asks finaX to build a ZUGFeRD PDF.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. finaX has no trigger, so this first slot goes to the app that holds your source data.

  2. 02

    Add the source module

    Search that other app by name, pick the module that reads your data and link its account. Each item it returns becomes a bundle that the next module can use.

  3. 03

    Add Create a ZUGFeRD PDF (Simple)

    Click the + on the right of the first module, search finaX and choose Create a ZUGFeRD PDF (Simple). Select your finaX connection and map the values of the previous module into its fields.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Read the bundles each module received and check what finaX sent back before going further.

  5. 05

    Set the schedule and switch it on

    Open the clock on the first module: a new scenario runs every 15 minutes by default, and you can change that. Then switch the scenario on so it keeps working without you.

Modules

What can finaX do in Make?

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

finaX1

Create a ZUGFeRD PDF (Expert)

ActionIn the docs only

This module gets you a ZUGFeRD PDF from finaX in its Expert variant; going by the name, it is the one to open when the Simple module does not expose what you need. Each run counts as one operation, the unit Make bills on your plan.

When to use it
after testing the Simple module, if a value from your source app has nowhere to go.
Watch out
the documentation does not describe its fields, so compare them in the editor before switching.
finaX2

Create a ZUGFeRD PDF (Simple)

ActionIn the docs only

Your data turns into a ZUGFeRD PDF produced by finaX, which makes this the natural starting point for a first scenario. Place it after the module that supplies the data and map each value into the fields it asks for.

When to use it
as soon as another app holds the information your PDF needs.
Watch out
run it once and open the output bundle before switching the scenario on.
finaX3

Make an API Call

ActionIn the docs only

With this module you can call any endpoint of the finaX API from your scenario, reusing the connection you already set up. It covers whatever the two PDF modules do not offer.

When to use it
when the finaX API does something no listed module does.
Watch out
you describe the request yourself, so keep the finaX API documentation open while you fill it in.
Need help

Need help automating finaX with Make?

A person reads every message.

FAQ

finaX and Make: common questions

01Is the finaX Make integration free?
Yes, on the Make side: finaX is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 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 drop the interval to 1 minute and remove the cap on active scenarios. Your finaX subscription is a separate matter, covered on the finaX pricing page.
02What does the finaX Make integration need to connect?
You need an active finaX account and its API key. In finaX, go to the dashboard, open the API section and copy the key shown there. In Make, add any finaX module, click Create a connection, optionally name it, then paste the key. That single connection is reused by all three finaX modules, so you only do this once per account. If Make asks for something you do not see in finaX, follow the on-screen instructions in the connection window rather than guessing a value.
03Can finaX start a Make scenario on its own?
No. finaX has no trigger module, so nothing in finaX can launch a scenario. You start the flow in one of two ways: with a trigger from another app that holds your data, or with a Make schedule on the first module, which runs every 15 minutes by default and can be changed. Either way, the finaX modules come after that first step. If you pick the schedule, remember that every module processing a bundle counts as one operation on your Make plan, so plan the schedule around how often your data really changes.
04What if a finaX module is missing in Make?
Use Make an API Call. It reaches any endpoint of the finaX API with the connection you already have, so you are not limited to the two PDF modules. Keep in mind that Make flags its finaX documentation as AI-generated and possibly wrong, so check important details against finaX and contact finaX directly if something does not match. For errors that come from Make itself rather than from finaX, the Make troubleshooting guide is the next place to look before you rebuild the module.
05Make or n8n for finaX: which one fits?
It depends on the tool your team already runs. Make gives you three finaX modules today: two that build ZUGFeRD PDFs and one API call that reaches the rest of the finaX API with the same connection. Many apps also have an n8n node, so check whether finaX does before you decide. Compare the criteria that matter to you rather than a general ranking. A short test in each tool, using Run once in Make, usually tells you more than any comparison written from the outside.
Same platform

Other docs you might need on this stack.

Browse all integrations