Equipment‑issue alerting workflow that watches issue submissions, normalizes and formats message content, and routes critical, medium, and low‑urgency incidents to separate Discord channels, with module‑level email error capture for each branch.
Make · workflow canvasproduction build
Context
Studio operations teams needed a fast way to escalate equipment issues by severity instead of letting all alerts appear the same, while keeping a clear audit trail if any part of the notification pipeline failed.
Approach
Built a single Make.com scenario that watches issue‑submission entries, normalizes the data, formats a Discord‑ready message, and branches by urgency into critical, medium, and low paths, each of which sends a tailored HTTP alert to Discord; dedicated error‑capture email modules sit alongside the intake/formatting and each Discord branch so failures are traceable to the exact step.
Architecture
Watch Issue Submissions
Normalize Submission Data
Format Message Contents
Format Discord Message Content
Urgency Level Branch
Critical Urgency: Post Critical Message to Discord
Medium Urgency
Post Medium Message to Discord
Low Urgency
Post Standard Message to Discord
Capture Module Error attached to each stage to send email on failure
