Resources · Make integration

PeppoBox PEPPOL connector Make integrationAutomate PeppoBox PEPPOL connector with Make.

Can Make pick up your PEPPOL documents and pass them to the rest of your stack? The PeppoBox PEPPOL connector Make integration gives you 11 modules: 2 triggers, 8 actions and 1 search. This guide links your account and walks you through a first working scenario.

Try the PeppoBox PEPPOL connector integration on MakeSee the 11 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the PeppoBox PEPPOL connector Make integration do?

The PeppoBox PEPPOL connector Make integration links your PeppoBox account to Make, a no-code tool where you build a scenario, meaning an automation made of modules chained together. Each module is one brick: a trigger that starts the run, an action, or a search. Here you get 11 of them, covering incoming and outgoing documents.

Route supplier documents as they land. Watch New Incoming Document starts the scenario when PeppoBox holds a document you have not processed yet. Chain Get a Document Attachment and send the file to wherever your accounting team works.

Send without leaving your other tools. A sales app or a spreadsheet row can feed Send a Peppol Document, and Watch New Outgoing Document can then log each sent item. Before a first send to a new customer, Check a Company Registration Status helps you confirm the company can receive.

Keep a clean audit trail. List Documents returns several documents at once, handy to rebuild a register after the fact.

One honest limit: Make's own documentation for this app is thin. It lists the module names but no fields, no connection steps and no troubleshooting notes, so plan to test each module with Run once before relying on it. If you are weighing tools, the n8n vs Make comparison lays out the differences, and the Make pricing page explains what an operation costs you.

Connect

How do you connect PeppoBox PEPPOL connector to Make?

  1. 01

    Add a PeppoBox module

    Open a scenario, click the +, search for PeppoBox PEPPOL connector and pick any of its modules. Then click Create a connection. A connection is your PeppoBox account linked to Make once, and every module of the app reuses it.

  2. 02

    Name the connection

    This step is optional, but a clear name pays off when you run a test account next to your live one. Something like the company name plus the word live keeps the two apart in every dropdown.

  3. 03

    Authorize and save

    Depending on what PeppoBox asks for, either approve Make on the PeppoBox page that opens or paste the key PeppoBox gives you. Click Save, and the module is ready to fill.

First scenario

Build your first scenario with PeppoBox PEPPOL connector

GoalWhen a new document arrives in PeppoBox, Make fetches its attachment so the next module can file it.

  1. 01

    Create the scenario

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

  2. 02

    Set the trigger

    Search PeppoBox PEPPOL connector, pick Watch New Incoming Document and select your connection, or click Create a connection if this is your first module.

  3. 03

    Add the attachment step

    Click the + on the right of the trigger, add Get a Document Attachment and map the document coming from the trigger into its fields.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles, the items each module received. Check that a real document and its file came through.

  5. 05

    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 switch the scenario on.

Triggers

What can start a PeppoBox scenario?

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

PeppoBox PEPPOL connector1Watch New Incoming Document

Watch New Incoming Document

triggerIn the docs only

This trigger hands your scenario each document that has reached your PeppoBox inbox since the last check, one bundle per document, so every received invoice can move on without anyone copying it by hand.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, or 15 minutes at the shortest on the Free plan.
When to use it
your accounts payable team wants supplier documents to show up in its own tools rather than in PeppoBox.
Watch out
the documentation gives no field list, so run it once on a real inbox to see what each bundle carries.
PeppoBox PEPPOL connector2Watch New Outgoing Document

Watch New Outgoing Document

triggerIn the docs only

Pick this one to react to what leaves your account: each new outgoing document becomes a bundle, which lets you record, notify or archive every send in the same place.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a send made just after a check waits for the next one.
When to use it
finance wants a row in a sheet or a message in a team channel each time a customer invoice goes out.
Watch out
if a scenario of yours also sends documents with Send a Peppol Document, this trigger will see those sends too, so avoid feeding them back into the same flow.
Modules

What can PeppoBox PEPPOL connector do in Make?

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

PeppoBox PEPPOL connector1

Check a Company Registration Status

ActionIn the docs only

Going by its name, this module tells you whether a company is registered, which helps before you address a document to a customer for the first time.

When to use it
a new customer record appears in your CRM and you want to know early whether it can take PEPPOL documents.
Watch out
Make publishes no detail on the answer it returns, so read the output of a Run once before adding a filter on it.
PeppoBox PEPPOL connector2

Generate a Peppol Xml

ActionIn the docs only

As its name suggests, it turns data from your scenario into a PEPPOL XML file you can keep, inspect or pass to another module, without writing the file yourself.

When to use it
you want the file in hand before anything is sent, for example to store a copy next to the order it came from.
Watch out
the documentation does not list the inputs it expects, so start from one known invoice and compare the result with what PeppoBox shows.
PeppoBox PEPPOL connector3

Get a Document

ActionIn the docs only

Give it one document and it brings back that document's details, so later modules can use them. Think of it as the follow-up to a trigger or a list.

When to use it
a trigger gave you a document and you need more of its data before deciding where it goes.
Watch out
it works on one document per bundle; for a batch, run it after List Documents and Make repeats it for each item, one operation each.
PeppoBox PEPPOL connector4

Get a Document Attachment

ActionIn the docs only

Going by its name, this is how the file attached to a document reaches your scenario, ready to be saved to a drive or attached to an email.

When to use it
your team files every received invoice in a shared folder and wants the file, not only its data.
Watch out
on the Free plan Make handles files up to 5 MB, so a heavy attachment may need a paid plan.
PeppoBox PEPPOL connector5

Get my Account Info

ActionIn the docs only

A quick way to read back the details of the PeppoBox account the connection uses, which confirms at a glance that Make is talking to the right one.

When to use it
you manage several PeppoBox accounts and want a scenario to state which one it ran on.
Watch out
it counts as an operation like any other module, so keep it out of loops that run for every document.
PeppoBox PEPPOL connector6

List Documents

SearchIn the docs only

This search returns several documents in one go, as separate bundles, so you can work through a whole set instead of waiting for new arrivals.

When to use it
you are setting up the integration and want to bring older documents into your new register once.
Watch out
a search can return zero, one or many bundles, and each one then costs an operation in every module after it.
PeppoBox PEPPOL connector7

Make an API Call

ActionIn the docs only

When none of the ready modules does what you need, this one lets you call any endpoint of the PeppoBox API while reusing the connection you already set up.

When to use it
you found a PeppoBox feature in its API documentation that has no module in Make.
Watch out
you write the request yourself, so keep the PeppoBox API reference open while you fill it in.
PeppoBox PEPPOL connector8

Send a Peppol Document

ActionIn the docs only

This action sends a document through PeppoBox from your scenario, so an invoice built in another tool can go out without anyone opening PeppoBox.

When to use it
an order is marked as delivered in your shop and the customer should receive the invoice next.
Watch out
a send is not something you take back, so test with Run once on a test recipient before switching the scenario on.
PeppoBox PEPPOL connector9

Send a Peppol Document (Synchronous)

ActionIn the docs only

A second way to send, whose name says the call is synchronous. Make's documentation does not describe how it differs from Send a Peppol Document, so compare both on a test.

When to use it
the next module needs to work with what the send returns, and you checked in a Run once that this version gives you that.
Watch out
keep only one of the two send modules in a scenario to avoid sending twice.
Need help

Need help automating PeppoBox PEPPOL connector with Make?

A person reads every message.

FAQ

PeppoBox PEPPOL connector and Make: common questions

01Is the PeppoBox PEPPOL connector Make integration free?
Yes, PeppoBox PEPPOL connector is a standard app in Make, so you can use it on the Free plan. That plan comes with limits: 2 active scenarios, a scheduled check every 15 minutes at the shortest, 5 minutes 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 remove the cap on active scenarios. Usage is counted in operations, one per module per bundle. Your PeppoBox subscription is a separate matter, handled on the PeppoBox side.
02What is required to connect PeppoBox PEPPOL connector to Make?
A PeppoBox account and a Make account. Make's documentation lists no specific prerequisite for this app. You add any PeppoBox module, click Create a connection, give it a name if you like, then either approve Make on the PeppoBox page or paste the key PeppoBox provides, and save. Since the documentation does not state which of the two methods applies, keep your PeppoBox account open in another tab while you connect. The connection is then reused by all 11 modules.
03Does the PeppoBox trigger react in real time?
No. Both PeppoBox triggers, Watch New Incoming Document and Watch New Outgoing Document, are scheduled: Make checks PeppoBox on the scenario's schedule rather than being called by the app. A new scenario checks every 15 minutes by default. On the Free plan 15 minutes is also the shortest interval, while paid plans can go down to 1 minute. So a document that arrives just after a check is picked up at the next one, not the moment it lands.
04What if a PeppoBox module is missing in Make?
Use Make an API Call. It calls any endpoint of the PeppoBox API with the same connection, which covers what the 10 other modules do not. Bear in mind that Make's documentation for this app is limited: it names the modules but gives no fields or troubleshooting notes. So the PeppoBox API reference is your best guide, and a Run once on each module shows you what it returns before you build on it.
05Is Make or n8n better for PeppoBox PEPPOL connector?
It depends on the tool your team already uses. On the Make side, this page covers what is confirmed: 11 modules, two scheduled triggers, and Make an API Call for the rest. The same app often has an n8n node as well, so check the n8n catalog before choosing. Compare the modules each tool offers for your exact case, then pick the one where you already build your other automations. The n8n vs Make comparison linked above goes through the criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations