​

Playbook

​

Attio CRM — Agent Guidance

​

Quick Reference

​

Playbooks

​

Playbook 1: Enrichment Roundtrip

1. attio_assert_record  -> upsert person/company by email/domain
2. Attio auto-enriches  -> job titles, social profiles, company data
3. attio_query_records  -> poll or re-query updated enrichment fields before downstream sync

​

Playbook 2: Pipeline Qualification

1. attio_query_records  -> filter by enrichment criteria (employee_count > 50, funding stage)
2. attio_create_entry   -> add qualified records to "Sales Pipeline" list
3. attio_create_task    -> assign follow-up to rep (round-robin)
4. attio_create_note    -> log qualification reasoning

​

Playbook 3: Meeting Follow-Up

1. attio_assert_record  -> upsert contact by email
2. attio_assert_record  -> upsert company by domain
3. attio_create_note    -> meeting summary (markdown format)
4. attio_create_task    -> action items with deadline
5. attio_assert_entry   -> create/update deal in pipeline

​

Playbook 4: Batch Import

1. Loop: attio_assert_record -> upsert each record (respect 25 writes/sec)
2. Loop: attio_create_entry  -> add to pipeline (respect 25 writes/sec)
3. attio_query_records       -> verify enrichment state before routing follow-up tasks

​

Common Mistakes

• Use assert_record (PUT) not create_record (POST) for upserts. POST fails with 409 on unique attribute conflicts. Assert always succeeds — creates if missing, updates if found.
• Multiselect append behavior on assert: When the matching attribute is multiselect, new values are appended (existing preserved). Non-matching multiselect attributes are fully replaced. Plan accordingly.
• search_records is fuzzy and eventual. It caps at 25 results and is not real-time. Use query_records with structured filters for precise, paginated queries.
• No bulk API. Each record is created or updated individually. Stay within rate limits.
• Note event gotcha: note.updated only fires for title changes. Use note-content.updated to track body edits.
• Enrichment is automatic. Attio enriches records when email (people) or domain (companies) is provided. There is no explicit enrichment API call.
• Always check schema first. Before writing to an unfamiliar object, call attio_list_attributes to discover available attribute slugs and types.

​

Rate Limits