Diagnose Attio REST API failures using response status, structured error details, and endpoint documentation. Identify authentication, permission, validation, and rate-limit problems, then apply a minimal correction and verify it while keeping tokens and customer data out of diagnostic records.
Diagnose Attio REST API failures from status, structured error fields, endpoint contract, and request context without exposing customer data. Use when an Attio request returns 400, 401, 403, 404, 409, 422, 429, or 5xx. Trigger with "Attio error", "Attio request failed", or "debug Attio API".
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
This skill classifies an Attio failure before changing code or credentials. It preserves the response's structured fields while keeping tokens and CRM values out of diagnostics.
Use Read, Glob, and Grep to locate the caller, response parser, retry policy, and logs. Use WebFetch only for current official Attio documentation. Use Write or Edit only after the failing contract and safe verification path are known.
Attio error responses can include status_code, type, code, and message. Diagnose from observed fields instead of inventing a fixed code list; endpoint references remain authoritative for request shape and scopes.
Confirm that a Bearer token exists at runtime and belongs to the intended workspace. For 401, rotate or replace the invalid credential; for 403, compare granted scopes with the endpoint's required scopes before requesting any change.
Retry-After as an HTTP date and retry only after the indicated time.Do not broaden scopes, rotate a shared production credential, replay an ambiguous mutation, or expose customer payloads while troubleshooting without the responsible owner and a recovery plan.
| Signal | Likely class | Safe next check |
|---|---|---|
| 400 or 422 | Shape or attribute-value validation | Compare body and attribute type with endpoint docs. |
| 401 | Missing or invalid token | Inspect credential injection without printing the token. |
| 403 | Insufficient scope | Compare exact required scopes. |
| 404 | Wrong resource identifier | Resolve current object, list, record, or entry ID. |
| 409 | Uniqueness conflict | Inspect the documented uniqueness boundary. |
| 429 | Global or score-based throttle | Honor Retry-After; simplify expensive queries. |
| 5xx | Provider or transient failure | Bound retries and retain redacted evidence. |
Return a redacted failure fingerprint, diagnosis, evidence, minimal correction, replay result, and any remaining uncertainty.
| Condition | Response |
|---|---|
| Response is not JSON | Preserve status and content type; do not force JSON parsing. |
| Token appears in evidence | Stop and redact before storing or sharing it. |
| Retry repeats a permanent 4xx | Stop retrying and fix the request contract. |
| Resource identity is uncertain | Resolve it with a read-only discovery request. |
Input:
method=POST; path=/v2/objects/companies/records/query; status=403; code=forbidden
Expected handoff:
class=authorization; missing-scope=confirmed-from-endpoint; replay=pass
This result ties the correction to endpoint evidence and a safe replay.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Add a synthetic-data CI gate for customer-owned Abridge integration code. Test consent handling, note-review handoffs, redaction, and rollback behavior with mocked vendor boundaries, without connecting CI to a live Abridge or EHR tenant.
Triage Abridge recording, note review, Epic handoff, and access problems using observed symptoms and approved guidance. Identify the affected workflow stage, organize a minimal timeline, and prepare a redacted escalation record for the responsible team.
Map and review an Abridge clinical documentation workflow from consent and recording through draft review, evidence checks, edits, and final disposition. Keep clinician approval explicit, identify failure exits, and separate verified facts from tenant-specific details and pending approvals.
Audit how clinician-reviewed Abridge note sections map into Epic templates and downstream workflows. Use approved test records to document destinations, exceptions, evidence, rollback steps, and a go or no-go decision for a specific environment.
Review Abridge adoption and workflow value using local usage records, clinician feedback, and verified contract costs. Build an evidence based decision table covering adoption, quality, support burden, and options to expand, hold, or improve the rollout.
Prepare a bounded support bundle for an Abridge issue using allowlisted operational details such as versions, coarse timestamps, and correlation references. Exclude recordings, transcripts, patient identifiers, credentials, and unrestricted logs, then document redactions and review details.