← Back to all articles

Automate EU e-invoicing with the SealDoc Make connector

SealDoc Team · · 5 min read

Many businesses already live inside Make. Their orders come from a webshop, their files land in Google Drive, their confirmations go out via Gmail. What they do not have yet is a way to slot compliant e-invoicing into that same visual workflow without hand-building HTTP requests. That is what the SealDoc app for Make does.

What Make is

Make (formerly Integromat) is a visual automation platform that connects more than 1,500 apps through a drag-and-drop scenario builder. You draw the flow, set the data mappings, and Make runs it on a schedule or whenever a trigger fires. No hosting, no deployment, no code. Finance teams, operations leads and developers all use it, because the learning curve is shallow and the coverage is broad.

What the SealDoc app adds

Six actions and one trigger, ready to drag onto a canvas:

  • Generate Invoice: turns structured invoice data (seller, buyer, lines) into a Factur-X e-invoice: a PDF/A-3 with the XML embedded, validated against EN 16931 and timestamped.
  • Create Job: uploads a file (PDF, Word, Excel, PowerPoint or an image) for conversion to PDF/A-3, with options for an RFC 3161 timestamp, an evidence pack, PDF/UA accessibility and OCR.
  • Generate Document: renders Markdown or HTML directly to a sealed PDF/A-3.
  • Get Job: returns the status and the details of any job.
  • Validate Invoice: checks an existing Factur-X or ZUGFeRD file against EN 16931 and returns a verdict with every finding.
  • Peppol-Ready Check: looks up a VAT number in the Peppol Directory.
  • Job Status Changed (trigger): starts a scenario the moment an uploaded job completes or fails. It runs on SealDoc webhooks, which are part of the Growth plan and up.

A practical scenario in four modules

Suppose your invoices start as rows in a Google Sheet: one row per invoice, with the number, the date, the customer and the line. You want each new row to become a compliant e-invoice in your Dropbox archive.

Module 1: Google Sheets, Watch New Rows. Point it at the sheet. Every new row starts the scenario.

Module 2: SealDoc, Generate Invoice. Map the fields from the row:

  • Invoice number and Invoice date from the row. Currency: EUR.
  • VAT rate (decimal): 0.21 for 21%. Leave VAT category and VAT label empty for a standard rate; SealDoc derives the category and writes the caption.
  • Seller: your own company, with company name, VAT number, address, postal code, city and country (two-letter code). The VAT number has to match the VAT number of your SealDoc workspace.
  • Buyer: choose the buyer details option and map the customer fields, or use a customer you saved in SealDoc.
  • Line items: description, quantity, unit and unit price (excl. VAT).
  • Profile: Basic, which produces Factur-X.

The module answers with a jobId, a status and a statusUrl. Invoice generation happens within the call, so status is completed when the module finishes, and there is nothing to wait for.

Module 3: HTTP, Make a request. Method GET, URL https://api.sealdoc.eu/api/download/{{2.jobId}}, and one header: X-Api-Key with your API key as value. The response is the sealed PDF/A-3 with factur-x.xml embedded. Need the XML on its own as well? Add a second request on https://api.sealdoc.eu/api/invoices/{{2.jobId}}/xml.

Module 4: Dropbox, Upload a File. Map the data from Module 3, give the file a name such as the invoice number plus .pdf, and choose the destination folder. The invoice is now archived, validated and timestamped.

Four modules, no JSON to build by hand, no retry logic to wire up yourself. The whole scenario fits on one screen.

Why no-code compliance matters for EU mandates

EU member states are rolling out B2B e-invoicing at different speeds:

  • France: from 1 September 2026, every business established in France must be able to receive e-invoices, and large and mid-sized companies must issue them. Small and micro businesses follow in September 2027.
  • Germany: businesses have had to be able to receive e-invoices since 1 January 2025. Issuing them becomes mandatory in 2027 and 2028.
  • Belgium: since 1 January 2026, businesses established in Belgium exchange B2B invoices electronically, with Peppol as the standard route.
  • Poland: KSeF has been mandatory since 1 February 2026 for the largest taxpayers and since 1 April 2026 for the others.

Each mandate has its own format, ruleset and delivery route. Keeping up with that as a developer is a moving target. In Make, backed by SealDoc, it is a different problem: SealDoc validates every invoice against EN 16931 before sealing it, and when the rules change, the validation changes with them on our side.

That is the core value: regulatory churn lives in SealDoc’s engine, not in your scenario.

How to connect SealDoc in Make

The SealDoc app for Make is in early access. Ask for access via our contact page. Once the app is in your Make organisation:

  1. Add any SealDoc module to a scenario.
  2. Open its Connection field and click Add.
  3. Paste your SealDoc API key into API key. You create the key in the SealDoc app under Integration → API Keys; it is shown only once.
  4. Click Save.

Every SealDoc module in your scenarios can use that connection from then on. Validate Invoice and Peppol-Ready Check need no connection at all.

Get started

Generate Invoice needs a SealDoc workspace with API access: the free Developer plan or any paid plan. Create Job with timestamps and evidence packs starts at Starter, and the Job Status Changed trigger at Growth. All plans are on our pricing page.

Already calling the SealDoc API from HTTP modules? The SealDoc app replaces them with modules that know every field, so your mappings stay readable. All the ways to connect SealDoc are on our integrations page.

Compliance automation does not have to mean a six-week engineering project. Four modules in Make are enough to start.

← Back to all articles