Scan, Sign & AI Chat
Mobile App
The mobile app pairs with your account via QR code and brings scanner, signature, chat and documents to your phone.
DownloadGuidesPDF · EN20 pages
Practical Guide n8n + PaperOffice
Every invoice different? PDF in, data out. This guide demonstrates how n8n sends an invoice to PaperOffice and retrieves the supplier, invoice number, amount, and due date as JSON.
The file is available in English and German; you download the version in the language of this page. Free, no registration.
Trusted by leading companies worldwide
OEM PARTNERSHIP
Hardware giants choose PaperOffice exclusively.
Sole official DMS partner for QNAP: Classic app, AI BYOS.
MoreISO/IEC 27001
CERTIFIED
SOC 2 Type 2
IN PREPARATION
Sole official DMS partner for ASUSTOR: Classic app, AI BYOS.
MoreWhat's inside
- Three invoices, three layouts
- Why building your own parser is costly
- The process at a glance
- What you need
- In the app: creating an API key
- In n8n: credential and workflow
- Route 1: Send invoice
- The fields as JSON
- Route 2: File in DMS
- Subscribe the webhook
- Verify every delivery
- The row for the payment list
- What teams ask at the start
- Try it yourself in 30 minutes
- Films and more on the topic
- From zero to your first workflow in five days
- Checklist and start
Who it is for
Development: You need to integrate invoices into your software without maintaining a custom parser. IT and Automation: You operate n8n and connect disparate systems. Accounting: You want to capture vendor, amount, and due date for your payment list without manual data entry.
Key facts
- 20 pages, with a test package to try it yourself in 30 minutes
- You do not need a dedicated n8n node. Everything runs via standard nodes such as HTTP Request, Webhook, and Code.
- Route 1: n8n sends the invoice and receives the supplier, number, amount, and due date in the same response. If processing takes longer, a small loop handles the polling.
- Route 2: n8n files the invoice in the DMS. Once it has been processed, PaperOffice calls your Webhook.
- Every delivery is signed with HMAC-SHA256. n8n verifies the signature and filters out duplicates.
- The API key lives in an n8n credential, never in the workflow. The API is available in every plan, including Free.
Questions and answers
Frequently asked questions about this download
Is there a PaperOffice node for n8n?
No. You will use the standard nodes HTTP Request, Webhook, Code, and Crypto. The completed workflow is included in the test package.
Which key do I need?
For the REST API, you need an API Key (poai_). For AI agents using the MCP Client from n8n, you require a User Token or OAuth; the MCP server does not accept API Keys.
Does n8n need to be publicly accessible?
Yes, for Webhook, via HTTP or HTTPS. For Route 1, n8n only requires outbound access to api.paperoffice.ai.
Need personalized advice?
Our experts are happy to help you choose the right solution.
Request consultation
