Resources · Make integration

PEPPOL e-invoicing Make integrationAutomate PEPPOL e-invoicing with Make.

Can Make send and collect your PEPPOL invoices without code? The PEPPOL e-invoicing Make integration gives you 11 modules, including 2 triggers. This guide is for finance and ops people: link your account, build a first flow, then pick the right module.

Try the PEPPOL e-invoicing integration on MakeSee the 11 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the PEPPOL e-invoicing Make integration do for you?

The PEPPOL e-invoicing Make integration links your PEPPOL e-invoicing account to Make, so documents you send and receive can move through a scenario, the automation you build in Make as a chain of modules. You get 2 scheduled triggers, 8 actions and 1 search, all usable from the Free plan.

Supplier invoices that file themselves. Watch New Incoming Document starts the scenario when a new document reaches your account, then Get a Document and Get a Document Attachment pull the details and the file so the next step can store or forward them.

Outgoing invoices with a paper trail. Watch New Outgoing Document reacts to what you have sent, which is handy for logging every invoice in your accounting tracker. When the invoice comes from another tool, Send a Peppol Document pushes it onto the network, and Check a Company Registration Status lets you look up the recipient first.

Cleanup and audits. List Documents returns several documents at once, one bundle each (a bundle is one item passed from module to module), which suits a review of what went through.

Be aware of one limit: Make's own documentation for this app is marked as limited, with no official description for any module. Behaviors on this page that come from a module's name are flagged as such, and you should confirm them with a test run. The Make review covers the editor in depth, and the Make troubleshooting guide helps when a run fails. Weighing tools? The n8n vs Make comparison lays out the criteria.

Connect

How do you connect PEPPOL e-invoicing to Make?

  1. 01

    Add a module and open the connection

    Drop any PEPPOL e-invoicing module into your scenario and click Create a connection. A connection is your account linked to Make once, then reused by every module of this app.

  2. 02

    Name it and authorize Make

    Give the connection a name if you manage several accounts. Then either approve Make on the page PEPPOL e-invoicing opens, or paste the key the app gives you, depending on what the connection window asks for.

  3. 03

    Save and reuse

    Click Save. The connection now appears in the dropdown of every other PEPPOL e-invoicing module, so you only do this once per account.

First scenario

Your first scenario with PEPPOL e-invoicing

GoalWhen a new document arrives in PEPPOL e-invoicing, Make fetches its details and then its attachment.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to place the first module.

  2. 02

    Add the trigger

    Search for PEPPOL e-invoicing, pick Watch New Incoming Document, and choose the connection you made, or click Create a connection now.

  3. 03

    Fetch the full document

    Click the + to the right of the trigger and add Get a Document. Then map the document coming from the trigger, so that Make knows exactly which one it should read.

  4. 04

    Grab the attachment

    Add Get a Document Attachment after it and map the same document. From here you can add any other app to store or forward the file.

  5. 05

    Test with Run once

    Click Run once, then open each module's bubble to read the bundles it received. Nothing new in the account? The trigger simply returns no bundle.

  6. 06

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default; keep that or change it, then turn the scenario on.

Triggers

What starts a PEPPOL e-invoicing scenario

2 modules start a scenario when something happens in PEPPOL e-invoicing. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by PEPPOL e-invoicing as soon as it happens.

PEPPOL e-invoicing1Watch New Incoming Document

Watch New Incoming Document

triggerIn the docs only

Your scenario starts with each new document that reaches your PEPPOL e-invoicing account, so received invoices get handled without anyone checking the inbox. Each new document becomes one bundle for the modules that follow.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and the module shows a clock badge.
When to use it
as the starting point of any flow that reacts to supplier invoices.
Watch out
Make's documentation gives no description here, so its exact behavior is read from the name; run it once on a real account before relying on it.
PEPPOL e-invoicing2Watch New Outgoing Document

Watch New Outgoing Document

triggerIn the docs only

This one is the mirror image: it picks up documents your account sends out, which lets you keep a record of every invoice you issued, wherever it was created. One bundle per new outgoing document.

How it fires
scheduled. Make checks the app on the scenario's schedule, not the moment the document leaves, so expect the delay of your schedule.
When to use it
logging sent invoices in a spreadsheet or alerting sales once a customer is billed.
Watch out
the type comes from the module name, not from an official description; confirm with the clock badge in the editor.
Modules

Everything the PEPPOL e-invoicing app can do in Make

PEPPOL e-invoicing gives you 9 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

PEPPOL e-invoicing1

Check a Company Registration Status

ActionIn the docs only

Before an invoice leaves, this action tells you, going by its name, whether a company is registered on the network, which saves you from sending into the void.

When to use it
right before Send a Peppol Document, when onboarding a new customer.
Watch out
the documentation does not describe the answer it returns, so read the bundle after a Run once before adding a filter on it.
PEPPOL e-invoicing2

Generate a Peppol Xml

ActionIn the docs only

Turning invoice data into the XML file the network expects is what the name promises here, handy when your source tool only produces plain data.

When to use it
your invoices live in a spreadsheet or a CRM and need a network-ready format before sending.
Watch out
no field list is documented; open the module and let Make show you what it asks for.
PEPPOL e-invoicing3

Get a Document

ActionIn the docs only

Once you know which document you care about, Get a Document reads it in full, so later modules can use its details instead of just a reference.

When to use it
after a Watch trigger or List Documents, when the next step needs more than what the trigger handed over.
Watch out
it works on one document per bundle; feed it one at a time.
PEPPOL e-invoicing4

Get a Document Attachment

ActionIn the docs only

Need the actual file rather than the data? Get a Document Attachment retrieves what is attached to a document, ready to be saved in a drive or sent by email.

When to use it
archiving the file of every received invoice in your document storage.
Watch out
the Free plan caps files at 5 MB, so test a heavy attachment with Run once to check it gets through.
PEPPOL e-invoicing5

Get my Account Info

ActionIn the docs only

Your own account details come back from this action, which makes it the quickest way to prove a connection works before building anything bigger.

When to use it
just after creating the connection, or when you manage several accounts and want to confirm which one a scenario uses.
Watch out
each run still counts as an operation on your plan, so remove it once testing is done.
PEPPOL e-invoicing6

List Documents

SearchIn the docs only

Several documents at once, each as its own bundle: that is what a search module like List Documents returns, and every later module then runs once per document.

When to use it
a review of past invoices, or a catch-up after the scenario was switched off.
Watch out
a search can return zero, one or many results; more bundles means more operations counted on your plan.
PEPPOL e-invoicing7

Make an API Call

ActionIn the docs only

Anything the listed modules do not cover can still be reached: this module calls any endpoint of the PEPPOL e-invoicing API with the connection you already set up.

When to use it
the action you need has no module of its own in Make.
Watch out
you need the app's API reference to know which endpoint to call, since Make's documentation for this app is limited.
PEPPOL e-invoicing8

Send a Peppol Document

ActionIn the docs only

Your invoice goes out over the network with this action, straight from the scenario, without anyone opening the PEPPOL e-invoicing interface.

When to use it
an invoice is validated in your billing tool and should reach the customer right away.
Watch out
sending cannot be taken back; test on a document you are allowed to send, and check the recipient first with Check a Company Registration Status.
PEPPOL e-invoicing9

Send a Peppol Document (Synchronous)

ActionIn the docs only

Same sending job, with one difference in the name: the word Synchronous suggests the module waits for the sending to finish before passing on, though the documentation does not confirm it.

When to use it
the next module depends on the sending result, for example to mark the invoice as sent in your tool.
Watch out
compare both sending modules with Run once and read their bundles before choosing one.
Need help

Need help automating PEPPOL e-invoicing with Make?

A person reads every message.

FAQ

PEPPOL e-invoicing and Make: common questions

01Is the PEPPOL e-invoicing Make integration free?
Yes, it is a standard app, so it works from the Free plan. That plan has its own limits: 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, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module per bundle, each month.
02What do you need to connect PEPPOL e-invoicing to Make?
An active PEPPOL e-invoicing account and a Make account. The documentation lists no special prerequisite and no dedicated connection steps, so the usual Make flow applies: add a module, click Create a connection, optionally name it, authorize Make on the app's page or paste the key the app gives you, then click Save. The same connection serves all 11 modules. A single test run of the account info module is a simple way to check it.
03Do the PEPPOL e-invoicing triggers fire instantly?
No. Both Watch New Incoming Document and Watch New Outgoing Document are scheduled triggers: Make checks the app on the scenario's schedule instead of being called by the app. A new scenario runs every 15 minutes by default. On the Free plan you cannot go below 15 minutes; paid plans go down to 1 minute. If you need faster handling, a paid plan and a shorter interval are the only levers documented.
04What if a PEPPOL e-invoicing module is missing in Make?
Use Make an API Call. With it, any endpoint of the PEPPOL e-invoicing API can be called from your scenario, reusing the same connection as the other modules. Keep in mind that Make marks its documentation for this app as limited: none of the 11 modules has an official description. You will need the app's own API reference to pick the endpoint, and a Run once test to see exactly what comes back.
05Should you use Make or n8n for PEPPOL e-invoicing?
It depends on the tool your automations already run on. On the Make side, the facts are clear: 11 modules, 2 of them scheduled triggers, Make an API Call for the rest, and access from the Free plan. The same app often has an n8n node too, but whether this one does is worth checking on the n8n side before deciding. There is no ranking to give between the two here; the comparison page on this site walks through the criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations