Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationAI systemIntermediate

Automated Meeting Management Workflow

Automated Meeting Management Workflow is a 19-node automation blueprint connecting OpenAI, Google Drive, Google Calendar. Inspect its trigger, execution graph, branches, and implementation requirements.

OpenAIGoogle DriveGoogle 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.

19

Nodes

17

Links

2

Run groups

Connected tools

3 integrations

  • OpenAI
  • Google Drive
  • Google Calendar

Canvas controls

Fit wide systems, then zoom into any run group.

Automated Meeting Management Workflow execution lanes2 run groups containing 19 workflow nodes and 17 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.When clicking "Test workflow". trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTWhen clicking "Test workf…TRIGGERMANUALTRIGGER0 IN / 1 OUTGet Calendar Event. Google Calendar node, googleCalendar. 1 incoming and 1 outgoing connections.STEP 02Get Calendar EventGOOGLE CALENDARGOOGLECALENDAR1 IN / 1 OUTGet Meeting ConferenceRecords. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 03Get Meeting ConferenceRec…INTEGRATIONHTTPREQUEST1 IN / 1 OUTGet Meeting Transcript Location. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 04Get Meeting Transcript Lo…INTEGRATIONHTTPREQUEST1 IN / 1 OUTGet Transcript File. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 05Get Transcript FileGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTPDF Loader. integration node, extractFromFile. 1 incoming and 1 outgoing connections.STEP 06PDF LoaderINTEGRATIONEXTRACTFROMFILE1 IN / 1 OUTAI Agent. ai node, agent. 4 incoming and 0 outgoing connections.OUTCOMEAI AgentAIAGENT4 IN / 0 OUTOpenAI Chat Model1. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI Chat Model1OPENAILMCHATOPENAI0 IN / 1 OUTStructured Output Parser. ai node, outputParserStructured. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Structured Output ParserAIOUTPUTPARSERSTRUCTURED0 IN / 1 OUTSchedule Meeting. ai node, toolWorkflow. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Schedule MeetingAITOOLWORKFLOW0 IN / 1 OUTExecute Workflow Trigger. trigger node, executeWorkflowTrigger. 0 incoming and 1 outgoing connections.STARTExecute Workflow TriggerTRIGGEREXECUTEWORKFLOWTRIGGER0 IN / 1 OUTEdit Fields. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Edit FieldsTRANSFORMSET1 IN / 1 OUTActions Router. decision node, switch. 1 incoming and 2 outgoing connections.STEP 03Actions RouterDECISIONSWITCH1 IN / 2 OUTCreate Calendar Event1. Google Calendar node, googleCalendar. 1 incoming and 1 outgoing connections.STEP 04Create Calendar Event1GOOGLE CALENDARGOOGLECALENDAR1 IN / 1 OUTFallback Response. transform node, set. 1 incoming and 0 outgoing connections.STEP 04Fallback ResponseTRANSFORMSET1 IN / 0 OUTGet Attendees. transform node, set. 1 incoming and 1 outgoing connections.STEP 05Get AttendeesTRANSFORMSET1 IN / 1 OUTAttendees List. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 06Attendees ListTRANSFORMSPLITOUT1 IN / 1 OUTAdd Attendee to Invite. Google Calendar node, googleCalendar. 1 incoming and 1 outgoing connections.STEP 07Add Attendee to InviteGOOGLE CALENDARGOOGLECALENDAR1 IN / 1 OUTResponse. transform node, set. 1 incoming and 0 outgoing connections.OUTCOMEResponseTRANSFORMSET1 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.19 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

When clicking "Test workflow"

6 Execution Links3 Support Dependencies

  1. Start

    When clicking "Test workflow"

    Trigger

  2. Step 2

    Get Calendar Event

    Integration

  3. Step 3

    Get Meeting ConferenceRecords

    Integration

  4. Step 4

    Get Meeting Transcript Location

    Integration

  5. Step 5

    Get Transcript File

    Integration

  6. Step 6

    PDF Loader

    Integration

  7. Outcome

    AI Agent

    AI reasoning

Attached dependencies

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

3 nodes

  • OpenAI Chat Model1

    AI reasoning dependency

  • Structured Output Parser

    AI reasoning dependency

  • Schedule Meeting

    AI reasoning dependency

02

Run Group

Execute Workflow Trigger

8 Execution Links

  1. Start

    Execute Workflow Trigger

    Trigger

  2. Step 2

    Edit Fields

    Transform

  3. Step 3

    Actions Router

    Decision

  4. Step 4

    Create Calendar Event1

    Integration

    Fallback Response

    Transform

  5. Step 5

    Get Attendees

    Transform

  6. Step 6

    Attendees List

    Transform

  7. Step 7

    Add Attendee to Invite

    Integration

  8. Outcome

    Response

    Transform

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