Manipulate PDF with Adobe developer API
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 14 nodes and runs when another workflow calls it (plus 1 other trigger). Along the way it connects Dropbox. It also calls pdf-services.adobe.io over HTTP.
How it runs
Trigger: When another workflow calls it (plus 1 other trigger).
- Authenticartion (get token) (HTTP Request): calls pdf-services.adobe.io (POST)
- Query + File + Asset information (Merge): merges the data from its input branches
- Load a test pdf file (Dropbox): download
- Adobe API Query (Edit Fields (Set)): sets 2 fields: endpoint, json_payload
- Create Asset (HTTP Request): calls pdf-services.adobe.io (POST)
- Upload PDF File (asset) (HTTP Request): calls an HTTP API (PUT)
- Query + File (Merge): merges the data from its input branches
- Process Query (HTTP Request): calls an HTTP API (POST)
- Wait: waits 5 seconds
- Try to download the result (HTTP Request): calls an HTTP API
…plus 2 more steps. See the full node list below.
Services it uses
HTTP calls to: pdf-services.adobe.io
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- Manual Trigger
n8n-nodes-base.manualTrigger - HTTP Request
n8n-nodes-base.httpRequest - Execute Workflow Trigger
n8n-nodes-base.executeWorkflowTrigger - Edit Fields (Set)
n8n-nodes-base.set - Dropbox
n8n-nodes-base.dropbox - Merge
n8n-nodes-base.merge - Wait
n8n-nodes-base.wait - Switch
n8n-nodes-base.switch
From the author
Adobe developer API Did you know that Adobe provides an API to perform all sort of manipulation on PDF files : - Split PDF, Combine PDF - OCR - Insert page, delete page, replace page, reorder page - Content extraction (text content, tables, pictures) - ...…