Who Is This For?
This recipe is for solo developers, indie hackers, and small SaaS operators who manage infrastructure without a dedicated DevOps team. You're juggling code, customers, and cron jobs—yet still want to sleep at night knowing your servers are up and your app is performing.
What You Get
A fully automated monitoring dashboard that:
- Tracks server uptime via HTTP checks
- Logs cron job execution status
- Pulls application performance metrics (e.g., response time)
- Sends alerts if thresholds are breached
- Stores all data in Google Sheets for historical review
All built without writing a single line of code.
Why It Matters
Solo developers often lack the time or budget for enterprise monitoring tools. This recipe gives them a lean, low-cost alternative that scales with their business. It’s ideal for bootstrappers managing multiple microservices or side projects on a shoestring budget.
🔗 Related: Cron Job Failure Cost Calculator, Downtime Financial Impact Calculator, DevOps Risk Calculator
How It Works
Trigger
HTTP Request via Webhook — Your server sends a heartbeat signal every 5 minutes.
Steps
- Catch Webhook Data — Capture server metrics like status code, response time, and cron job status.
- Parse JSON Payload — Extract uptime status and performance metrics.
- Conditional Logic — If server is down or response time > 2s, proceed to alerting.
- Send Alert via Email or Slack — Notify you of issues immediately.
- Log Metrics to Google Sheets — Store all data for historical tracking.
- Optional: Push to Grafana or Airtable — For advanced users wanting richer dashboards.
Outcome
You get real-time visibility into your system health, with alerts that prevent costly downtime and logs that help diagnose issues later.
Step-by-Step Setup Guide
Step 1: Create a New Scenario in Make.com
- Go to Make.com and click Create New Scenario.
- Choose Webhooks as your trigger → Select Custom Webhook.
- Copy the webhook URL and add it to your server’s cron job or health check script.
Step 2: Add Webhook Module
- In Make, add a Webhooks > Custom Webhook module.
- Name it “Server Health Webhook”.
- Set up your server to POST JSON like this:
{
"status": "up",
"response_time_ms": 180,
"cron_job_status": "success",
"timestamp": "2025-04-05T10:00:00Z"
}
Step 3: Add a Filter
Add a Filter module to only proceed if:
status≠up- OR
response_time_ms> 2000
Step 4: Send Alert via Email or Slack
Add an Email or Slack module to notify you when issues occur.
Step 5: Log to Google Sheets
Add a Google Sheets > Create Row module to log:
- Status
- Response Time
- Cron Job Status
- Timestamp
Step 6: Test and Schedule
- Run a test from your server.
- Confirm alerts fire and data logs correctly.
- Set up a recurring check every 5–15 minutes via cron.
Troubleshooting FAQ
Q: My server isn’t triggering the webhook
A: Double-check your POST URL and ensure your server is sending valid JSON. Use tools like curl or Postman to simulate a POST.
Q: Google Sheets isn’t logging data
A: Confirm your Google account is connected in Make and the sheet ID is correct. Also check column headers match the data being sent.
Q: Alerts aren’t firing
A: Ensure your filter logic is correct and that your email or Slack app is properly authenticated in Make.
Q: Can I use this with AWS Lambda or Vercel?
A: Yes. Just add a scheduled function that pings your Make webhook with health data.
Monetisation Next Step
Want to sell this as a service or turn it into a SaaS monitoring tool for indie makers?
Or, if you’re reselling digital tools:
No-code doesn’t mean no power. With this recipe, you’re not just monitoring—you’re building the foundation for a resilient, scalable digital business.