Mailhook and Slack: Vendor Outage Notification Relay Template

Forward vendor outage emails to a Spojit mailhook, have an Agent-mode Connector node summarize them, and relay a clean alert to your on-call Slack channel within seconds.

What It Builds

This template starts with a Mailhook trigger that gives the workflow its own dedicated email address. When a vendor status email lands there, an Agent-mode Connector node reads the raw message and produces a short, structured summary (affected service, severity, and impact). A Slack Connector node then posts that summary to your on-call channel, so your team sees the essentials without digging through the original email.

The Prompt

Paste this into Miraxa and it builds the workflow, connecting the tools for you:

Build a workflow with a mailhook trigger so vendor outage emails can be forwarded to it. Use an AI step to summarize each email into the affected service, severity, and a one-line impact, then post that summary to my #on-call Slack channel including the vendor name and the time received.

Connectors Used

Mailhook trigger - the workflow's dedicated address that fires a run on each forwarded outage email.
Agent-mode Connector node - summarizes the email body into affected service, severity, and impact.
Slack - posts the relayed alert to your chosen channel.

Customize It

Change #on-call to your incident channel, adjust which fields the summary should include, or add a line in the prompt to only relay emails whose severity is high or critical.

Tips

Set up a forwarding rule from your shared inbox so vendor alerts reach the mailhook address automatically.
Use a Response Schema on the Agent-mode node to keep the summary fields consistent every run.
Connect the Slack node with a scope that can post to your on-call channel.