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

The entire automation, wired and inspectable.

Brand marks identify the operational stack. Focus or select any node to isolate its real incoming and outgoing connections.

7

Nodes

7

Edges

6

Zones

System stack

2 integrations

  • HTTP API
  • Custom PDF merge service
Automated PDF Merger Workflow interactive execution graphStructural view of 7 workflow nodes and 7 visible connections. Focus any node to inspect its connected path. Parameters and credentials are intentionally excluded.When clicking ‘Test workflow’. trigger node, manualTrigger. 0 incoming and 2 outgoing connections.When clicking ‘Test workf…TRIGGERMANUALTRIGGER0 IN / 2 OUTHTTP Request. integration node, httpRequest. 1 incoming and 1 outgoing connections.HTTP RequestINTEGRATIONHTTPREQUEST1 IN / 1 OUTHTTP Request2. integration node, httpRequest. 1 incoming and 1 outgoing connections.HTTP Request2INTEGRATIONHTTPREQUEST1 IN / 1 OUTMerge. decision node, merge. 2 incoming and 1 outgoing connections.MergeDECISIONMERGE2 IN / 1 OUTMerge PDF1. decision node, @custom-js/n8n-nodes-pdf-toolkit.mergePdfs. 1 incoming and 1 outgoing connections.Merge PDF1DECISION@CUSTOM-JS/N8N-NODES-PD1 IN / 1 OUTRead/Write Files from Disk. integration node, readWriteFile. 1 incoming and 1 outgoing connections.Read/Write Files from DiskINTEGRATIONREADWRITEFILE1 IN / 1 OUTRead/Write Files from Disk4. integration node, readWriteFile. 1 incoming and 0 outgoing connections.Read/Write Files from Disk4INTEGRATIONREADWRITEFILE1 IN / 0 OUT

Signal inspector

Focus, hover, or select a node to illuminate its real path.

triggeraidecisiontransformintegration
Scroll horizontally to inspect every zone.7 connected nodesEnter or click to lock · Escape to clear

Structured review

Read the workflow as a system, not a node dump.

The workflow is grouped into operational zones, then reviewed for the controls needed to adapt the pattern safely.

01

Entry signals

1 node

Events, schedules, and unconnected roots that can start an execution.

When clicking ‘Test workflow’

Trigger

02

Data & operations

3 nodes

Transformations and external-system actions that move the work forward.

HTTP Request

Integration

HTTP Request2

Integration

Read/Write Files from Disk

Integration

03

Intelligence & routing

2 nodes

Model calls and control points that interpret, branch, or govern the run.

Merge

Decision

Merge PDF1

Decision

04

Terminal actions

1 node

Nodes with no visible outgoing edge: the workflow’s observable outcomes.

Read/Write Files from Disk4

Integration

Adjacent systems

Keep tracing the stack.

Related workflows share tools and similar system patterns.

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