Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Index held / follow enabledBrowse archive
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

Live system map / verified archive

The entire automation, wired and inspectable.

Brand marks identify the operational stack. Focus or select any node to isolate its real incoming and outgoing connections.

6

Nodes

5

Edges

5

Zones

System stack

2 integrations

  • Mattermost
  • Google Calendar
Weekly Coffee Chat Coordinator interactive execution graphStructural view of 6 workflow nodes and 5 visible connections. Focus any node to inspect its connected path. Parameters and credentials are intentionally excluded.Weekly trigger on monday. integration node, cron. 0 incoming and 1 outgoing connections.Weekly trigger on mondayINTEGRATIONCRON0 IN / 1 OUTGreetings. integration node, mattermost. 1 incoming and 1 outgoing connections.GreetingsINTEGRATIONMATTERMOST1 IN / 1 OUTEmployees in coffee chat channel. integration node, mattermost. 1 incoming and 1 outgoing connections.Employees in coffee chat …INTEGRATIONMATTERMOST1 IN / 1 OUTDivide into groups. transform node, function. 1 incoming and 2 outgoing connections.Divide into groupsTRANSFORMFUNCTION1 IN / 2 OUTAnnounce groups. integration node, mattermost. 1 incoming and 0 outgoing connections.Announce groupsINTEGRATIONMATTERMOST1 IN / 0 OUTSend calendar invites. Google Calendar node, googleCalendar. 1 incoming and 0 outgoing connections.Send calendar invitesGOOGLE CALENDARGOOGLECALENDAR1 IN / 0 OUT

Signal inspector

Focus, hover, or select a node to illuminate its real path.

triggeraidecisiontransformintegration
Scroll horizontally to inspect every zone.verified structural metadata · graph 099a6274a8a67886Enter or click to lock · Escape to clear

Structured review

Read the workflow as a system, not a node dump.

The archived graph is grouped into operational zones, then checked against the controls needed to adapt the pattern safely. Every count below is derived from the normalized record.

01

Entry signals

1 node

Events, schedules, and unconnected roots that can start an execution.

Weekly trigger on monday

Integration

02

Data & operations

3 nodes

Transformations and external-system actions that move the work forward.

Divide into groups

Transform

Greetings

Integration

Employees in coffee chat channel

Integration

03

Intelligence & routing

0 nodes

Model calls and control points that interpret, branch, or govern the run.

No nodes observed in this zone
04

Terminal actions

2 nodes

Nodes with no visible outgoing edge: the workflow’s observable outcomes.

Announce groups

Integration

Send calendar invites

Integration

Provenance boundary

Inspectable does not mean redistributable.

This page publishes structural metadata extracted from a local workflow archive. Parameters, credential references, code bodies, and downloadable JSON are excluded. The route can enter indexing only after a graph match and quality gate; source licensing remains a separate promotion gate.

Graph match
exact
Quality score
13 / 14
Raw download
Held
Crawler state
Follow

Adjacent systems

Keep tracing the stack.

Related records are ranked by shared integrations and graph quality.

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