Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationIntermediate

PDF Generation via Webhook

PDF Generation via Webhook is a 5-node automation blueprint connecting Custom PDF Conversion API. Inspect its trigger, execution graph, branches, and implementation requirements.

Custom PDF Conversion API

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.

5

Nodes

4

Links

1

Run groups

Connected tools

1 integrations

  • Custom PDF Conversion API

Canvas controls

Fit wide systems, then zoom into any run group.

PDF Generation via Webhook execution lanes1 run groups containing 5 workflow nodes and 4 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.Webhook. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTWebhookTRIGGERWEBHOOK0 IN / 1 OUTSet data. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Set dataTRANSFORMSET1 IN / 1 OUTPreprocess. transform node, code. 1 incoming and 1 outgoing connections.STEP 03PreprocessTRANSFORMCODE1 IN / 1 OUTHTML to PDF. integration node, @custom-js/n8n-nodes-pdf-toolkit.html2Pdf. 1 incoming and 1 outgoing connections.STEP 04HTML to PDFINTEGRATION@CUSTOM-JS/N8N-NODES-PD1 IN / 1 OUTRespond to Webhook. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.OUTCOMERespond to WebhookTRIGGERRESPONDTOWEBHOOK1 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.5 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

Webhook

4 Execution Links

  1. Start

    Webhook

    Trigger

  2. Step 2

    Set data

    Transform

  3. Step 3

    Preprocess

    Transform

  4. Step 4

    HTML to PDF

    Integration

  5. Outcome

    Respond to Webhook

    Trigger

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