Sharing some common work to help others out.
If you spot something, feel free to use Issues to raise suggestions, changes, recommdations or issues.
List of Workflows
Link to workflow published on N8N marketplace
Intended for a dedicated Slack channel for outage notifications, and to be readable on mobile or desktop.
This is for:
- IT Administrators & small MSPs looking to streamline M365 alerts from one or multiple mailboxes into a single or specific Slack channels
- IT Admins who prefer ChatOps over management-by-email
- Scans for M365 outage alert emails
- Checks if it impacts your users in specific countries (list manually defined), if the alert calls it out, and adjusts the summary accordingly.
- Uses Slack Blocks and provides a button to the M365 Incident or to admin.microsoft.com, if no link provided
- Cleans up by deleting the original alert email, after successful send to Slack
- Uses OpenAI's 4o-mini model, can be easily replaced with locally hosted Ollama or alternative service, with the same prompts.
Credentials
- Outlook: Create an Outlook credential (OAuth2.0) to point to the mailbox (regular or shared) where M365 service alerts will be received
- Slack: Create a Slack bot credential with access to the slack channel you want updates posted to
- OpenAI: Create a OpenAI credential that has access to the GPT-4O-MINI model. Recommend you use projects in OpenAI so that you may set a per-project-budget and not impact other projects.
Expect this to consume no more than 1-2 cents per month on average. Recommend configuring a separate project so you may set a per-project budget in OpenAI. Review this OpenAI documentation for more info on managing Projects in the API portal.
Don't like Slack? Can easily replace with ntfy.sh, Teams, Discord, or whatever platform you prefer.
Download & Setup
- Download & import the workflow
- Add your credentials (OpenAI, Slack bot connection)
- Modify the system prompt to call out the countries your users reside in
ie. “- Assume the organization has users primarily in the U.S. and Australia. If those regions are affected, state: “Your users may have been affected.” Otherwise, add: “No impact expected for your user base.”” <- swap U.S. & Australia for desired countries
Sample Slack Output
Workflow diagram
Link to workflow published on N8N marketplace
Automatically backs up your workflows to Github and generates documentation in a Notion database.
- Weekly run, uses the "internal-infra" tag to look for new or recently modified workflows
- Uses a Notion database page to hold the workflow summary, last updated date, and a link to the workflow
- Uses OpenAI's 4o-mini to generate a summarization of what the workflow does
- Stores a backup of the workflow in GitHub (recommend a private repo)
- Sends notification to Slack channel for new or updated workflows
Credentials
- Notion: Create a database with the following columns. Column type is specified in [type].
- Workflow Name [text]
- isActive (dev) [checkbox]
- Error workflow setup [checkbox]
- AI Summary [text]
- Record last update [date/time]
- URL (dev) [text/url]
- Workflow created at [date/time]
- Workflow updated at [date/time]
- GitHub: Create a private repo for your workflows to be exported into
- Slack: Create a Slack bot credential with access to the slack channel you want updates posted to
- OpenAI: Create a OpenAI credential that has access to the GPT-4O-MINI model. Recommend you use projects in OpenAI so that you may set a per-project-budget and not impact other projects.
Expect this to consume no more than 1-2 cents per month on average. Recommend configuring a separate project so you may set a per-project budget in OpenAI. Review this OpenAI documentation for more info on managing Projects in the API portal.
Download & Setup
- Download & import the workflow
- Add your credentials (N8N, Notion, Slack, GitHub)
- Insert your N8N hostname in the Set fields block
- Insert your Notion database in the Get notion page with workflow id block
- Change the "internal-infra" tag if desired
Sample output in Notion
Workflow diagram
