Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Index cohort 01Browse archive
Event-Driven AutomationAI systemIntermediate

Automated Meeting Summary with AI

Automated Meeting Summary with AI is a 5-node automation blueprint connecting Google Calendar, Slack, Langchain AI. Inspect its trigger, execution graph, branches, and implementation requirements.

Google CalendarSlackLangchain AIGoogle Gemini

System map / archived topology

See the whole system without the collisions.

Archived canvas positions are normalized into readable zones. Every visible connector still represents an edge from the source graph.

5

Nodes

4

Edges

4

Zones

Automated Meeting Summary with AI execution graphStructural view of 5 workflow nodes and 4 visible connections. Parameters and credentials are intentionally excluded.ZONE 01Entry1 NODEZONE 02Intelligence2 NODESZONE 03Operations1 NODEZONE 04Operations1 NODESchedule TriggerTRIGGER / SCHEDULETRIGGER04Calendar AI AgentAI / AGENT03Google Gemini Chat ModelAI / LMCHATGOOGLEGEMI05Google Calendar - Get …INTEGRATION / GOOGLECALENDARTO02Send response back to …INTEGRATION / SLACK01
triggeraidecisiontransformintegration
Scroll horizontally to inspect every zone.structural metadata only · graph 0a3c0bcabf5e64d9

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.

Schedule Trigger

Trigger

02

Data & operations

1 node

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

Google Calendar - Get Events

Integration

03

Intelligence & routing

2 nodes

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

Calendar AI Agent

AI reasoning

Google Gemini Chat Model

AI reasoning

04

Terminal actions

1 node

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

Send response back to slack channel

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
14 / 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