Skip to Workflow Atlas
Event-Driven AutomationAI systemIntermediate

Automated Invoice Management via Gmail

Automated Invoice Management via Gmail is a 11-node automation blueprint connecting Gmail, Google Drive. 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.

11

Nodes

10

Links

1

Run groups

Connected tools

2 integrations

  • Gmail
  • Google Drive

Canvas controls

Fit wide systems, then zoom into any run group.

Automated Invoice Management via Gmail execution lanes1 run groups containing 11 workflow nodes and 10 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.Gmail Trigger. Gmail node, gmailTrigger. 0 incoming and 1 outgoing connections.STARTGmail TriggerGMAILGMAILTRIGGER0 IN / 1 OUTSetup. transform node, set. 1 incoming and 1 outgoing connections.STEP 02SetupTRANSFORMSET1 IN / 1 OUTOnly n8n Paddle invoice mails. decision node, if. 1 incoming and 2 outgoing connections.STEP 03Only n8n Paddle invoice m…DECISIONIF1 IN / 2 OUTExtract "a-tags" from email. integration node, html. 1 incoming and 1 outgoing connections.STEP 04Extract "a-tags" from emailINTEGRATIONHTML1 IN / 1 OUTDo nothing on other emails. integration node, noOp. 1 incoming and 0 outgoing connections.STEP 04Do nothing on other emailsINTEGRATIONNOOP1 IN / 0 OUTSplit Out. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 05Split OutTRANSFORMSPLITOUT1 IN / 1 OUTOnly keep invoice link. decision node, filter. 1 incoming and 1 outgoing connections.STEP 06Only keep invoice linkDECISIONFILTER1 IN / 1 OUTDownload Invoice PDF from URL. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 07Download Invoice PDF from…INTEGRATIONHTTPREQUEST1 IN / 1 OUTUpload PDF to Drive. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 08Upload PDF to DriveINTEGRATIONHTTPREQUEST1 IN / 1 OUTRename file. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 09Rename fileGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTMove to the correct folder. Google Drive node, googleDrive. 1 incoming and 0 outgoing connections.OUTCOMEMove to the correct folderGOOGLE DRIVEGOOGLEDRIVE1 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.11 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

Gmail Trigger

10 Execution Links
  1. Start

    Gmail Trigger

    Trigger

  2. Step 2

    Setup

    Transform

  3. Step 3

    Only n8n Paddle invoice mails

    Decision

  4. Step 4

    Extract "a-tags" from email

    Integration

    Do nothing on other emails

    Integration

  5. Step 5

    Split Out

    Transform

  6. Step 6

    Only keep invoice link

    Decision

  7. Step 7

    Download Invoice PDF from URL

    Integration

  8. Step 8

    Upload PDF to Drive

    Integration

  9. Step 9

    Rename file

    Integration

  10. Outcome

    Move to the correct folder

    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.