HumationHuman + Automation
Back to Catalog

Manipulate PDF with Adobe developer API

digi-stud.iodigi-stud.io
4606 views
2/3/2026
File ManagementGoogle DriveWebhookData StorageDate Based
Official Page

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)
  • ...

The free tier allows up to 500 PDF operation / month. As it comes directly from Adobe, it works often better than other alternatives.

Adobe documentation:

What does this workflow do

The API is a bit painful to use. To perform a transformation on a PDF it requires to

  • Authenticate and get a temporal token
  • Register a new asset (file)
  • Upload you PDF to the registered asset
  • Perform a query according to the transformation requested
  • Wait for the query to be proccessed by Adobe backend
  • Download the result

This workflow is a generic wrapper to perform all these steps for any transformation endpoint. I usually use it from other workflow with an Execute Workflow node.

Examples are given in the workflow.

Example use case

This service is useful for example to clean PDF data for an AI / RAG system.

My favorite use-case is to extract table as images and forward images to an AI for image recognition / description which is often more accuarate than feedind raw tabular data to a LLM.

n8n Workflow: Manipulate PDF with Adobe Developer API (Placeholder)

This n8n workflow serves as a foundational structure, likely intended to interact with the Adobe Developer API for PDF manipulation. While the current JSON definition primarily outlines a basic flow with a manual trigger and a few core n8n nodes, it sets the stage for a more complex automation involving file operations, API calls, and conditional logic.

Note: The provided JSON does not contain specific Adobe Developer API nodes or configurations. The description below is based on the potential purpose suggested by the directory name and the generic nodes present, assuming the workflow is a starting point for such an integration.

What it does

This workflow currently defines a basic execution path, demonstrating how to:

  1. Manually Trigger Execution: Start the workflow with a single click in the n8n editor.
  2. Set Initial Data: Define or modify data fields within the workflow.
  3. Introduce a Delay: Pause the workflow for a specified duration.
  4. Route Based on Conditions: Implement conditional logic to direct the workflow's path.
  5. Perform HTTP Requests: Make calls to external APIs (e.g., Adobe Developer API).
  6. Merge Data Streams: Combine data from different branches of the workflow.
  7. Interact with Dropbox: Potentially upload, download, or list files in Dropbox.
  8. Trigger Another Workflow: Initiate the execution of a separate n8n workflow.

Prerequisites/Requirements

To fully utilize this workflow once it's configured for PDF manipulation with Adobe Developer API, you would typically need:

  • n8n Instance: A running n8n instance (self-hosted or cloud).
  • Dropbox Account: Configured credentials for Dropbox within n8n.
  • Adobe Developer Account: Access to Adobe Developer APIs (e.g., PDF Services API, Document Generation API) and corresponding API credentials (Client ID, Client Secret, etc.).
  • Understanding of Adobe API Endpoints: Knowledge of the specific API endpoints and request formats for PDF operations (e.g., combining PDFs, converting files, extracting text).

Setup/Usage

  1. Import the Workflow:
    • In your n8n instance, go to "Workflows".
    • Click "New" -> "Import from JSON".
    • Paste the provided JSON content and click "Import".
  2. Configure Credentials (if applicable):
    • Locate the "Dropbox" node (ID: 8). You would need to set up a Dropbox credential if not already done.
    • For the "HTTP Request" node (ID: 19), you would typically configure it to make calls to the Adobe Developer API. This would involve setting the URL, HTTP method, headers (e.g., for authentication with Adobe API Key), and body with the necessary payload for PDF manipulation.
  3. Customize Nodes:
    • Edit Fields (Set) (ID: 38): Modify this node to set any initial data or parameters required for your PDF operations.
    • Wait (ID: 514): Adjust the delay as needed for your specific use case.
    • Switch (ID: 112): Implement your desired conditional logic based on input data or API responses to branch the workflow.
    • HTTP Request (ID: 19): This node is crucial for interacting with the Adobe Developer API. Configure it with the correct API endpoint, authentication (e.g., OAuth 2.0 or API Key), and request body for your specific PDF task (e.g., POST /dc-integration/v1/combine/files).
    • Dropbox (ID: 8): Configure this node to read input files or upload processed PDF files.
    • Merge (ID: 24): Use this node to combine results from different branches if your workflow involves parallel processing or conditional paths.
    • Execute Workflow Trigger (ID: 837): If this workflow is part of a larger system, configure this node to call another n8n workflow.
  4. Activate the Workflow: Once configured, click the "Activate" toggle in the top right corner of the workflow editor to enable it.
  5. Execute:
    • For manual testing, click "Execute Workflow" on the "When clicking โ€˜Execute workflowโ€™" node (ID: 838).
    • If triggered by another workflow, ensure the calling workflow is properly configured to execute this one.

Related Templates

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch ๐Ÿ”— LinkedIn โ€“ Wessel Bulte

Wessel BulteBy Wessel Bulte
247

๐ŸŽ“ How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From โ€“ senderโ€™s email address To โ€“ recipientโ€™s email address Subject โ€“ email subject line Summary โ€“ short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits โœ… Full Automation: Eliminates manual reading and data entry from incoming emails. โœ… Multi-Source Integration: Handles data from different email providers seamlessly. โœ… AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. โœ… Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. โœ… Time Efficiency: Processes emails in real time, improving productivity and response speed. *โœ… Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616

Automated YouTube video uploads with 12h interval scheduling in JST

This workflow automates a batch upload of multiple videos to YouTube, spacing each upload 12 hours apart in Japan Standard Time (UTC+9) and automatically adding them to a playlist. โš™๏ธ Workflow Logic Manual Trigger โ€” Starts the workflow manually. List Video Files โ€” Uses a shell command to find all .mp4 files under the specified directory (/opt/downloads/ๅ•่ฏๅก/A1-A2). Sort and Generate Items โ€” Sorts videos by day number (dayXX) extracted from filenames and assigns a sequential order value. Calculate Publish Schedule (+12h Interval) โ€” Computes the next rounded JST hour plus a configurable buffer (default 30 min). Staggers each videoโ€™s scheduled time by order ร— 12 hours. Converts JST back to UTC for YouTubeโ€™s publishAt field. Split in Batches (1 per video) โ€” Iterates over each video item. Read Video File โ€” Loads the corresponding video from disk. Upload to YouTube (Scheduled) โ€” Uploads the video privately with the computed publishAtUtc. Add to Playlist โ€” Adds the newly uploaded video to the target playlist. ๐Ÿ•’ Highlights Timezone-safe: Pure UTC โ†” JST conversion avoids double-offset errors. Sequential scheduling: Ensures each upload is 12 hours apart to prevent clustering. Customizable: Change SPANHOURS, BUFFERMIN, or directory paths easily. Retry-ready: Each upload and playlist step has retry logic to handle transient errors. ๐Ÿ’ก Typical Use Cases Multi-part educational video series (e.g., A1โ€“A2 English learning). Regular content release cadence without manual scheduling. Automated YouTube publishing pipelines for pre-produced content. --- Author: Zane Category: Automation / YouTube / Scheduler Timezone: JST (UTC+09:00)

ZaneBy Zane
226