Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationAI systemIntermediate

Automated Email Attachment Processing

Automated Email Attachment Processing is a 14-node automation blueprint connecting Gmail, Google Drive, Google Sheets. Inspect its trigger, execution graph, branches, and implementation requirements.

GmailGoogle DriveGoogle SheetsOpenAI

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.

14

Nodes

14

Links

1

Run groups

Connected tools

4 integrations

  • Gmail
  • Google Drive
  • Google Sheets
  • OpenAI

Canvas controls

Fit wide systems, then zoom into any run group.

Automated Email Attachment Processing execution lanes1 run groups containing 14 workflow nodes and 14 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 Trigger1. Gmail node, gmailTrigger. 0 incoming and 1 outgoing connections.STARTGmail Trigger1GMAILGMAILTRIGGER0 IN / 1 OUTSetup1. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Setup1TRANSFORMSET1 IN / 1 OUTOnly invoice mails with attachments. decision node, if. 1 incoming and 2 outgoing connections.STEP 03Only invoice mails with a…DECISIONIF1 IN / 2 OUTUpload PDF to Drive1. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 04Upload PDF to Drive1INTEGRATIONHTTPREQUEST1 IN / 1 OUTRename file1. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 05Rename file1GOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTMove to the correct folder1. Google Drive node, googleDrive. 1 incoming and 2 outgoing connections.STEP 06Move to the correct folder1GOOGLE DRIVEGOOGLEDRIVE1 IN / 2 OUTGoogle Drive. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 07Google DriveGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTGmail. Gmail node, gmail. 2 incoming and 0 outgoing connections.STEP 07GmailGMAILGMAIL2 IN / 0 OUTExtract from File2. integration node, extractFromFile. 1 incoming and 1 outgoing connections.STEP 08Extract from File2INTEGRATIONEXTRACTFROMFILE1 IN / 1 OUTApply Data Extraction Rules. ai node, chainLlm. 3 incoming and 1 outgoing connections.STEP 09Apply Data Extraction RulesAICHAINLLM3 IN / 1 OUTMap Output. transform node, set. 1 incoming and 1 outgoing connections.STEP 10Map OutputTRANSFORMSET1 IN / 1 OUTAppend to Reconciliation Sheet. Google Sheets node, googleSheets. 1 incoming and 0 outgoing connections.OUTCOMEAppend to Reconciliation …GOOGLE SHEETSGOOGLESHEETS1 IN / 0 OUTOpenAI Model. OpenAI node, lmOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI ModelOPENAILMOPENAI0 IN / 1 OUTStructured Output Parser. ai node, outputParserStructured. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Structured Output ParserAIOUTPUTPARSERSTRUCTURED0 IN / 1 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.14 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 Trigger1

12 Execution Links2 Support Dependencies

  1. Start

    Gmail Trigger1

    Trigger

  2. Step 2

    Setup1

    Transform

  3. Step 3

    Only invoice mails with attachments

    Decision

  4. Step 4

    Upload PDF to Drive1

    Integration

  5. Step 5

    Rename file1

    Integration

  6. Step 6

    Move to the correct folder1

    Integration

  7. Step 7

    Google Drive

    Integration

    Gmail

    Integration

  8. Step 8

    Extract from File2

    Integration

  9. Step 9

    Apply Data Extraction Rules

    AI reasoning

  10. Step 10

    Map Output

    Transform

  11. Outcome

    Append to Reconciliation Sheet

    Integration

Attached dependencies

These nodes support the runtime above; they are not additional starts or outcomes.

2 nodes

  • OpenAI Model

    AI reasoning dependency

  • Structured Output Parser

    AI reasoning dependency

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