Automate the invoicing process without writing code
A workflow instead of an application: inbox, spreadsheet or form in, e-invoice out.
Not every invoicing process needs an application of its own. An inbox, a spreadsheet and a form often suffice; what is missing is the place that turns them into a compliant format. That place is one HTTP call. For n8n there are ready-made workflows — import one, enter the credentials, activate it. Make and Zapier reach the same interface through their HTTP module; the integration pages show the configuration.
What comes in
A trigger: a new email, a new row in a sheet, a submitted form
Invoice data from the source — line items, amounts, recipient
Your API key, stored as a credential in the workflow
A destination: outbox, storage or spreadsheet
What this solves
Ready-made workflows instead of a blank canvas
Seven n8n templates cover the usual routes: generate from a spreadsheet, check through a form, read the inbox, shop orders, PDF invoices per department, extra fields on the PDF, file incoming invoices. Each template is a JSON file to import.
The call is an HTTP module
No SDK, no library: one URL, one header with the key, one JSON body. What works in n8n works the same way in Make or Zapier through their HTTP module.
Validation belongs in the run
One step before dispatch checks the data and stops the run with a rule code and a field. The form template turns this into a small page where a colleague can have a file checked without touching the API themselves.
The key stays in the workflow
Credentials live in the automation, not in a spreadsheet and not with the recipient. If you run n8n yourself, the key never leaves your environment.
One real example
The body the HTTP module sends — from the recipe “Validate an existing invoice”.
{ "invoice": { "invoiceNumber": "RE-2025-003", "countrySpecific": { "countryCode": "DE", "leitwegId": "991-12345-67" }, "subtotal": 1500, "total": 1785 }}POST /api/v1/invoice/DE/validate
Response: valid plus errors and warnings with rule code and field. That is exactly where the workflow branches: continue when clean, otherwise stop and report.
The full recipeThe endpoints involved
- Invoice CreatorLive
POST /api/v1/invoice/{countryCode}/{format}/generate
- ValidatorLive
POST /api/v1/invoice/{countryCode}/validate
Compared to the alternative
The alternative is invoicing software that brings everything along — and in which your process has to look the way it prescribes. A workflow stays yours.
Read the comparisonHow it runs
- 1
Import a template or create a workflow and pick the trigger: inbox, spreadsheet or form.
- 2
Point the HTTP module at the right endpoint and store the key as a credential.
- 3
Pass the result on: attach the file, write the row, send the message.
What it costs at this volume
Around 300 invoices per month fit the Starter plan at 23 € per month.
All prices net, plus VAT · 20 % off when billed annually · Free tier without a credit card
All plansLimits
- Dedicated blocks exist for n8n so far; in Make and Zapier the call goes through their HTTP module — each integration page states the current status.
- A workflow is only as reliable as its operation: retries, timeouts and error paths have to be set up.
- Peppol dispatch is not available yet (planned 2027).
Frequently asked questions
Do I need n8n, or do Make and Zapier work too?
Both work. n8n has ready-made templates and a dedicated block; Make and Zapier call the same endpoints through their HTTP module. The integration pages show the configuration for each.
Where does the API key live?
In the automation's credential store, not in the workflow body and not in a spreadsheet. If you run n8n yourself, it stays in your environment.
What does a workflow cost?
The templates themselves are free. What is counted are the generated invoices as API calls; the price example above works through a typical volume.