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

Email Expense Extraction to Google Sheets

Email Expense Extraction to Google Sheets is a 6-node automation blueprint connecting IMAP Email, Mindee API, Google Sheets. Inspect its trigger, execution graph, branches, and implementation requirements.

IMAP EmailMindee APIGoogle Sheets

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.

6

Nodes

5

Links

1

Run groups

Connected tools

3 integrations

  • IMAP Email
  • Mindee API
  • Google Sheets

Canvas controls

Fit wide systems, then zoom into any run group.

Email Expense Extraction to Google Sheets execution lanes1 run groups containing 6 workflow nodes and 5 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.Check for new emails. integration node, emailReadImap. 0 incoming and 1 outgoing connections.STARTCheck for new emailsINTEGRATIONEMAILREADIMAP0 IN / 1 OUTSetup Variables. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Setup VariablesTRANSFORMSET1 IN / 1 OUTCheck subject. decision node, if. 1 incoming and 1 outgoing connections.STEP 03Check subjectDECISIONIF1 IN / 1 OUTRead Receipts. integration node, mindee. 1 incoming and 1 outgoing connections.STEP 04Read ReceiptsINTEGRATIONMINDEE1 IN / 1 OUTSet column data. transform node, set. 1 incoming and 1 outgoing connections.STEP 05Set column dataTRANSFORMSET1 IN / 1 OUTAdd to Google Sheet. Google Sheets node, googleSheets. 1 incoming and 0 outgoing connections.OUTCOMEAdd to Google SheetGOOGLE SHEETSGOOGLESHEETS1 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.6 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

Check for new emails

5 Execution Links

  1. Start

    Check for new emails

    Integration

  2. Step 2

    Setup Variables

    Transform

  3. Step 3

    Check subject

    Decision

  4. Step 4

    Read Receipts

    Integration

  5. Step 5

    Set column data

    Transform

  6. Outcome

    Add to Google Sheet

    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