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

Automated Email to Calendar Scheduler

Automated Email to Calendar Scheduler is a 17-node automation blueprint connecting Gmail, Google Calendar, OpenAI. Inspect its trigger, execution graph, branches, and implementation requirements.

GmailGoogle CalendarOpenAI

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.

17

Nodes

15

Edges

5

Zones

Automated Email to Calendar Scheduler execution graphStructural view of 17 workflow nodes and 15 visible connections. Parameters and credentials are intentionally excluded.ZONE 01Entry5 NODESZONE 02Intelligence2 NODESZONE 03Control2 NODESZONE 04Intelligence4 NODESZONE 05Operations4 NODESGmail TriggerTRIGGER / GMAILTRIGGER01Classify appointmentAI / CHAINLLM12Chat OpenAIAI / LMCHATOPENAI02Execute Workflow TriggerTRIGGER / EXECUTEWORKFLOWT06Google CalendarINTEGRATION / GOOGLECALENDAR05Structured Output ParserAI / OUTPUTPARSERSTRU13Filter only confirmed …DECISION / FILTER10Is appointment requestDECISION / IF11Extract start, end and…TRANSFORM / SET09AgentAI / AGENT17Chat OpenAI1AI / LMCHATOPENAI04SortTRANSFORM / ITEMLISTS14Format responseTRANSFORM / ITEMLISTS07Send ReplyINTEGRATION / GMAIL16Mark as readINTEGRATION / GMAIL15Workflow ToolAI / TOOLWORKFLOW03Stringify ResponseTRANSFORM / SET08
triggeraidecisiontransformintegration
Scroll horizontally to inspect every zone.structural metadata only · graph a3d17d58574c5b8d

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

2 nodes

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

Gmail Trigger

Trigger

Execute Workflow Trigger

Trigger

02

Data & operations

4 nodes

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

Google Calendar

Integration

Format response

Transform

Extract start, end and name

Transform

Sort

Transform

03

Intelligence & routing

8 nodes

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

Chat OpenAI

AI reasoning

Workflow Tool

AI reasoning

Chat OpenAI1

AI reasoning

Filter only confirmed and with set time

Decision

Is appointment request

Decision

Classify appointment

AI reasoning

+ 2 more in system map
04

Terminal actions

3 nodes

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

Stringify Response

Transform

Mark as read

Integration

Send Reply

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