n8n DR Readiness Scoring Workflow: Remediation Tasks & Rollup

Know your Disaster Recovery readiness every day—automatically

The n8n DR Readiness Scoring Workflow: Remediation Tasks & Rollup daily (or on-demand) evaluates disaster recovery across your in-scope systems, scores each system from 0–100, creates remediation tasks for gaps, escalates critical findings, and produces a single rollup report for the run.

What this workflow does

• Schedules and scope: Runs daily at 06:00 (or manually) to load the list of in-scope systems plus DR policy thresholds, pillar weights, and remediation settings.
• Pulls DR signals via internal HTTP APIs: For each system, it fetches backup freshness, AWS RDS snapshot recency and cross-region copy status, replication health/lag, Terraform workspace drift, and DR runbook last review metadata.
• Normalizes results safely: Unreachable sources are treated as “unknown” rather than healthy.
• Scores readiness: Computes per-pillar scores (backup, snapshot, replication, IaC drift, runbook) and produces a weighted overall DR readiness score (0–100). It also identifies pillar-level gaps and trends over recent runs.
• Creates remediation tasks: For each gap, it generates structured tasks via a task-tracker HTTP API, with priority and due dates based on severity.
• Escalates critical systems: When a system is rated Critical, the workflow waits briefly to reduce duplicate escalations, then sends an urgent alert via an incident/alerting HTTP API.
• Rolls up results: Aggregates all system outcomes into one DR readiness rollup summary for the run.

Use cases

• Daily verification that backups, RDS snapshot copies, and replication are meeting DR targets.
• Automatic gap-to-task conversion for DR remediation—so issues don’t get lost.
• Critical incident escalation with reduced alert duplication.
• Evidence-ready rollup reporting for DR audits and ongoing improvements.

Technical details

• n8n workflow nodes: if, set, code, wait, merge, split out.
• Integrations: Internal backup, RDS snapshot/copy, replication health/lag, Terraform drift, and DR runbook metadata exposed through HTTP APIs.
• Required setup: Replace placeholder endpoints and configure required authentication.