Library / Documents, PDF & OCR
Documents, PDF & OCR
Manipulate PDFs with the Adobe Developer API
When you run it or call it from another workflow, it uploads a PDF asset and sends processing requests to the Adobe PDF Services API.
What it does
# 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.
The steps
- When clicking ‘Test workflow’
- Create Asset
- Execute Workflow Trigger
- Adobe API Query
- Load a test pdf file
- Query + File
- Query + File + Asset information
- Process Query
- Wait 5 second
- Try to download the result
- Switch
- Forward response to origin workflow
- Authenticartion (get token)
- Upload PDF File (asset)
Similar automations