Website Uptime Monitor With Email Alerts
Pings your site every two minutes to check availability, updating a public GitHub status page and sending an HTML email alert if it goes...
developers and engineersops and IT teams
What it does
You get immediate HTML email alerts when your website goes down or returns an error, while a public GitHub status page automatically updates to reflect its current availability every two minutes. This ensures you and your visitors always know the site's operational status without manual checking.
Step by step
- Configure the n8n Schedule Trigger to run at your desired interval, such as every five minutes.
- Set up an HTTP Request node to perform a GET request against the target URL and check for status codes outside the 200-299 range.
- Connect the GitHub Node to update the repository contents based on the boolean result of the uptime check.
Where the LLM does the work
- Generate the HTML template code for the email alert that includes dynamic variables for downtime duration and error messages.
- Write the JavaScript logic in the Code Node to parse HTTP response headers and determine if a timeout constitutes an outage.
- Draft the subject line and body text variations for the Gmail Node to ensure alerts are clear and actionable.
Watch out for
Email delivery failures will cause missing alerts so add error handling logic to retry or log failed sends.
False positives from temporary network glitches can spam your inbox so add a consecutive failure threshold before triggering an alert.
Tools that fit
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 Website Uptime Monitor With Email Alerts: Pings your site every two minutes to check availability, updating a public GitHub status page and sending an HTML email alert if it goes... ## Specification - What it does: You get immediate HTML email alerts when your website goes down or returns an error, while a public GitHub status page automatically updates to reflect its current availability every two minutes. This ensures you and your visitors always know the site's operational status without manual checking. - Trigger: On a schedule (Scheduled · every 2 minutes) - Autonomy: Fully hands-off - Expected setup effort: about an afternoon - Tools/services involved: - n8n: Workflow orchestration and automation logic - HTTP Request: Pinging website URL to check availability - Code: Generating dynamic HTML status page content - GitHub: Hosting and updating the public status page - Gmail: Sending email alerts when site is down ## Known pitfalls, handle each one explicitly in your implementation 1. Email delivery failures will cause missing alerts so add error handling logic to retry or log failed sends. 2. False positives from temporary network glitches can spam your inbox so add a consecutive failure threshold before triggering an alert. ## Reference implementation https://n8n.io/workflows/8624 (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/automated-website-uptime-monitor-with-email-alerts/ via usecasesforagents.com
Frequently asked questions
Can I use a different Automation Platform than n8n?
Yes. n8n is only the example automation platform in this recipe. The same flow works with Home Assistant. Swap the automation platform 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.