Skip to Workflow Atlas
ETL PipelineAI systemIntermediate

Automated PDF Invoice Workflow

Automated PDF Invoice Workflow is a 3-node automation blueprint connecting JSReport, Gmail. Inspect its trigger, execution graph, branches, and implementation requirements.

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.

3

Nodes

2

Links

1

Run groups

Connected tools

2 integrations

  • JSReport
  • Gmail

Canvas controls

Fit wide systems, then zoom into any run group.

Automated PDF Invoice Workflow execution lanes1 run groups containing 3 workflow nodes and 2 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.Form Invoice. trigger node, formTrigger. 0 incoming and 1 outgoing connections.STARTForm InvoiceTRIGGERFORMTRIGGER0 IN / 1 OUTGet PDF From JSReport. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 02Get PDF From JSReportINTEGRATIONHTTPREQUEST1 IN / 1 OUTSend invoice. Gmail node, gmail. 1 incoming and 0 outgoing connections.OUTCOMESend invoiceGMAILGMAIL1 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.3 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

Form Invoice

2 Execution Links
  1. Start

    Form Invoice

    Trigger

  2. Step 2

    Get PDF From JSReport

    Integration

  3. Outcome

    Send invoice

    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.