Automation & utilitiesDropboxExecute Workflow TriggerHTTP RequestManual TriggerMerge

Wait for file do be processed

Configured with Dropbox, Execute Workflow Trigger, HTTP Request, Switch, and additional nodes. Review the connections and setup before adapting this template.

Download workflow JSON View files on GitHub ↗14 nodes · MIT

Workflow preview

Node categories in this workflow

Trigger
Web / API
Transform
Files / media
Wait
Routing

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
Node	Category	Type	Operation
When clicking ‘Test workflow’	Trigger	Manual Trigger	See node parameters
Create Asset	Web / API	HTTP Request	POST
Execute Workflow Trigger	Trigger	Execute Workflow Trigger	See node parameters
Adobe API Query	Transform	Edit Fields	See node parameters
Load a test pdf file	Files / media	Dropbox	download
Query + File	Transform	Merge	See node parameters
Query + File + Asset information	Transform	Merge	See node parameters
Process Query	Web / API	HTTP Request	POST
Wait 5 second	Wait	Wait	See node parameters
Try to download the result	Web / API	HTTP Request	See node parameters
Switch	Routing	Switch	See node parameters
Forward response to origin workflow	Transform	Edit Fields	See node parameters
Authenticartion (get token)	Web / API	HTTP Request	POST
Upload PDF File (asset)	Web / API	HTTP Request	PUT

Setup

Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

dropboxOAuth2Api
httpCustomAuth
httpHeaderAuth

Workflow notes

Adobe API Wrapper

See Adobe documentation:

https://developer.adobe.com/document-services/docs/overview/pdf-services-api/howtos/
https://developer.adobe.com/document-services/docs/overview/pdf-extract-api/gettingstarted/

In short, this workflow does the following steps :

Authentication
Upload an asset (pdf) to adobe
Wait for the asset to be processed by Adobe
Download the result

Credential

Credentials are not "predefined" and you'll have to create 2 custom credentials, detailed in the workflow.

Result

The result will depend on the transformation requested. It could be 1 of various files (json, zip...) accessible via download URL returned by the workflow.

Workflow can be tested with a PDF filed fetched with Dorpbox for example or any storage provider.

1- Credential for token request

Create a "Custom Auth" credential like this :

{
  "headers": {
    "Content-Type":"application/x-www-form-urlencoded"
  }, 
  "body" : {
      "client_id": "****", 
      "client_secret":"****"
  }
}

2- Credential for all other Queries

Create a "Header Auth" credential like this :

X-API-Key: **** (same value as client_id)

Workflow Input

endpoint: splitpdf, extractpdf, ...
json_payload : all endpoint payload except assetID which is handled in current workflow
PDF Data as n8n Binary

Example for split :

{
   "endpoint": "splitpdf",
   "json_payload": {
      "splitoption": 
         { "pageRanges": [{"start": 1,"end": 2}]}
       }
    }
}

Example for extractpdf

{
   "endpoint": "splitpdf",
   "json_payload": {
      "renditionsToExtract": [
        "tables"
       ],
      "elementsToExtract": [
        "text",
        "tables"
     ]
   }
}

Wait for file do be processed

Purpose and structure

This folder contains the Wait for file do be processed workflow. Its executable nodes use dropbox, executeWorkflowTrigger, httpRequest, manualTrigger, merge, set, switch, wait. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

When clicking ‘Test workflow’, Execute Workflow Trigger

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Wait/0582_Wait_Dropbox_Create_Webhook.json MIT; preserve source notices.

Canvas section labels

These name areas of the original canvas; they do not include explanatory instructions.

Testing for development
Wait for file do be processed

More in Automation & utilities

1/ Add Your credentials 2. Refresh Pipedrive tokens 6