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

Automated PDF Merger Workflow

Automated PDF Merger Workflow is a 7-node automation blueprint connecting HTTP API, Custom PDF merge service. Inspect its trigger, execution graph, branches, and implementation requirements.

HTTP APICustom PDF merge service

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

7

Links

1

Run groups

Connected tools

2 integrations

  • HTTP API
  • Custom PDF merge service

Canvas controls

Fit wide systems, then zoom into any run group.

Automated PDF Merger Workflow execution lanes1 run groups containing 7 workflow nodes and 7 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 2 outgoing connections.STARTWhen clicking ‘Test workf…TRIGGERMANUALTRIGGER0 IN / 2 OUTHTTP Request. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 02HTTP RequestINTEGRATIONHTTPREQUEST1 IN / 1 OUTHTTP Request2. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 02HTTP Request2INTEGRATIONHTTPREQUEST1 IN / 1 OUTMerge. decision node, merge. 2 incoming and 1 outgoing connections.STEP 03MergeDECISIONMERGE2 IN / 1 OUTMerge PDF1. decision node, @custom-js/n8n-nodes-pdf-toolkit.mergePdfs. 1 incoming and 1 outgoing connections.STEP 04Merge PDF1DECISION@CUSTOM-JS/N8N-NODES-PD1 IN / 1 OUTRead/Write Files from Disk. integration node, readWriteFile. 1 incoming and 1 outgoing connections.STEP 05Read/Write Files from DiskINTEGRATIONREADWRITEFILE1 IN / 1 OUTRead/Write Files from Disk4. integration node, readWriteFile. 1 incoming and 0 outgoing connections.OUTCOMERead/Write Files from Disk4INTEGRATIONREADWRITEFILE1 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’

7 Execution Links

  1. Start

    When clicking ‘Test workflow’

    Trigger

  2. Step 2

    HTTP Request

    Integration

    HTTP Request2

    Integration

  3. Step 3

    Merge

    Decision

  4. Step 4

    Merge PDF1

    Decision

  5. Step 5

    Read/Write Files from Disk

    Integration

  6. Outcome

    Read/Write Files from Disk4

    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