Collect Attio integration diagnostic evidence -- API health, scopes,
object schema, and rate limit status -- for debugging or support tickets.
Trigger: "attio debug", "attio support bundle", "attio diagnostic",
"collect attio logs", "attio not working debug".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Collect Attio integration diagnostic evidence -- API health, scopes,
object schema, and rate limit status -- for debugging or support tickets.
Trigger: "attio debug", "attio support bundle", "attio diagnostic",
"collect attio logs", "attio not working debug".
Collect all diagnostic evidence needed to debug Attio API issues or file a support ticket. Checks auth, scopes, object schema, rate limit headers, and endpoint connectivity.
Prerequisites
ATTIO_API_KEY environment variable set
curl and jq available
Permissions to read project environment
Instructions
Step 1: Run the Full Diagnostic Script
#!/bin/bash# attio-debug-bundle.sh -- Collects Attio diagnostic evidenceset -euo pipefail
BUNDLE_DIR="attio-debug-$(date +%Y%m%d-%H%M%S)"mkdir -p "$BUNDLE_DIR"
SUMMARY="$BUNDLE_DIR/summary.txt"echo"=== Attio Debug Bundle ===" | tee"$SUMMARY"echo"Generated: $(date -u +%Y-%m-%dT%H:%M:%SZ)" | tee -a "$SUMMARY"echo"" | tee -a "$SUMMARY"# 1. Check token is set (never log the actual key)echo"--- Token Status ---" | tee -a "$SUMMARY"if [ -z "${ATTIO_API_KEY:-}" ]; thenecho"ATTIO_API_KEY: NOT SET" | tee -a "$SUMMARY"
| -a
1
| -a
| -a
| -a
HTTP_CODE=$(curl -s -o -w \
-H \
https://api.attio.com/v2/objects)
| -a
[ = ];
| -a
jq -r \
| -a
[ = ];
| -a
[ = ];
| -a
jq 2>/dev/null | -a
| -a
| -a
curl -s -D -o /dev/null \
-H \
https://api.attio.com/v2/objects
grep -i 2>/dev/null | -a || | -a
| -a
| -a
obj people companies;
| -a
curl -s \
-H \
| jq -r \
2>/dev/null | -a || | -a
| -a
| -a
curl -s https://api.attio.com/v2/lists \
-H \
| jq -r \
2>/dev/null | -a || | -a
| -a
| -a
curl -s https://api.attio.com/v2/webhooks \
-H \
| jq -r \
2>/dev/null | -a || | -a
| -a
| -a
| -a
| -a
| -a
| -a
curl -s https://status.attio.com/api/v2/status.json \
| jq -r 2>/dev/null | -a || | -a
tar -czf
-rf
echo
"Cannot proceed without API key"
tee
"$SUMMARY"
exit
else
echo
"ATTIO_API_KEY: SET (${#ATTIO_API_KEY} chars, starts with ${ATTIO_API_KEY:0:3}...)"
Following this guide produces the Attio integration outcome for its topic—configuration, validation evidence, operational recovery, or a documented migration result. Record command output and relevant identifiers so a failed step is traceable.
Examples
Start with the smallest applicable command or code example in the relevant section, using a dedicated test record or workspace and non-production credentials. Confirm the expected response or validation result before applying the pattern to production.