clay-debug-bundle

# Clay Debug Bundle ## Current State !`node --version 2>/dev/null || echo 'N/A'` !`python3 --version 2>/dev/null || echo 'N/A'` ## Overview Collect all diagnostic information needed for Clay support tickets. Clay is a web platform, so debugging focuses on webhook delivery, enrichment column errors, HTTP API responses, and credit consumption -- not pods or clusters. ## Prerequisites - Clay account with access to affected table - curl for testing webhook/API connectivity - Browser developer tools for capturing network requests ## Instructions ### Step 1: Create Debug Bundle Script ```bash #!/bin/bash # clay-debug-bundle.sh — collect Clay integration diagnostics set -euo pipefail BUNDLE_DIR="clay-debug-$(date +%Y%m%d-%H%M%S)" mkdir -p "$BUNDLE_DIR" echo "=== Clay Debug Bundle ===" > "$BUNDLE_DIR/summary.txt" echo "Generated: $(date -u +%Y-%m-%dT%H:%M:%SZ)" >> "$BUNDLE_DIR/summary.txt" echo "" >> "$BUNDLE_DIR/summary.txt" ``` ### Step 2: Test Webhook Connectivity ```bash # Test webhook endpoint is reachable echo "--- Webhook Test ---" >> "$BUNDLE_DIR/summary.txt" WEBHOOK_URL="${CLAY_WEBHOOK_URL:-not_set}" if [ "$WEBHOOK_URL" != "not_set" ]; then HTTP_CODE=$(curl -s -o "$BUNDLE_DIR/webhook-response.txt" -w "%{http_code}" \ -X POST "$WEBHOOK_URL" \ -H "Content-Type: application/json" \ -d '{"_debug": true, "_test": "debug-bundle"}') echo "Webhook HTTP Status: $HTTP_CODE" >> "$BUNDLE_DIR/summary.txt" echo "Webhook URL: ${WEBHOOK_URL:0:50}..." >> "$BUNDL...