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

PDF to Text Automation Workflow

PDF to Text Automation Workflow is a 5-node automation blueprint connecting customJsApi. Inspect its trigger, execution graph, branches, and implementation requirements.

customJsApi

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

  • customJsApi

Canvas controls

Fit wide systems, then zoom into any run group.

PDF to Text Automation Workflow 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.When clicking ‘Test workflow’. trigger node, manualTrigger. 0 incoming and 2 outgoing connections.STARTWhen clicking ‘Test workf…TRIGGERMANUALTRIGGER0 IN / 2 OUTHTML to PDF. integration node, @custom-js/n8n-nodes-pdf-toolkit.html2Pdf. 1 incoming and 1 outgoing connections.STEP 02HTML to PDFINTEGRATION@CUSTOM-JS/N8N-NODES-PD1 IN / 1 OUTCode. transform node, code. 1 incoming and 1 outgoing connections.STEP 02CodeTRANSFORMCODE1 IN / 1 OUTConvert PDF into Text. integration node, @custom-js/n8n-nodes-pdf-toolkit.PdfToText. 1 incoming and 0 outgoing connections.OUTCOMEConvert PDF into TextINTEGRATION@CUSTOM-JS/N8N-NODES-PD1 IN / 0 OUTConvert PDF into Text1. integration node, @custom-js/n8n-nodes-pdf-toolkit.PdfToText. 1 incoming and 0 outgoing connections.OUTCOMEConvert PDF into Text1INTEGRATION@CUSTOM-JS/N8N-NODES-PD1 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

When clicking ‘Test workflow’

4 Execution Links

  1. Start

    When clicking ‘Test workflow’

    Trigger

  2. Step 2

    HTML to PDF

    Integration

    Code

    Transform

  3. Outcome

    Convert PDF into Text

    Integration

    Convert PDF into Text1

    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