HTTP and Slack: Webhook Endpoint Reachability Check Template

A scheduled Spojit workflow that probes your own callback and integration endpoints and alerts Slack the moment one returns an error or times out.

What It Builds

A Schedule trigger fires on a regular cron, then a Connector node in Direct mode uses the http connector to send a probe request to each endpoint you list. A Condition node checks the status code and response time, and any failure posts a message to your slack channel so you catch broken inbound integrations before your partners do.

The Prompt

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

Build a workflow that runs every 5 minutes and sends an HTTP GET request to each of my webhook and callback endpoints. If any endpoint returns a non-2xx status code or takes longer than 5 seconds to respond, post an alert to the #integrations Slack channel with the endpoint URL, the status code, and the response time.

Connectors Used

Schedule trigger - runs the check on a cron interval in your timezone.
http - probes each endpoint and reports the status code and latency.
slack - posts a failure alert to the channel you choose.

Customize It

Change the interval to suit your tolerance, swap the channel name, and edit the list of endpoint URLs in the prompt. You can tighten the timeout threshold, switch the probe to a POST with a sample payload, or have the alert message also include the response body for faster debugging.

Tips

Use Direct mode on the http node so each probe is a fixed, no-AI-cost request.
Point probes at lightweight health paths, not endpoints that create real records.
Add a second slack message on recovery so you know when an endpoint comes back.