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

Automated Meeting and Email Workflow

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

Google CalendarGmailOpenAI

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.

16

Nodes

16

Links

1

Run groups

Connected tools

3 integrations

  • Google Calendar
  • Gmail
  • OpenAI

Canvas controls

Fit wide systems, then zoom into any run group.

Automated Meeting and Email Workflow execution lanes1 run groups containing 16 workflow nodes and 16 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.Schedule Trigger. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.STARTSchedule TriggerTRIGGERSCHEDULETRIGGER0 IN / 1 OUTGet Past Events. Google Calendar node, googleCalendar. 1 incoming and 1 outgoing connections.STEP 02Get Past EventsGOOGLE CALENDARGOOGLECALENDAR1 IN / 1 OUTMark as Seen. integration node, removeDuplicates. 1 incoming and 1 outgoing connections.STEP 03Mark as SeenINTEGRATIONREMOVEDUPLICATES1 IN / 1 OUTLoop Over Items. integration node, splitInBatches. 2 incoming and 2 outgoing connections.STEP 04Loop Over ItemsINTEGRATIONSPLITINBATCHES2 IN / 2 OUTOnly Follow Ups. decision node, filter. 1 incoming and 1 outgoing connections.STEP 05Only Follow UpsDECISIONFILTER1 IN / 1 OUTGet Emails Since. Gmail node, gmail. 1 incoming and 1 outgoing connections.STEP 06Get Emails SinceGMAILGMAIL1 IN / 1 OUTFlag to Follow Up. transform node, set. 1 incoming and 1 outgoing connections.STEP 07Flag to Follow UpTRANSFORMSET1 IN / 1 OUTMeeting Availability Agent. ai node, agent. 4 incoming and 1 outgoing connections.STEP 08Meeting Availability AgentAIAGENT4 IN / 1 OUTGenerate Message. transform node, set. 1 incoming and 1 outgoing connections.STEP 09Generate MessageTRANSFORMSET1 IN / 1 OUTSend for Human Approval. Gmail node, gmail. 1 incoming and 1 outgoing connections.STEP 10Send for Human ApprovalGMAILGMAIL1 IN / 1 OUTMeeting Booking Agent. ai node, agent. 3 incoming and 0 outgoing connections.OUTCOMEMeeting Booking AgentAIAGENT3 IN / 0 OUTModel. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1ModelOPENAILMCHATOPENAI0 IN / 1 OUTAvailability. Google Calendar node, googleCalendarTool. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1AvailabilityGOOGLE CALENDARGOOGLECALENDARTOOL0 IN / 1 OUTOutput. ai node, outputParserStructured. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OutputAIOUTPUTPARSERSTRUCTURED0 IN / 1 OUTModel1. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Model1OPENAILMCHATOPENAI0 IN / 1 OUTMeetings. Google Calendar node, googleCalendarTool. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1MeetingsGOOGLE 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.16 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

Schedule Trigger

11 Execution Links5 Support Dependencies

  1. Start

    Schedule Trigger

    Trigger

  2. Step 2

    Get Past Events

    Integration

  3. Step 3

    Mark as Seen

    Integration

  4. Step 4

    Loop Over Items

    Integration

  5. Step 5

    Only Follow Ups

    Decision

  6. Step 6

    Get Emails Since

    Integration

  7. Step 7

    Flag to Follow Up

    Transform

  8. Step 8

    Meeting Availability Agent

    AI reasoning

  9. Step 9

    Generate Message

    Transform

  10. Step 10

    Send for Human Approval

    Integration

  11. Outcome

    Meeting Booking Agent

    AI reasoning

Attached dependencies

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

5 nodes

  • Model

    AI reasoning dependency

  • Availability

    Integration dependency

  • Output

    AI reasoning dependency

  • Model1

    AI reasoning dependency

  • Meetings

    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