Start with a managed workflow environment
Configure pdfRest automation in n8n Cloud with little or no code. Connect PDF processing to your applications without writing a custom API integration, while n8n hosts the workflows for you.
Why use n8n Cloud with pdfRest?
Choose n8n Cloud for a managed workflow host. Pair it with pdfRest Cloud for hosted PDF processing, or connect a reachable Container/AWS deployment.
Need private network access? Use self-hosted n8n. Compare n8n plans.
Before you start
- An n8n Cloud workspace, with an owner or admin available to install the node.
- A pdfRest Cloud API key, or a self-hosted pdfRest endpoint reachable from n8n Cloud.
- A sample PDF and access to the storage service you will use for the test.
Operation availability and usage depend on your pdfRest deployment and plan. Cloud Starter and Container Trial apply watermarks or, for some output types, text redactions. Compare pdfRest plans.
Install the pdfRest node
- Open a workflow in your n8n Cloud workspace and select + to open the nodes panel.
- Search for pdfRest and select pdfRest API Toolkit in the community results.
- Select Install, then add the installed node to the workflow.
An owner or admin installs the node. If it is missing, check verified-node availability in the Cloud Admin Panel. View installation help.
Connect your pdfRest deployment
Create a pdfRest API credential and choose where processing happens.
pdfRest Cloud
Create an account, get your API key from the dashboard, and select the US or EU endpoint. Save the key in your n8n credential.
Container or AWS
Select Self-Hosted or Container Deployment and enter a reachable Deployment URL. Configure licensing in pdfRest; this option does not require a Cloud API key.
Endpoint values and deployment instructions
Use pdfRest Cloud
Create a pdfRest account and get your API key from the account dashboard. In the pdfRest API Toolkit node, create a pdfRest API credential. Select the US (https://api.pdfrest.com) or EU (https://eu-api.pdfrest.com) API Base URL, enter your API key, and save the credential.
Use a self-hosted pdfRest deployment
Deploy pdfRest through Container or AWS. In the credential, select Self-Hosted or Container Deployment and enter its Deployment URL. This credential does not require an API key for self-hosted pdfRest; configure product licensing in the pdfRest deployment.
Keep Cloud API keys in n8n credentials rather than workflow exports or ordinary node fields. The selected endpoint receives the documents and parameters supplied to the node.
Private endpoint? n8n Cloud must reach it through an appropriate public endpoint. To keep processing inside your network, use self-hosted n8n.
Test a complete PDF workflow
Connect Google Drive using Sign in with Google in the credential setup. Create separate input and output folders and add a sample PDF. Google sign-in help.
- Add a Manual Trigger and download a sample PDF with Google Drive. Confirm it produces binary file data.
- Add pdfRest API Toolkit, select your credential, and choose Compress PDF.
- Choose Input File and match its data field to the download, typically
data. Choose your compression settings. - Enable Download Output Files and set its output data field to
data. - Upload
datato your separate output folder with a distinct filename. - Run the workflow and open the saved PDF. Check its content and file size.
Once this works, add a Google Drive trigger and map its file ID into the download node. Keep output outside the watched folder, test again, then activate.
Troubleshoot the connection
The node is missing
Confirm that an owner or admin has installed pdfRest API Toolkit and that verified community nodes are enabled for the workspace. Refresh the node search after installation.
Authentication or connection fails
For pdfRest Cloud, verify the selected endpoint, API key, plan, and usage allowance. For self-hosted pdfRest, check the Deployment URL, network access, and product licensing. Review the failed execution for the specific API response.
The next step has no PDF file
Confirm the input step downloaded the PDF as binary data and that the field name matches Input File Data Field Name. Turn on Download Output Files for the processing step, then match its output field in the upload step. Operations producing multiple files use suffixes such as data_1; check the actual output before mapping them.
Choose your next workflow
Start with a template, connect your accounts, and test with a sample document.
Prepare local PDFs for prepress
Watch a local folder and save separate PDF/X copies. Requires self-hosted n8n.
OCR and route email PDF attachments
Add OCR when needed and file PDFs in invoice, contract, or review folders in Google Drive.
Create and review ZUGFeRD / Factur-X invoices
Create or validate a hybrid invoice, collect human approval, and download its review record.