Uptime Monitoring With Scheduled Triggers
Every 5 minutes, checks a list of URLs in Google Sheets for uptime and alerts via Slack and email if any site goes down.
developers and engineersops and IT teams
What it does
You get instant alerts on your Slack channel or email whenever a website listed in Google Sheets goes down. Every five minutes, the tool automatically checks your sites, logs their status back to the sheet, and notifies you immediately if any go offline so you can act fast.
Step by step
- Configure a scheduled cloud function or workflow to execute at fixed intervals.
- Implement an HTTP GET request to each URL in the Google Sheet and parse the status code.
- Use conditional logic to write 'UP' or 'DOWN' along with a timestamp back to the specific row in Google Sheets.
- Trigger separate API calls to Slack and Gmail endpoints when the status code indicates failure.
Where the LLM does the work
- Generate robust error handling code for transient network failures during HTTP checks.
- Draft clear and concise notification messages for both Slack channels and email bodies.
- Design the logic to handle edge cases like SSL certificate errors versus simple timeouts.
Watch out for
Slack API tokens can expire or lose permissions so verify webhook URLs and scopes regularly.
Google Sheets API quotas are strict so batch writes where possible to avoid hitting daily limits.
Tools that fit
HTTP Request API Checking website availability status
The agent brief
Everything your agent needs, including the gotchas. Copy it and go.
You are helping me build the following AI agent workflow. ## Goal Uptime Monitoring With Scheduled Triggers: Every 5 minutes, checks a list of URLs in Google Sheets for uptime and alerts via Slack and email if any site goes down. ## Specification - What it does: You get instant alerts on your Slack channel or email whenever a website listed in Google Sheets goes down. Every five minutes, the tool automatically checks your sites, logs their status back to the sheet, and notifies you immediately if any go offline so you can act fast. - Trigger: On a schedule (Scheduled · every 5 minutes) - Autonomy: Fully hands-off - Expected setup effort: under an hour - Tools/services involved: - Google Sheets: Storing website URLs and state logs - HTTP Request: Checking website availability status - Slack: Sending alerts for down websites - Gmail: Sending email alerts for down websites ## Known pitfalls, handle each one explicitly in your implementation 1. Slack API tokens can expire or lose permissions so verify webhook URLs and scopes regularly. 2. Google Sheets API quotas are strict so batch writes where possible to avoid hitting daily limits. ## Reference implementation https://n8n.io/workflows/2327 (workflow template) Fetch and inspect this before building. If it matches my stack, adapt it; if not, rebuild the pattern with my tools. ## Process requirements 1. Before building: ask me which of the listed tools I actually use and what my platform is (n8n / Make / code / other). Do not assume. 2. Adapt the pattern to my answers; do not force the reference stack. 3. Address every pitfall above; tell me how you handled each. 4. Provide a test plan I can run before letting this touch real data. 5. Ask before any step that sends messages, modifies data, or spends money. Source: https://usecasesforagents.com/use-case/uptime-monitoring-with-scheduled-triggers/ via usecasesforagents.com
Frequently asked questions
Can I use a different Spreadsheet than Google Sheets?
Yes. Google Sheets is only the example spreadsheet in this recipe. The same flow works with Airtable, Baserow and Excel. Swap the spreadsheet connection and keep the rest of the setup as written.
Want this running in your business?
This is what I do. I design and build AI agents like this one, and keep them running. If you want it set up for your team instead of doing it yourself, get in touch.
Who it's for
Built for developers who want the busywork around code automated, not the code itself.
Ops-IT teams triaging their own internal requests get the same pattern, different queue.