Automation library · Alerts and monitoring

Summarize Microsoft 365 outage alerts with OpenAI and Outlook

Started by an event in a connected app, and works across Outlook and Slack. It hands the judgement calls to OpenAI. 6 steps: small enough to read in one sitting and change without fear.

SmallCalls a model: OpenAI

Download free
6 stepsSmall: readable in one sitting
0Branches: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 1Model 1Logic 2Service 2

The steps in the order they run, from what starts it.

  1. 1Check for 365 Service AlertMicrosoft Outlook triggerStarts it
  2. 2Post outage to SlackSlackService
  3. 3Clear email alert from mailboxMicrosoft OutlookService
  4. 4Extract M365 Incident text & linkCodeLogic
  5. 5Summarize service alertOpen AiModel
  6. 6Generate Slack BlockCodeLogic

How it's built

Starts on
An event in a connected app
Steps
6
Size
Small: readable in one sitting
Connects to
Outlook, Slack
Model
OpenAI

Questions

What does it need to run?

An n8n account, plus your own Outlook and Slack accounts, and a key for OpenAI. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an event in a connected app.

Does it use AI?

Yes. It calls OpenAI. Model calls are billed by the provider, not by n8n.

How long does it take to set up?

Not long. At 6 steps it can be read in one sitting and changed without fear.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 6 steps before you point it at anything that matters.