Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
ETL PipelineAI systemIntermediate

Automated Invoice Processing & Archiving

Automated Invoice Processing & Archiving is a 10-node automation blueprint connecting Google Drive, Gmail, Slack. Inspect its trigger, execution graph, branches, and implementation requirements.

Google DriveGmailSlack

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.

10

Nodes

9

Links

1

Run groups

Connected tools

3 integrations

  • Google Drive
  • Gmail
  • Slack

Canvas controls

Fit wide systems, then zoom into any run group.

Automated Invoice Processing & Archiving execution lanes1 run groups containing 10 workflow nodes and 9 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.On clicking 'execute'. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTOn clicking 'execute'TRIGGERMANUALTRIGGER0 IN / 1 OUTEvery 23:45. integration node, cron. 0 incoming and 1 outgoing connections.STARTEvery 23:45INTEGRATIONCRON0 IN / 1 OUTCurrent date. transform node, function. 0 incoming and 1 outgoing connections.STARTCurrent dateTRANSFORMFUNCTION0 IN / 1 OUTGet Year folder. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 02Get Year folderGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTOrlen Invoice. Gmail node, gmail. 2 incoming and 1 outgoing connections.STEP 02Orlen InvoiceGMAILGMAIL2 IN / 1 OUTGet Month folder. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 03Get Month folderGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTMerge. decision node, merge. 2 incoming and 1 outgoing connections.STEP 04MergeDECISIONMERGE2 IN / 1 OUTUpload Invoice to Google Drive. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 05Upload Invoice to Google …GOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTMark as Read. Gmail node, gmail. 1 incoming and 1 outgoing connections.STEP 06Mark as ReadGMAILGMAIL1 IN / 1 OUTSlack. Slack node, slack. 1 incoming and 0 outgoing connections.OUTCOMESlackSLACKSLACK1 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.10 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

On clicking 'execute'

9 Execution Links

  1. Start

    On clicking 'execute'

    Trigger

    Every 23:45

    Integration

    Current date

    Transform

  2. Step 2

    Get Year folder

    Integration

    Orlen Invoice

    Integration

  3. Step 3

    Get Month folder

    Integration

  4. Step 4

    Merge

    Decision

  5. Step 5

    Upload Invoice to Google Drive

    Integration

  6. Step 6

    Mark as Read

    Integration

  7. Outcome

    Slack

    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