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

Google Calendar Manager

Google Calendar Manager is a 7-node automation blueprint connecting Google Calendar. Inspect its trigger, execution graph, branches, and implementation requirements.

Google 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.

7

Nodes

6

Links

1

Run groups

Connected tools

1 integrations

  • Google Calendar

Canvas controls

Fit wide systems, then zoom into any run group.

Google Calendar Manager execution lanes1 run groups containing 7 workflow nodes and 6 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.MCP_CALENDAR. trigger node, mcpTrigger. 6 incoming and 0 outgoing connections.CORE RUNTIMEMCP_CALENDARTRIGGERMCPTRIGGER6 IN / 0 OUTAVALIABILITY_CALENDAR. Google Calendar node, googleCalendarTool. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1AVALIABILITY_CALENDARGOOGLE CALENDARGOOGLECALENDARTOOL0 IN / 1 OUTGET_ALL_CALENDAR. Google Calendar node, googleCalendarTool. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1GET_ALL_CALENDARGOOGLE CALENDARGOOGLECALENDARTOOL0 IN / 1 OUTDELETE_CALENDAR. Google Calendar node, googleCalendarTool. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1DELETE_CALENDARGOOGLE CALENDARGOOGLECALENDARTOOL0 IN / 1 OUTUPDATE_CALENDAR. Google Calendar node, googleCalendarTool. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1UPDATE_CALENDARGOOGLE CALENDARGOOGLECALENDARTOOL0 IN / 1 OUTGET_CALENDAR. Google Calendar node, googleCalendarTool. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1GET_CALENDARGOOGLE CALENDARGOOGLECALENDARTOOL0 IN / 1 OUTCREATE_CALENDAR. Google Calendar node, googleCalendarTool. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1CREATE_CALENDARGOOGLE CALENDARGOOGLECALENDARTOOL0 IN / 1 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.7 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

MCP_CALENDAR

0 Execution Links6 Support Dependencies

  1. Core Runtime

    MCP_CALENDAR

    Trigger

Attached dependencies

These nodes support the runtime above; they are not additional starts or outcomes.

6 nodes

  • AVALIABILITY_CALENDAR

    Integration dependency

  • GET_ALL_CALENDAR

    Integration dependency

  • DELETE_CALENDAR

    Integration dependency

  • UPDATE_CALENDAR

    Integration dependency

  • GET_CALENDAR

    Integration dependency

  • CREATE_CALENDAR

    Integration dependency

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