HTTP and Slack: API Latency Threshold Alert Template

A ready-to-build Spojit template that checks an API endpoint every five minutes and pings your on-call Slack channel the moment response time crosses a threshold you set.

What It Builds

A Schedule trigger fires every five minutes. A Connector node in Direct mode uses the http connector to call your service endpoint and capture the response time. A Condition node compares that latency against your threshold, and when it is exceeded it routes to a Connector node that posts a formatted alert into your Slack on-call channel. Healthy checks simply end the run quietly.

The Prompt

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

Build a workflow that runs every 5 minutes, sends an HTTP GET request to https://api.example.com/health, measures the response time in milliseconds, and if it is greater than 800 ms posts a message to the #on-call Slack channel with the endpoint URL, the measured latency, and the timestamp.

Connectors Used

  • Schedule trigger - runs the check on a 5-minute cron.
  • http - calls the endpoint and returns the response so latency can be measured.
  • slack - posts the threshold-breach alert to your on-call channel.

Customize It

Edit the prompt before building to fit your service: change the endpoint URL, swap the 5 minute interval, raise or lower the 800 ms threshold, and point the alert at a different Slack channel. You can also add the HTTP status code or a service name to the message text without needing a second prompt.

Tips

  • Keep the API call on a Connector node in Direct mode so the check costs nothing in AI usage and runs fast.
  • The Slack connection needs chat:write scope and access to the target channel.
  • For a heads-up before things break, set the threshold below your hard SLA so the alert lands while there is still time to act.

Related

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.