Back to library
Reliability·n8n workflow

Cloud Availability SLO Monitor

Hourly check: if availability burn exceeds 50%, escalate with hours until SLO breach, affected services, and remediation steps.

Overview

**What it does**: Hourly schedule → query cloud provider health/status API (AWS CloudWatch, GCP Cloud Monitoring) for service availability metrics → compare vs. availability SLO targets (e.g., 99.9%) → IF burn > 50% → LLM calculates: hours until SLO breach, which services degraded, impact → Slack to #platform-alerts with alert. **Setup (5 steps)**: 1. Configure cloud monitoring: AWS CloudWatch, GCP Cloud Monitoring, Azure Monitor (API + credentials) 2. Set SLO targets: per-service (default 99.9%) 3. Set burn threshold: default 50% of monthly allowance 4. Configure Slack channel: #platform-alerts 5. Test: manually trigger service degradation; verify alert in Slack **Apps/nodes**: Schedule, HTTP request (monitoring API), code node (SLO math), Claude/OpenAI (analysis), Slack. **Credentials required**: Cloud monitoring API key, OpenAI account, Slack workspace. **Difficulty**: Medium | **Setup time**: 8 minutes. **Business outcome**: SLO violations caught proactively → availability ↑ predictable, customer trust ↑, incident response ↑ faster.

What's included

Importable n8n workflow (JSON)
Real, wired nodes — trigger, logic, and actions
Setup notes: which credentials to connect
Free updates when the workflow changes
Commercial-use license — keep and customize
Email support if you get stuck

Inside this workflow

Every HourFetch SLO StatusBurned > 50%?Summarize BurnEscalateWithin Budget

Quickstart

  1. 01

    Download the JSON

    With an active Library Pass, download the workflow file right from this page or your dashboard.

  2. 02

    Import into n8n

    Choose Import from File and select the downloaded JSON. The full agent graph appears, ready to configure.

  3. 03

    Plug in credentials

    Each integration node prompts for credentials on first run. The setup guide lists every credential the agent expects.

  4. 04

    Activate and test

    Run once with sample input, confirm the expected output, then flip the activate toggle.

Frequently Asked Questions

How do I import this workflow into n8n?
Download the JSON file from your Library Pass, go to your n8n workspace, click the import button, select "Import from File", and upload the JSON. The entire workflow graph will load instantly, ready for configuration.
What credentials do I need to provide?
Each workflow lists required credentials in its description (e.g., Slack API key, GitHub token, PagerDuty account). You connect your own credentials—the workflow file contains only placeholder names, no actual API keys or secrets.
Are the credentials included in the JSON file?
No. For security, credential IDs are sanitized before distribution. You connect your own accounts when you first run the workflow. n8n will prompt you to authenticate each service.
Can I edit or customize the workflow after importing?
Yes, absolutely. Once imported, the workflow is yours to modify. You can change node logic, add/remove steps, adjust schedules, or integrate with different services. All changes are saved in your n8n workspace.
What n8n version is required?
These workflows use standard n8n-nodes-base node types (released 2022+). They work on n8n Cloud, self-hosted versions 0.180+, and Docker deployments. Community nodes (if required) are noted in the workflow description.
What if something breaks after I import it?
Check the workflow description for setup steps and credential names. Most issues are credential-related. If you get stuck, email support@autoflowworks.com with a screenshot of the error, and we'll help you troubleshoot.
Can I use this workflow for my customers or business?
Yes. The commercial-use license lets you keep, customize, and deploy the workflow for your business or clients. You can redistribute customized versions (except the original unmodified JSON without a valid Library Pass).
Will the workflow receive updates?
Yes. When we improve a workflow (fix bugs, add features, optimize node types), you'll get the updated JSON for free. Check your Library Pass dashboard for new versions.
Do I need n8n Pro or a paid plan?
Not necessarily. These workflows run on n8n Free if you have enough execution time and storage. For production use (frequent triggers, high data volumes, many webhooks), you may want n8n Cloud Pro or higher. Check n8n's pricing for details.
Can I ask for a custom workflow?
Yes! We offer custom workflow design for specific DevOps/SRE use cases. Visit /custom-solutions or email support@autoflowworks.com with your requirements for a quote.

Reviews (0)

No reviews yet. Be the first.

Sign in to leave a review.

Library Pass

Included with any pass

This agent — and every other in the library — comes with a Library Pass. One pass, the whole catalog.

Get a Library Pass
  • Every agent in the library
  • All new releases while active
  • Unlimited downloads
  • Commercial-use license
  • Priority email support
  • 30-day money-back guarantee
Browse the full library →

More in Reliability

Reliability
n8n workflow

Batch Job Failure Watchdog

Monitor scheduled cloud batch jobs; on failure, LLM summarizes what failed, when it last ran, and recovery steps — escalate to #batch-ops.

Included with a PassView →
Reliability
n8n workflow

SSL Certificate & Domain Expiry Monitor

Daily: scan all domains and certificates across accounts; alert 60/30/7 days before expiry to prevent outages.

Included with a PassView →
Reliability
n8n workflow

Cloud Incident Enrichment (Service Context)

Automatically enrich PagerDuty incidents with cloud context: affected services, resource health, cost impact, dependencies — posted to war room instantly.

Included with a PassView →