clay-incident-runbook

# Clay Incident Runbook ## Overview Rapid response procedures for Clay-related production incidents. Clay is a hosted SaaS platform, so incidents fall into two categories: (1) Clay-side issues (platform outage, provider degradation) and (2) your-side issues (webhook misconfiguration, credit exhaustion, handler failures). ## Severity Levels | Level | Definition | Response Time | Examples | |-------|------------|---------------|----------| | P1 | Complete data flow stopped | < 15 min | Credits exhausted, webhook URL expired, Clay outage | | P2 | Degraded enrichment | < 1 hour | Low hit rates, slow processing, CRM sync errors | | P3 | Minor impact | < 4 hours | Single provider down, intermittent webhook failures | | P4 | No user impact | Next business day | Monitoring gaps, cost optimization needed | ## Instructions ### Step 1: Quick Triage (2 Minutes) ```bash #!/bin/bash # clay-triage.sh — rapid diagnostic for Clay incidents set -euo pipefail echo "=== Clay Incident Triage ===" echo "Time: $(date -u +%Y-%m-%dT%H:%M:%SZ)" echo "" # 1. Check Clay platform status echo "--- Clay Platform Status ---" curl -s -o /dev/null -w "clay.com: HTTP %{http_code}\n" https://www.clay.com echo "" # 2. Test webhook delivery echo "--- Webhook Test ---" if [ -n "${CLAY_WEBHOOK_URL:-}" ]; then WEBHOOK_CODE=$(curl -s -o /dev/null -w "%{http_code}" \ -X POST "$CLAY_WEBHOOK_URL" \ -H "Content-Type: application/json" \ -d '{"_triage": true, "_ts": "'$(date -u +%s)'"}') echo "We...