pdfRest Brings More Than 50 PDF Operations and E-Invoicing Templates to n8n
The verified pdfRest API Toolkit community node brings extensive PDF processing into n8n, including a ready-to-import workflow for ZUGFeRD/Factur-X e-invoices.
New: Meet n8n Nod, your personal AI agent for local task automation.
pdfRest has launched a verified community node for n8n that brings more than 50 PDF operations into automation workflows. The pdfRest API Toolkit, published as @pdfrest/n8n-nodes-pdfrest, also has ready-to-import templates, including a workflow for creating and validating ZUGFeRD/Factur-X e-invoices. For teams that currently move PDFs between inboxes, portals, spreadsheets, and separate document tools, the integration creates a more direct path to automate document-heavy processes inside n8n.
The official pdfRest API Toolkit integration page confirms that the node is verified by n8n and supports both pdfRest Cloud and self-hosted pdfRest deployments. It is powered by the Adobe PDF Library and uses a single credential for access to its available operations. That matters because n8n users can build PDF steps directly on the workflow canvas instead of configuring bespoke HTTP requests for each document task.
What the pdfRest node adds to n8n
The official figure is more than 50 operations, which supersedes the earlier 40-plus figure associated with the initial announcement. The node is designed as a broad PDF toolkit rather than a connector limited to one task, such as conversion or text extraction.
Supported operation categories include:
- Converting and compressing PDFs
- OCR and extraction of text or images
- Reading and handling PDF metadata and forms
- Redaction, passwords, permissions, and watermarks
- Digital signing
- PDF/A and PDF/X archival-format workflows
This range lets a workflow treat a PDF as an active business document rather than a static attachment. For example, an incoming file can be processed, its content extracted, sensitive material redacted, and an output document sent to another system as part of one automation. The specific design still depends on the organization’s source documents, validation needs, and connected applications, but the node makes those PDF functions available within n8n itself.
| Deployment option | Where PDF processing is accessed | What the integration confirms |
|---|---|---|
| pdfRest Cloud | pdfRest Cloud in US or EU regions | The n8n node can be configured for cloud use. |
| Self-hosted pdfRest | A self-managed pdfRest Container or AWS deployment | The same node supports private deployment scenarios. |
The verified research does not provide pdfRest pricing details. Businesses evaluating the integration should therefore confirm the applicable pdfRest plan and deployment costs directly with the provider, particularly when deciding between cloud and self-hosted use.
ZUGFeRD and Factur-X invoicing workflow
The most concrete business example is the published ZUGFeRD/Factur-X workflow template. ZUGFeRD and Factur-X are hybrid invoice formats that pair a human-readable PDF with structured invoice data in CII XML. The template shows how document automation can support a complete e-invoicing process instead of simply generating a PDF.
According to the n8n workflow-gallery description, the template can receive CII XML and PDFs through an n8n Form. It can then create a hybrid PDF from the XML, pair XML with an existing PDF, or validate a completed hybrid PDF. The workflow also builds an audit bundle containing the PDF, source XML, and a JSON-plus-README report for download and archiving.
That structure is useful because invoice processing often requires both a readable document and retained structured data. A workflow that keeps the source XML alongside the resulting PDF and validation output can make downstream handling and recordkeeping more consistent. It also offers a practical starting point for teams that want to test a ZUGFeRD/Factur-X process without designing every workflow branch from scratch.
What implementation requires
The integration is available as the @pdfrest/n8n-nodes-pdfrest verified community-node package. Users need to install the node in n8n and configure a pdfRest credential. From there, they can connect it to existing n8n triggers, forms, storage steps, and other workflow components.
The template should be treated as an implementation foundation, not a substitute for checking an organization’s own invoice inputs and archival process. Before putting an automated invoice workflow into regular use, teams should test the documents they receive or produce, decide where audit bundles should be stored, and confirm which path applies: creating a hybrid invoice, pairing XML with an existing PDF, or validating a completed file.
For other PDF workflows, the same principle applies. Start with a narrowly defined process, such as extracting text from inbound documents or applying a watermark to generated files, then connect it to the systems already used by the team. This helps identify where manual handoffs can be removed without turning a document process into an unnecessarily complex automation project.
If your team spends time moving, converting, validating, or filing PDFs by hand, a well-built n8n workflow can turn those repetitive steps into a reliable process. Scalevise can help map the document journey, connect the required apps and APIs, and implement production-ready handling around the pdfRest node. Explore an n8n workflow automation setup for document processes to reduce manual PDF work and create a workflow your team can operate with confidence. Discuss your n8n automation project with Scalevise.
Availability and practical significance
The pdfRest node is now available in the n8n ecosystem as a verified community node, with cloud and self-hosted deployment options confirmed by the integration documentation. Its value is not only the number of PDF functions. It is the ability to place those functions alongside workflow triggers, business logic, forms, and destination systems in n8n.
For businesses using n8n, that can reduce the need to build individual PDF API calls for routine tasks. The ZUGFeRD/Factur-X template is particularly significant because it illustrates a complete use case with intake, document creation or validation, reporting, and archiving. It gives users a tangible example of how PDF automation can support an operational workflow rather than remain an isolated technical capability.
Frequently Asked Questions
What is the pdfRest API Toolkit for n8n?
The pdfRest API Toolkit is a verified n8n community node, published as @pdfrest/n8n-nodes-pdfrest, that provides more than 50 PDF processing operations in n8n workflows.
What PDF tasks can the pdfRest n8n node perform?
The documented categories include conversion, compression, OCR, text and image extraction, metadata and forms handling, redaction, security settings, watermarks, digital signing, and PDF/A and PDF/X workflows.
Does pdfRest provide a ZUGFeRD or Factur-X template for n8n?
Yes. The published workflow template can receive CII XML and PDFs, create or validate hybrid ZUGFeRD/Factur-X PDFs, and produce an audit bundle with the PDF, source XML, and a JSON-plus-README report.
Can the pdfRest n8n node be used with self-hosted infrastructure?
Yes. The integration documentation states that the node supports pdfRest Cloud in US or EU regions and self-hosted scenarios using a self-managed pdfRest Container or AWS deployment.
What does pdfRest cost for n8n users?
The verified material confirms the integration and its deployment options but does not provide pricing. Users should consult pdfRest directly for the relevant plan and deployment costs.
Conclusion
pdfRest's verified n8n node adds a substantial set of PDF capabilities to the automation platform, while its ZUGFeRD/Factur-X template demonstrates a practical e-invoicing workflow. The combination gives n8n users a direct way to build PDF processing into wider business automations, with cloud and self-hosted deployment paths available.