Diagnose this Chatwoot problem: $ARGUMENTS
Run the read-only checks below (all GETs — safe), interpret the results, and recommend a fix.
Load the troubleshoot skill for the full symptom → cause → fix tables.
Env vars present?
for v in CHATWOOT_BASE_URL CHATWOOT_API_KEY CHATWOOT_ACCOUNT_ID; do [ -n "${!v}" ] && echo "$v: set" || echo "$v: MISSING" doneIf any are missing, stop and point the user to the
setupskill.Base URL reachable?
curl -sI "${CHATWOOT_BASE_URL}" | head -1Token valid + identity? (401 ⇒ bad token, wrong header, or a proxy dropping the header; send
api-access-tokenwith hyphens, notapi_access_tokenand notAuthorization: Bearerunless the instance is v4.19.0+)curl -s -o /dev/null -w "profile HTTP %{http_code}\n" \ -H "api-access-token: ${CHATWOOT_API_KEY}" "${CHATWOOT_BASE_URL}/api/v1/profile" curl -s -H "api-access-token: ${CHATWOOT_API_KEY}" \ "${CHATWOOT_BASE_URL}/api/v1/profile" | jq '{id, name, role}' 2>/dev/null # For comparison: 200 above but 401 here means a proxy drops underscore headers - use the hyphen form curl -s -o /dev/null -w "underscore header HTTP %{http_code}\n" \ -H "api_access_token: ${CHATWOOT_API_KEY}" "${CHATWOOT_BASE_URL}/api/v1/profile"Account scope resolves? (404 ⇒ wrong
account_idor base URL)curl -s -o /dev/null -w "conversations HTTP %{http_code}\n" \ -H "api-access-token: ${CHATWOOT_API_KEY}" \ "${CHATWOOT_BASE_URL}/api/v1/accounts/${CHATWOOT_ACCOUNT_ID}/conversations"CLI installed/authenticated? (optional)
command -v chatwoot >/dev/null && chatwoot auth status 2>&1 | head -5 || echo "chatwoot CLI not installed"Map the observed status codes to the fix using the
troubleshootskill: 401 → token/header or wrong API family · 403 → insufficient role · 404 → account_id/base URL · 422 → request body · 429 → rate limit/backoff. For webhook signature mismatches, verify the HMAC is computed over the raw body as"{timestamp}.{raw_body}".
Report what passed, what failed, and the single most likely fix.