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

Daily Activity Encouragement Workflow

Daily Activity Encouragement Workflow is a 6-node automation blueprint connecting Strava, SMTP Email. Inspect its trigger, execution graph, branches, and implementation requirements.

StravaSMTP Email

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

2 integrations

  • Strava
  • SMTP Email

Canvas controls

Fit wide systems, then zoom into any run group.

Daily Activity Encouragement Workflow 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 Daily at 11:AM. integration node, cron. 0 incoming and 1 outgoing connections.STARTCheck Daily at 11:AMINTEGRATIONCRON0 IN / 1 OUTAccountability Settings. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Accountability SettingsTRANSFORMSET1 IN / 1 OUTStrava. integration node, strava. 1 incoming and 1 outgoing connections.STEP 03StravaINTEGRATIONSTRAVA1 IN / 1 OUTCheck Activity Level. decision node, if. 1 incoming and 2 outgoing connections.STEP 04Check Activity LevelDECISIONIF1 IN / 2 OUTEnough Activity. integration node, noOp. 1 incoming and 0 outgoing connections.OUTCOMEEnough ActivityINTEGRATIONNOOP1 IN / 0 OUTSend Email. integration node, emailSend. 1 incoming and 0 outgoing connections.OUTCOMESend EmailINTEGRATIONEMAILSEND1 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 Daily at 11:AM

5 Execution Links

  1. Start

    Check Daily at 11:AM

    Integration

  2. Step 2

    Accountability Settings

    Transform

  3. Step 3

    Strava

    Integration

  4. Step 4

    Check Activity Level

    Decision

  5. Outcome

    Enough Activity

    Integration

    Send Email

    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