Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationIntermediate

Weekly Coffee Chat Coordinator

Weekly Coffee Chat Coordinator is a 6-node automation blueprint connecting Mattermost, Google Calendar. Inspect its trigger, execution graph, branches, and implementation requirements.

MattermostGoogle Calendar

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

  • Mattermost
  • Google Calendar

Canvas controls

Fit wide systems, then zoom into any run group.

Weekly Coffee Chat Coordinator 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.Weekly trigger on monday. integration node, cron. 0 incoming and 1 outgoing connections.STARTWeekly trigger on mondayINTEGRATIONCRON0 IN / 1 OUTGreetings. integration node, mattermost. 1 incoming and 1 outgoing connections.STEP 02GreetingsINTEGRATIONMATTERMOST1 IN / 1 OUTEmployees in coffee chat channel. integration node, mattermost. 1 incoming and 1 outgoing connections.STEP 03Employees in coffee chat …INTEGRATIONMATTERMOST1 IN / 1 OUTDivide into groups. transform node, function. 1 incoming and 2 outgoing connections.STEP 04Divide into groupsTRANSFORMFUNCTION1 IN / 2 OUTAnnounce groups. integration node, mattermost. 1 incoming and 0 outgoing connections.OUTCOMEAnnounce groupsINTEGRATIONMATTERMOST1 IN / 0 OUTSend calendar invites. Google Calendar node, googleCalendar. 1 incoming and 0 outgoing connections.OUTCOMESend calendar invitesGOOGLE CALENDARGOOGLECALENDAR1 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

Weekly trigger on monday

5 Execution Links

  1. Start

    Weekly trigger on monday

    Integration

  2. Step 2

    Greetings

    Integration

  3. Step 3

    Employees in coffee chat channel

    Integration

  4. Step 4

    Divide into groups

    Transform

  5. Outcome

    Announce groups

    Integration

    Send calendar invites

    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