Skip to main content Accueil Créateurs jeremylongshore tons-of-skills-marketplace webflow-incident-runbook
webflow-incident-runbook Execute Webflow incident response — triage by HTTP status (401/403/429/500),
circuit breaker activation, cached fallback, Webflow status page checks,
communication templates, and postmortem process.
Trigger with phrases like "webflow incident", "webflow outage",
"webflow down", "webflow on-call", "webflow emergency", "webflow broken".
Aller à l'installation Skills Marketplace Découvrez et explorez les compétences IA créées par la communauté.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Afficher les détails du prompt Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace --skill webflow-incident-runbookLa commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.
Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.
Télécharger Zip Téléchargement... Plus depuis ce dépôt langchain-deploy-integration Deploy a LangChain 1.0 / LangGraph 1.0 app to Cloud Run, Vercel, or LangServe correctly — with timeouts sized for chain length, cold-start mitigation, SSE anti-buffering headers, and Secret Manager over .env. Use when prepping a first production deploy, debugging a stream that hangs behind a proxy, or diagnosing p99 latency spikes. Trigger with "langchain deploy", "langchain cloud run", "langchain vercel python", "langchain langserve", or "langchain docker".
langchain-langgraph-agents Build a correct LangGraph 1.0 ReAct agent with create_react_agent — typed tools, error propagation, recursion caps, and stop conditions that actually stop. Use when writing a first tool-calling agent, migrating from AgentExecutor or initialize_agent, or diagnosing an agent that loops on vague prompts. Trigger with "langgraph agent", "create_react_agent", "langgraph tool calling", "AgentExecutor migration", or "agent loop cost".
langchain-langgraph-human-in-loop Build LangGraph 1.0 human-in-the-loop approval flows with interrupt_before /
interrupt_after and Command(resume=...) — JSON-serializable state, clean
resume semantics, and UI wiring for approval decisions. Use when adding an
approval gate before an expensive tool call, wiring a Slack/web UI for agent
approvals, or debugging a graph that crashes on interrupt.
Trigger with "langgraph human in loop", "langgraph interrupt_before",
"langgraph approval flow", "Command resume", "langgraph HITL".
name webflow-incident-runbook description Execute Webflow incident response — triage by HTTP status (401/403/429/500),
circuit breaker activation, cached fallback, Webflow status page checks,
communication templates, and postmortem process.
Trigger with phrases like "webflow incident", "webflow outage",
"webflow down", "webflow on-call", "webflow emergency", "webflow broken".
allowed-tools Read, Grep, Bash(curl:*), Bash(npm:*) version 1.5.0 license MIT author Jeremy Longshore <jeremy@intentsolutions.io> tags ["saas","design","no-code","webflow"] compatibility Designed for Claude Code
Webflow Incident Runbook
Overview
Rapid incident response procedures for Webflow Data API v2 integration failures.
Covers triage, immediate remediation by error type, graceful degradation,
stakeholder communication, and postmortem.
Prerequisites
Access to Webflow dashboard and status page
Application logs and metrics access
Communication channels (Slack, PagerDuty)
Cached fallback data available
Severity Levels
Level Definition Response Time Example P1 Integration fully down < 15 min All API calls returning 401/500 P2 Degraded service < 1 hour High 429 rate, elevated latency P3 Minor impact < 4 hours Webhook delays, form sync lag P4 No user impact Next business day Monitoring gap, stale cache
Quick Triage (Run First)
#!/bin/bash
echo "=== Webflow Incident Triage ==="
echo "Time: $(date -u) "
echo ""
echo "--- Platform Status ---"
curl -s https://status.webflow.com/api/v2/status.json 2>/dev/null | \
python3 -c "
import sys,json
d=json.load(sys.stdin)
print(f'Status: {d[\"status\"][\"description\"]}')
for c in d.get('components',[]):
if c['status'] != 'operational':
print(f' DEGRADED: {c[\"name\"]} ({c[\"status\"]})')
" 2>/dev/null || echo "Cannot reach status page"
echo ""
echo "--- API Connectivity ---"
HTTP=$(curl -s -o /dev/null -w "%{http_code}" \
-H "Authorization: Bearer \
https://api.webflow.com/v2/sites 2>/dev/null)
$WEBFLOW_API_TOKEN
echo
"Sites endpoint: HTTP $HTTP "
echo
""
echo
"--- Rate Limits ---"
"Authorization: Bearer $WEBFLOW_API_TOKEN "
"x-ratelimit\|retry-after"
echo
"No rate limit headers"
echo
""
echo
"--- App Health ---"
echo
"$HEALTH "
"
import sys,json
d=json.load(sys.stdin)
print(f'Status: {d[\"status\"]}')
for k,v in d.get('services',{}).items():
print(f' {k}: {v.get(\"status\",\"unknown\")} ({v.get(\"latencyMs\",\"?\")}ms)')
"
echo
"Health endpoint unreachable"
Decision Tree Is Webflow API returning errors?
├── YES
│ ├── status.webflow.com shows incident?
│ │ ├── YES → Activate fallback. Wait for Webflow resolution.
│ │ └── NO → Our issue. Check token, config, network.
│ ├── HTTP 401/403?
│ │ └── Token issue. See "Auth Failure" below.
│ ├── HTTP 429?
│ │ └── Rate limited. See "Rate Limit" below.
│ └── HTTP 500/502/503?
│ └── Webflow server issue. Activate circuit breaker.
└── NO
├── Our service healthy?
│ ├── YES → Likely resolved or intermittent. Monitor closely.
│ └── NO → Our infrastructure issue (pods, memory, network).
└── Webhooks not firing?
└── Check webhook registrations and endpoint accessibility.
Immediate Actions by Error Type
401/403 — Authentication Failure (P1)
echo "Token present: ${WEBFLOW_API_TOKEN:+YES} ${WEBFLOW_API_TOKEN:-NO} "
curl -s -o /dev/null -w "HTTP %{http_code}" \
-H "Authorization: Bearer $WEBFLOW_API_TOKEN " \
https://api.webflow.com/v2/sites
429 — Rate Limited (P2)
curl -sI -H "Authorization: Bearer $WEBFLOW_API_TOKEN " \
https://api.webflow.com/v2/sites 2>&1 | grep -i "retry-after"
500/502/503 — Webflow Server Error (P2)
curl -s https://status.webflow.com/api/v2/status.json | jq '.status.description'
watch -n 30 'curl -s -o /dev/null -w "%{http_code}" \
-H "Authorization: Bearer $WEBFLOW_API_TOKEN" \
https://api.webflow.com/v2/sites'
Webhook Delivery Failure (P3)
curl -s "https://api.webflow.com/v2/sites/$WEBFLOW_SITE_ID /webhooks" \
-H "Authorization: Bearer $WEBFLOW_API_TOKEN " | \
jq '.webhooks[] | {id, triggerType, url, createdOn}'
curl -s -o /dev/null -w "%{http_code}" https://your-app.com/webhooks/webflow
curl -X POST "https://api.webflow.com/v2/sites/$WEBFLOW_SITE_ID /webhooks" \
-H "Authorization: Bearer $WEBFLOW_API_TOKEN " \
-H "Content-Type: application/json" \
-d '{"triggerType": "form_submission", "url": "https://your-app.com/webhooks/webflow"}'
Communication Templates
Internal (Slack) P[1-4] INCIDENT: Webflow Integration
Status: INVESTIGATING | IDENTIFIED | MONITORING | RESOLVED
Impact: [What users experience]
Root cause: [Webflow outage / Token expired / Rate limited / Our bug]
Current action: [What we're doing]
Next update in: [15 min / 1 hour]
Incident commander: @[name]
External (Status Page) Webflow Integration — Degraded Performance
We're experiencing issues with content updates powered by our Webflow integration.
[Specific impact: delayed content / forms not processing / orders not syncing].
Our team is actively working on resolution. Existing content remains accessible.
Last updated: [timestamp UTC]
Post-Incident
Evidence Collection
grep -i "webflow\|429\|401\|500" /var/log/app/*.log | tail -200 > incident-logs.txt
curl "http://prometheus:9090/api/v1/query_range?\
query=rate(webflow_api_errors_total[5m])&\
start=$(date -d '2 hours ago' +%s) &\
end=$(date +%s) &step=60" > incident-metrics.json
./webflow-debug-bundle.sh
Postmortem Template ## Incident: Webflow [Error Description]
**Date:** YYYY-MM-DD HH:MM — HH:MM UTC
**Duration:** X hours Y minutes
**Severity:** P[1-4]
**Impact:** [Users affected, revenue impact]
### Timeline
- HH:MM — Alert fired: [description]
- HH:MM — Triage started
- HH:MM — Root cause identified: [cause]
- HH:MM — Mitigation applied: [action]
- HH:MM — Service restored
### Root Cause
[Technical explanation]
### What Went Well
- [What worked]
### What Went Wrong
- [What failed]
### Action Items
- [ ] [Preventive measure] — Owner — Due date
- [ ] [Monitoring improvement] — Owner — Due date
Output
Triage script identifying the error source
Decision tree for rapid root cause identification
Remediation steps for every HTTP error type
Communication templates for internal and external stakeholders
Evidence collection for postmortem
Error Handling Issue Cause Solution Status page unreachable Network issue or DNS Use mobile data or VPN Can't rotate token Lost dashboard access Contact Webflow support Circuit breaker stuck open Reset time too long Manually reset or adjust threshold Stale cache served Fallback active too long Set TTL on cached content
Resources
Next Steps For data handling and compliance, see webflow-data-handling.
