Skip to Workflow Atlas
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.

Live system map / verified archive

The entire automation, wired and inspectable.

Brand marks identify the operational stack. Focus or select any node to isolate its real incoming and outgoing connections.

11

Nodes

10

Edges

6

Zones

System stack

3 integrations

  • OpenAI
  • Microsoft Outlook
  • Slack
Outlook and Slack AI-Powered Calendar Assistant interactive execution graphStructural view of 11 workflow nodes and 10 visible connections. Focus any node to inspect its connected path. Parameters and credentials are intentionally excluded.On BOT/APP Mention. trigger node, webhook. 0 incoming and 1 outgoing connections.On BOT/APP MentionTRIGGERWEBHOOK0 IN / 1 OUTIs Auth Challenge?. decision node, if. 1 incoming and 2 outgoing connections.Is Auth Challenge?DECISIONIF1 IN / 2 OUTRespond to Challenge. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.Respond to ChallengeTRIGGERRESPONDTOWEBHOOK1 IN / 0 OUTGet Message. transform node, set. 1 incoming and 1 outgoing connections.Get MessageTRANSFORMSET1 IN / 1 OUTOpenAI Chat Model. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.OpenAI Chat ModelOPENAILMCHATOPENAI0 IN / 1 OUTOutlook Calendar Assistant. ai node, agent. 6 incoming and 1 outgoing connections.Outlook Calendar AssistantAIAGENT6 IN / 1 OUTSimple Memory. ai node, memoryBufferWindow. 0 incoming and 1 outgoing connections.Simple MemoryAIMEMORYBUFFERWINDOW0 IN / 1 OUTSearch All Outlook Events. integration node, microsoftOutlookTool. 0 incoming and 1 outgoing connections.Search All Outlook EventsINTEGRATIONMICROSOFTOUTLOOKTOOL0 IN / 1 OUTCreate New Calendar Event. integration node, microsoftOutlookTool. 0 incoming and 1 outgoing connections.Create New Calendar EventINTEGRATIONMICROSOFTOUTLOOKTOOL0 IN / 1 OUTSend Reply. Slack node, slack. 1 incoming and 0 outgoing connections.Send ReplySLACKSLACK1 IN / 0 OUTGet Available Calendars. integration node, microsoftOutlookTool. 0 incoming and 1 outgoing connections.Get Available CalendarsINTEGRATIONMICROSOFTOUTLOOKTOOL0 IN / 1 OUT

Signal inspector

Focus, hover, or select a node to illuminate its real path.

triggeraidecisiontransformintegration
Scroll horizontally to inspect every zone.verified structural metadata · graph 5cc6e1e411519f02Enter or click to lock · Escape to clear

Structured review

Read the workflow as a system, not a node dump.

The archived graph is grouped into operational zones, then checked against the controls needed to adapt the pattern safely. Every count below is derived from the normalized record.

01

Entry signals

2 nodes

Events, schedules, and unconnected roots that can start an execution.

Respond to Challenge

Trigger

On BOT/APP Mention

Trigger

02

Data & operations

4 nodes

Transformations and external-system actions that move the work forward.

Search All Outlook Events

Integration

Create New Calendar Event

Integration

Get Available Calendars

Integration

Get Message

Transform

03

Intelligence & routing

4 nodes

Model calls and control points that interpret, branch, or govern the run.

OpenAI Chat Model

AI reasoning

Simple Memory

AI reasoning

Outlook Calendar Assistant

AI reasoning

Is Auth Challenge?

Decision

04

Terminal actions

1 node

Nodes with no visible outgoing edge: the workflow’s observable outcomes.

Send Reply

Integration

Provenance boundary

Inspectable does not mean redistributable.

This page publishes structural metadata extracted from a local workflow archive. Parameters, credential references, code bodies, and downloadable JSON are excluded. The route can enter indexing only after a graph match and quality gate; source licensing remains a separate promotion gate.

Graph match
exact
Quality score
12 / 14
Raw download
Held
Crawler state
Follow

Adjacent systems

Keep tracing the stack.

Related records are ranked by shared integrations and graph quality.

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.