Automate EU e-invoicing with the SealDoc Make connector

Most businesses already live inside Make. Their orders come from Shopify, their files land in Google Drive, their confirmations go out via Gmail. What they do not yet have is a way to slot EU-compliant e-invoicing into that same visual workflow, without writing a single line of HTTP configuration. That is exactly what the SealDoc Make connector 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 automatically on a schedule or whenever a trigger fires. No hosting, no deployment, no code. It is used by finance teams, operations leads, and developers alike because the learning curve is shallow and the coverage is broad: from Google Workspace and Microsoft 365 to Slack, Airtable, Stripe, and everything in between.

What the SealDoc connector adds

Searching for “SealDoc” in Make’s app browser gives you one module set that covers the full SealDoc API surface. Six actions and one webhook trigger, ready to drag onto a canvas:

• Create Job: submit a document for processing, choose the compliance profile, and receive a job ID back instantly.
• Generate Document: render a PDF from a template and data payload, with optional PDF/A-3 conversion and RFC 3161 timestamping.
• Generate Invoice: produce a structured e-invoice with a profile picker for Factur-X, XRechnung, and Peppol BIS 3 formats.
• Get Job: retrieve the current status and download URL for any previously submitted job.
• Validate Invoice: run a compliance check against EN 16931 and Peppol business rules without generating a new document.
• Peppol-Ready Check: verify that a buyer identifier is registered on the Peppol network before you attempt delivery.
• Job Status Changed (trigger): receive a webhook event the moment a job moves to completed or failed, so your scenario continues without polling.

Together these cover every step of a compliant invoicing flow: generate, validate, deliver, confirm.

A practical three-module scenario

Here is a real-world example of what this looks like in Make. Suppose your accounts team receives supplier invoices as PDFs in a shared Google Drive folder. You want each one converted to a Peppol-compliant invoice and archived in Dropbox.

Module 1: Google Drive, Watch Files. Configure it to watch a specific folder. Every new file triggers the scenario. No manual intervention.

Module 2: SealDoc, Generate Invoice. Map the file from Module 1 as the source document. Set the profile to Peppol BIS 3. Add your company VAT number and the buyer’s Peppol ID in the data fields. The module returns a jobId immediately, then uses the Job Status Changed webhook to continue when the invoice is ready. You get back a downloadUrl pointing at the structured, validated Peppol XML.

Module 3: Dropbox, Upload a File. Map the download URL from Module 2 as the file source and choose the destination folder. The compliant invoice is now archived, timestamped, and retrievable.

Three modules. No API credentials to hand-craft, no JSON to build by hand, no retry logic to wire up yourself. The entire scenario fits on one screen in Make’s canvas.

Why no-code compliance matters for EU mandates

EU member states are rolling out B2B e-invoicing mandates at different speeds. France requires structured invoices for B2B transactions from September 2026. Germany has phased obligations under the Wachstumschancengesetz for XRechnung and Factur-X. Belgium and the Netherlands are following the Peppol network as their routing layer. Poland’s KSeF system is live for large taxpayers and expanding.

Each mandate has its own format requirement, validation ruleset, and delivery method. Keeping up with that as a developer is a moving target. Keeping up with it in a no-code tool like Make, backed by a compliance engine that tracks the rules for you, is a fundamentally different problem. When the profile changes, you change one dropdown. The underlying validation logic stays current on our side.

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

How to connect SealDoc in Make

1. Open Make and go to Connections in the left sidebar.
2. Search for SealDoc and click Add.
3. Paste your SealDoc API key (generate one under Settings, API Keys in your SealDoc dashboard).
4. Click Save. The connection appears as verified.

From that point, every SealDoc module in every scenario uses that connection automatically. You can also add the modules first: in any scenario, click the plus icon, search “SealDoc”, and the full module list appears.

Get started

The connector is live in Make’s app browser today. If you do not have a SealDoc account yet, the free trial gives you access to all connector modules so you can build and test a full scenario before committing to a plan.

For teams already generating documents with the SealDoc API, the Make connector replaces your HTTP modules with something that self-documents, self-validates, and does not break when a field name changes. The integration page at sealdoc.eu/integrations lists all supported platforms with setup guides for each.

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