Skip to Workflow Atlas
Event-Driven AutomationAI systemIntermediate

AI-Powered Appointment Scheduler

AI-Powered Appointment Scheduler is a 17-node automation blueprint connecting OpenAI, Microsoft Outlook. Inspect its trigger, execution graph, branches, and implementation requirements.

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.

17

Nodes

15

Links

2

Run groups

Connected tools

2 integrations

  • OpenAI
  • Microsoft Outlook

Canvas controls

Fit wide systems, then zoom into any run group.

AI-Powered Appointment Scheduler execution lanes2 run groups containing 17 workflow nodes and 15 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.Execute Workflow Trigger. trigger node, executeWorkflowTrigger. 0 incoming and 1 outgoing connections.STARTExecute Workflow TriggerTRIGGEREXECUTEWORKFLOWTRIGGER0 IN / 1 OUTSwitch. decision node, switch. 1 incoming and 2 outgoing connections.STEP 02SwitchDECISIONSWITCH1 IN / 2 OUTGet Events. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 03Get EventsINTEGRATIONHTTPREQUEST1 IN / 1 OUTSend Message1. integration node, microsoftOutlook. 1 incoming and 1 outgoing connections.STEP 03Send Message1INTEGRATIONMICROSOFTOUTLOOK1 IN / 1 OUTfreeTimeSlots. transform node, code. 1 incoming and 1 outgoing connections.STEP 04freeTimeSlotsTRANSFORMCODE1 IN / 1 OUTvarMessageResponse. transform node, set. 1 incoming and 0 outgoing connections.STEP 04varMessageResponseTRANSFORMSET1 IN / 0 OUTvarResponse. transform node, set. 1 incoming and 0 outgoing connections.OUTCOMEvarResponseTRANSFORMSET1 IN / 0 OUTChat Trigger. trigger node, chatTrigger. 0 incoming and 1 outgoing connections.STARTChat TriggerTRIGGERCHATTRIGGER0 IN / 1 OUTIf. decision node, if. 1 incoming and 2 outgoing connections.STEP 02IfDECISIONIF1 IN / 2 OUTAI Agent. ai node, agent. 6 incoming and 1 outgoing connections.STEP 03AI AgentAIAGENT6 IN / 1 OUTRespond With Initial Message. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.STEP 03Respond With Initial Mess…TRIGGERRESPONDTOWEBHOOK1 IN / 0 OUTRespond to Webhook. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.OUTCOMERespond to WebhookTRIGGERRESPONDTOWEBHOOK1 IN / 0 OUTOpenAI Chat Model. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI Chat ModelOPENAILMCHATOPENAI0 IN / 1 OUTMake Appointment. ai node, toolHttpRequest. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Make AppointmentAITOOLHTTPREQUEST0 IN / 1 OUTWindow Buffer Memory. ai node, memoryBufferWindow. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Window Buffer MemoryAIMEMORYBUFFERWINDOW0 IN / 1 OUTSend Message. ai node, toolWorkflow. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Send MessageAITOOLWORKFLOW0 IN / 1 OUTGet Availability. ai node, toolWorkflow. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Get AvailabilityAITOOLWORKFLOW0 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.17 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

Execute Workflow Trigger

6 Execution Links
  1. Start

    Execute Workflow Trigger

    Trigger

  2. Step 2

    Switch

    Decision

  3. Step 3

    Get Events

    Integration

    Send Message1

    Integration

  4. Step 4

    freeTimeSlots

    Transform

    varMessageResponse

    Transform

  5. Outcome

    varResponse

    Transform

02

Run Group

Respond to Webhook

4 Execution Links5 Support Dependencies
  1. Start

    Chat Trigger

    Trigger

  2. Step 2

    If

    Decision

  3. Step 3

    AI Agent

    AI reasoning

    Respond With Initial Message

    Trigger

  4. Outcome

    Respond to Webhook

    Trigger

Attached dependencies

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

5 nodes
  • OpenAI Chat Model

    AI reasoning dependency

  • Make Appointment

    AI reasoning dependency

  • Window Buffer Memory

    AI reasoning dependency

  • Send Message

    AI reasoning dependency

  • Get Availability

    AI reasoning 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.