Monitor your APIs. Alert on failure. Fix itself.

Check your endpoints on a schedule. If any return errors or slow responses, send a Slack alert with full context. The monitoring workflow self-heals if the alert API changes format.

You find out your API is down when a customer tells you.

Existing monitors are either too simple (just ping, no context) or too complex (full observability stacks with YAML config and dashboards to maintain). What you want is: check these endpoints, if anything is wrong, tell me why and where.

Write it once. Runs every 15 minutes.

api-monitor.mdcron: */15 * * * *
# API Health Monitor
 
### 1. Check authentication endpoint
GET https://api.example.com/health — expect 200. No dependencies.
 
### 2. Check payments endpoint
GET https://api.example.com/payments/ping — expect 200. Runs in parallel with step 1.
 
### 3. Evaluate results
If either step 1 or step 2 returned a non-200 status or took more than 2 seconds, mark as degraded. Depends on steps 1 AND 2.
 
### 4. Alert on degradation
If step 3 found issues, post a Slack alert to #ops-alerts with the endpoint name, status code, and response time. Only runs if degraded.

More than a ping check.

⚡
Parallel checks, fast results
Multiple endpoint checks run simultaneously. No waiting for one to finish before starting the next.
🔁
Self-healing monitoring
If the Slack API changes its payload format, AI recovery corrects the request automatically. Your monitor stays up even when dependencies shift.
📋
Full context in the alert
The alert includes the endpoint name, HTTP status, response time, and a summary of what was checked — not just "something is down."

Built with 3 step types and a cron trigger.

cron trigger — fires every 15 minutes
http_request ×N — parallel checks of each endpoint
conditional — evaluates status codes and response times
connector — sends Slack alert with full context

Your APIs monitored
in under 5 minutes.

Write the workflow in plain English. CFFBRW compiles and schedules it. No credit card. No config files.