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

Automated Gmail Thread Archiving

Automated Gmail Thread Archiving is a 7-node automation blueprint connecting Gmail. Inspect its trigger, execution graph, branches, and implementation requirements.

Gmail

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.

7

Nodes

6

Links

1

Run groups

Connected tools

1 integrations

  • Gmail

Canvas controls

Fit wide systems, then zoom into any run group.

Automated Gmail Thread Archiving execution lanes1 run groups containing 7 workflow nodes and 6 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.At midnight every work day. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.STARTAt midnight every work dayTRIGGERSCHEDULETRIGGER0 IN / 1 OUTGet all emails in the last day. Gmail node, gmail. 1 incoming and 1 outgoing connections.STEP 02Get all emails in the las…GMAILGMAIL1 IN / 1 OUTGet the thread of each email. Gmail node, gmail. 1 incoming and 1 outgoing connections.STEP 03Get the thread of each em…GMAILGMAIL1 IN / 1 OUTKeep only starred emails in inbox. decision node, filter. 1 incoming and 2 outgoing connections.STEP 04Keep only starred emails …DECISIONFILTER1 IN / 2 OUTArchive thread (remove from inbox). Gmail node, gmail. 1 incoming and 0 outgoing connections.STEP 05Archive thread (remove f…GMAILGMAIL1 IN / 0 OUTfor each message in the thread. transform node, itemLists. 1 incoming and 1 outgoing connections.STEP 05for each message in the t…TRANSFORMITEMLISTS1 IN / 1 OUTArchive message (remove from inbox). Gmail node, gmail. 1 incoming and 0 outgoing connections.OUTCOMEArchive message (remove f…GMAILGMAIL1 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.7 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

At midnight every work day

6 Execution Links

  1. Start

    At midnight every work day

    Trigger

  2. Step 2

    Get all emails in the last day

    Integration

  3. Step 3

    Get the thread of each email

    Integration

  4. Step 4

    Keep only starred emails in inbox

    Decision

  5. Step 5

    Archive thread (remove from inbox)

    Integration

    for each message in the thread

    Transform

  6. Outcome

    Archive message (remove from inbox)

    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