Start with a managed workflow environment
Install the pdfRest node in n8n Cloud, connect your processing endpoint, and send a PDF through a complete workflow without setting up an n8n server.
Explore what n8n and pdfRest can do together
Why use n8n Cloud with pdfRest?
n8n Cloud handles the workflow hosting, letting your team focus on the automation. Pair it with pdfRest Cloud for hosted PDF processing and connect the result to the cloud services you already use.
This is a good fit for teams building around email, shared storage, and online business systems. Choose self-hosted n8n when private network access or control over the workflow host is central to the design. Compare n8n plans for current features and execution limits.
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 instance owner or admin installs the node; other members can use it afterward. If it is missing from search, ask the instance owner to check verified community-node availability in the Cloud Admin Panel. See n8n’s verified-node installation instructions.
Connect your pdfRest deployment
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.
Using a private pdfRest endpoint? n8n Cloud must be able to reach it through an appropriate public endpoint. A local or private address does not become reachable just by entering it in the credential. If processing must remain inside your network, use self-hosted n8n with your private pdfRest deployment.
Test a complete PDF workflow
Use a small sample PDF in Google Drive to verify the connection and file handling before adding more operations. Connect your Google Drive account in n8n and create separate input and output folders.
- Start with a Manual Trigger and a Google Drive node configured to download your sample file. A file ID or metadata alone is not the PDF; confirm the download produces binary file data.
- Add pdfRest API Toolkit, select your credential, and choose Compress PDF.
- Choose Input File. Set Input File Data Field Name to the binary field from the download node, typically
data. Select the compression settings for your test. - Enable Download Output Files and set Output File Data Field Name to
data. Without the download option, processing returns its JSON response by default. - Connect a Google Drive upload node. Use the output binary field
data, give the result a distinct filename, and select the output folder. - Execute the workflow and open the saved PDF. Check the content and file size; compression results depend on the source document.
Once the test works, replace the manual start with a Google Drive trigger for new files in your input folder, map its file ID into the download node, and test again. Keep the output folder outside the watched input folder to avoid processing the same result repeatedly. Publish or activate the workflow using the controls in your n8n version.
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.