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

Outlook and Slack AI-Powered Calendar Assistant

Outlook and Slack AI-Powered Calendar Assistant is a 11-node automation blueprint connecting OpenAI, Microsoft Outlook, Slack. Inspect its trigger, execution graph, branches, and implementation requirements.

OpenAIMicrosoft OutlookSlack

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.

11

Nodes

10

Links

1

Run groups

Connected tools

3 integrations

  • OpenAI
  • Microsoft Outlook
  • Slack

Canvas controls

Fit wide systems, then zoom into any run group.

Outlook and Slack AI-Powered Calendar Assistant execution lanes1 run groups containing 11 workflow nodes and 10 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.On BOT/APP Mention. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTOn BOT/APP MentionTRIGGERWEBHOOK0 IN / 1 OUTIs Auth Challenge?. decision node, if. 1 incoming and 2 outgoing connections.STEP 02Is Auth Challenge?DECISIONIF1 IN / 2 OUTRespond to Challenge. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.STEP 03Respond to ChallengeTRIGGERRESPONDTOWEBHOOK1 IN / 0 OUTGet Message. transform node, set. 1 incoming and 1 outgoing connections.STEP 03Get MessageTRANSFORMSET1 IN / 1 OUTOutlook Calendar Assistant. ai node, agent. 6 incoming and 1 outgoing connections.STEP 04Outlook Calendar AssistantAIAGENT6 IN / 1 OUTSend Reply. Slack node, slack. 1 incoming and 0 outgoing connections.OUTCOMESend ReplySLACKSLACK1 IN / 0 OUTOpenAI Chat Model. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI Chat ModelOPENAILMCHATOPENAI0 IN / 1 OUTSimple Memory. ai node, memoryBufferWindow. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Simple MemoryAIMEMORYBUFFERWINDOW0 IN / 1 OUTSearch All Outlook Events. integration node, microsoftOutlookTool. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Search All Outlook EventsINTEGRATIONMICROSOFTOUTLOOKTOOL0 IN / 1 OUTCreate New Calendar Event. integration node, microsoftOutlookTool. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Create New Calendar EventINTEGRATIONMICROSOFTOUTLOOKTOOL0 IN / 1 OUTGet Available Calendars. integration node, microsoftOutlookTool. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Get Available CalendarsINTEGRATIONMICROSOFTOUTLOOKTOOL0 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.11 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

Respond to Challenge

5 Execution Links5 Support Dependencies

  1. Start

    On BOT/APP Mention

    Trigger

  2. Step 2

    Is Auth Challenge?

    Decision

  3. Step 3

    Respond to Challenge

    Trigger

    Get Message

    Transform

  4. Step 4

    Outlook Calendar Assistant

    AI reasoning

  5. Outcome

    Send Reply

    Integration

Attached dependencies

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

5 nodes

  • OpenAI Chat Model

    AI reasoning dependency

  • Simple Memory

    AI reasoning dependency

  • Search All Outlook Events

    Integration dependency

  • Create New Calendar Event

    Integration dependency

  • Get Available Calendars

    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