Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
ETL PipelineIntermediate

Automated PDF Processing Workflow

Automated PDF Processing Workflow is a 7-node automation blueprint connecting Custom API for data fetching. Inspect its trigger, execution graph, branches, and implementation requirements.

Custom API for data fetching

Interactive system map

Follow the runtime. Inspect what supports it.

Solid horizontal paths show main-channel execution. Violet dependencies sit beneath the exact step they configure or empower.

7

Nodes

6

Links

1

Run groups

Connected tools

1 integrations

  • Custom API for data fetching

Canvas controls

Fit wide systems, then zoom into any run group.

Automated PDF Processing Workflow execution lanes1 run groups containing 7 workflow nodes and 6 visible links. Solid horizontal lines are main-channel runtime links. Violet dashed lines connect typed dependencies beneath the runtime step they support. Focus any node to inspect its immediate path.When clicking ‘Test workflow’. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTWhen clicking ‘Test workf…TRIGGERMANUALTRIGGER0 IN / 1 OUTPDF Array. transform node, code. 1 incoming and 1 outgoing connections.STEP 02PDF ArrayTRANSFORMCODE1 IN / 1 OUTSplit Out. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 03Split OutTRANSFORMSPLITOUT1 IN / 1 OUTHTTP Request1. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 04HTTP Request1INTEGRATIONHTTPREQUEST1 IN / 1 OUTMerge PDF. decision node, @custom-js/n8n-nodes-pdf-toolkit.mergePdfs. 1 incoming and 1 outgoing connections.STEP 05Merge PDFDECISION@CUSTOM-JS/N8N-NODES-PD1 IN / 1 OUTRead/Write Files from Disk2. integration node, readWriteFile. 1 incoming and 1 outgoing connections.STEP 06Read/Write Files from Disk2INTEGRATIONREADWRITEFILE1 IN / 1 OUTRead/Write Files from Disk3. integration node, readWriteFile. 1 incoming and 0 outgoing connections.OUTCOMERead/Write Files from Disk3INTEGRATIONREADWRITEFILE1 IN / 0 OUT

Signal inspector

Focus, hover, or select a step to isolate its runtime and support links.

Main-channel runtimeTyped dependencytriggeraidecisiontransformintegration
Scroll horizontally to follow every connected flow.7 connected nodesEnter or click to lock · Escape to clear

Runtime breakdown

Read the execution spine before its dependencies.

Each run group separates main-channel steps from the models, tools, retrievers, and data services that support them. Start and outcome labels apply only to runtime nodes.

01

Run Group

When clicking ‘Test workflow’

6 Execution Links

  1. Start

    When clicking ‘Test workflow’

    Trigger

  2. Step 2

    PDF Array

    Transform

  3. Step 3

    Split Out

    Transform

  4. Step 4

    HTTP Request1

    Integration

  5. Step 5

    Merge PDF

    Decision

  6. Step 6

    Read/Write Files from Disk2

    Integration

  7. Outcome

    Read/Write Files from Disk3

    Integration

Turn the map into a plan

Adapt this blueprint to your company.

Bring the system shape into a workspace, then define the production controls, data boundaries, owners, and delivery sequence around your context.

Create a build planReturn to the atlas