Turn long PDF tasks into a simple flow that sends a file to Adobe PDF Services, runs an action like extract or split, and returns a ready to download result. Great for teams that need fast document processing without manual steps. Useful for operations, marketing content teams, and data entry teams that work with many PDFs.

The flow can start from a manual test or be called by another workflow. It requests an access token from Adobe, creates an asset, uploads the PDF, and builds a request based on the chosen endpoint and JSON payload. It then waits for a short time, checks the job status, and keeps polling until the file is ready. A Switch node routes success or in progress states. A Dropbox node is included to load a test file, but you can pass a binary PDF from any source.

Setup needs two Adobe credentials and one Dropbox connection. You choose the endpoint and payload in the set node so you can reuse the same flow for extract tables, split pages, and more. Expect faster turnaround and fewer copy and paste errors. Common uses include splitting large brochures, extracting tables for reports, and preparing data for downstream apps. The result is a download URL or file content that you can pass back to the calling workflow.

• Manual test trigger and a callable trigger so other workflows can run it on demand
• Secure token request to Adobe to obtain an access token before any file action
• Asset creation and PDF upload to Adobe to prepare the document for processing
• Dynamic endpoint and JSON payload set in a node so you can switch use cases without edits
• Wait and retry loop that checks job status every few seconds until ready
• Status Switch that routes success versus not ready and passes a clear response
• Dropbox node included to load a test PDF for development and demos

• Reduce manual PDF handling from two hours to five minutes per file
• Streamline document processing by about 80 percent through automation
• Improve data accuracy by cutting copy and paste errors by 90 percent
• Handle up to ten times more documents each day with the same team
• Connect cloud storage and Adobe API in one repeatable flow

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You will need accounts with Adobe PDF Services and Dropbox. See the Tools Required section above for links to create accounts with these services.
3. In the n8n credentials manager, double click the node named Authenticartion get token. In the credential field, click Create new credential, choose Custom Auth, then follow the on screen steps to add your Adobe client id and client secret.
4. Open any Adobe HTTP Request node that makes API calls. In the credential dropdown, click Create new credential, choose Header Auth, and add your Adobe API key in the header as required by Adobe.
5. Double click the Dropbox node named Load a test pdf file. In the credential field, click Create new credential, choose Dropbox OAuth2, and complete the sign in. Test the node to confirm a file downloads.
6. Open the Set node named Adobe API Query. Set the endpoint field to the Adobe operation you need such as extractpdf or splitpdf. Paste the JSON payload that operation expects and do not include the asset ID because the flow fills it in.
7. Run the workflow with Test. Check the token node returns an access token. If it fails, confirm your client id and secret and retry.
8. Inspect the Create Asset node output. You should see an asset ID. If missing, check your header auth API key and that the Authorization header is set from the token node.
9. Confirm the Upload PDF File node returns a success response. If it fails, verify that the incoming item has a binary PDF and that the media type is set to application pdf.
10. Watch the Wait and Try to download the result nodes. The Switch node will loop back to wait if the job is not ready. When ready, you will receive a download link or file data.
11. If you plan to call this from another workflow, trigger it with Execute Workflow and read the output from the node named Forward response to origin workflow.
12. Troubleshooting tips: ensure the endpoint name is correct, remove asset ID from your payload, allow extra wait time for large files, and review node logs for any status or rate limit messages.