HTTP and Slack: Status Page Component Watcher Template

This Spojit template polls a vendor status page on a schedule and pings your team in Slack the moment a component you depend on stops being operational.

What It Builds

A Schedule trigger fires every few minutes and a Connector node in Direct mode uses the http connector to fetch the vendor's status page JSON (the standard /api/v2/components.json Statuspage feed, or any equivalent URL). A Condition node checks each component's status, and when one you care about leaves operational, a slack Connector node posts an alert to your incident channel.

The Prompt

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

Build a workflow that runs every 5 minutes, fetches the JSON status feed at https://status.example.com/api/v2/components.json over HTTP, and checks the components named "API" and "Dashboard". If either is not "operational", post a Slack message to #incidents with the component name, its current status, and a link to the status page.

Connectors Used

Schedule trigger - runs the check on a fixed cron interval.
http - reads the vendor status page JSON; Miraxa connects to any status feed via its URL.
slack - posts the alert to your chosen channel.

Customize It

Change the interval (every minute for critical vendors), swap the feed URL and component names for the services you depend on, point the alert at a different channel, and broaden the check to flag any status that is degraded_performance or partial_outage as well as full outages.

Tips

Keep the http Connector node in Direct mode: it is one fixed GET request, so there is no AI cost.
Most status pages expose a public JSON feed with no auth; if yours needs a key, add it as an HTTP header in the node.
Add a second Condition branch to post a "recovered" message when the component returns to operational.