Prepare local PDFs for prepress with pdfRest verified n8n node
Local files + pdfRest + self-hosted n8n
Turn incoming PDFs into PDF/X copies
Automate PDF/X preparation with little or no code. Configure pdfRest in self-hosted n8n to watch a local folder and save separate PDF/X copies without writing a custom API integration.
Requires configured service credentials and a pdfRest plan that supports the operations. Evaluation plans may add watermarks or text redactions.
What is n8n?
n8n is a low-code automation platform for connecting applications and services. Import this template, then configure its nodes to add pdfRest processing to your workflow.
From local folder to PDF/X output
Watch
React to newly added local files after writing has finished. Existing files are ignored.
Read
Filter for PDF filenames and read the file from the n8n host or mounted volume.
Convert
Convert to PDF/X-4 by default. Select the standard required by your printer.
Save
Save a separate PDF/X copy with the workflow run ID in its filename. Preserve the original PDF.
Import and connect your workflow
Import the template
Create a workflow, open the editor’s three-dot menu, and choose Import from File. Select the downloaded JSON and configure it before activating.
Search pdfRest in the nodes panel to install the verified node. Use the setup guide below if you need help.
Prepare self-hosted n8n
Local File Trigger is disabled by default in n8n 2.0+. Ask your administrator to enable it while preserving other node restrictions.
Connect your file paths
Mount incoming and output folders at /files/pdfrest/incoming and /files/pdfrest/output. n8n needs read access to incoming, write access to output, and both paths in its filesystem allow-list.
Choose your PDF service
Select your pdfRest credential. Use Cloud for hosted processing or a reachable Container/AWS deployment for private processing.
Confirm print requirements
Confirm PDF/X version and print requirements with your printer before activating.
Administrator setup: trigger, folders, and permissions
Use self-hosted n8n. In n8n 2.0 and later, Local File Trigger is disabled by default. Have an administrator enable n8n-nodes-base.localFileTrigger by removing only that node from NODES_EXCLUDE, preserving the other node restrictions. Restart n8n after changing its configuration.
See Local File Trigger requirements and node-exclusion configuration.
Map your host incoming folder to /files/pdfrest/incoming inside the n8n container, with read access. Map your host output folder to /files/pdfrest/output, with write access. Create both host folders first. These are container paths; they do not automatically refer to folders on the host.
Set N8N_RESTRICT_FILE_ACCESS_TO to /files/pdfrest/incoming;/files/pdfrest/output, incorporating any other directories the administrator intentionally permits. See filesystem access configuration and filesystem and mount guidance. The general Docker example mounts n8n’s data directory, not these workflow folders.
For different paths, change Watch local incoming folder → path and the output-directory portion of Write prepress copy → fileName. Read local PDF already receives the trigger’s path.
Test, review, then activate
Test with a sample PDF. Confirm the original stays unchanged and the PDF/X copy meets your printer’s requirements before activating.
Open the workflow test checklist
- Add a PDF after the watcher starts and confirm processing begins only after the file finishes writing. Verify one PDF/X output and an unchanged source.
- Add a non-PDF and confirm it is ignored.
- Confirm the output folder does not trigger a second conversion.
- Check the output with your printer’s preflight process, including page dimensions, bleed, fonts, colors, and images.
- Verify incoming-folder read permission and output-folder write permission, including visible failures when access is denied.
- A corrupt or inaccessible PDF must fail visibly without a successful output.
Know what to review
PDF/X and print readiness
PDF/X conversion is one prepress step, not a guarantee of print readiness.
Filesystem access
Requires access to the self-hosted filesystem. Trigger availability and filesystem restrictions depend on the installation.
New files and repeated runs
This watches new files only, with no backlog or persistent deduplication. A replay creates a new output copy.
Sources remain intact. Files travel through n8n, the selected pdfRest deployment, and any connected services shown above. Review your execution-data retention settings before production use.
Build your workflow
Download, connect your accounts, and test with a sample PDF.