Make your first Attio API calls -- list objects, create a person,
query companies, and read attributes.
Use when starting a new Attio integration or learning the API.
Trigger: "attio hello world", "attio example", "first attio call",
"attio quick start", "try attio API".
Instrucciones de origen · Vista previa de solo lectura
name
attio-hello-world
description
Make your first Attio API calls -- list objects, create a person,
query companies, and read attributes.
Use when starting a new Attio integration or learning the API.
Trigger: "attio hello world", "attio example", "first attio call",
"attio quick start", "try attio API".
allowed-tools
Read, Write, Edit, Bash(curl:*), Bash(npx:*)
version
1.7.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
["saas","crm","attio"]
compatibility
Designed for Claude Code
Attio Hello World
Overview
Five progressively deeper API calls that exercise the Attio object/record model. Every call targets https://api.attio.com/v2 and returns JSON.
Prerequisites
Completed attio-install-auth (valid ATTIO_API_KEY in env)
Common people attributes: name (personal-name), email_addresses (email-address), phone_numbers (phone-number), description (text), primary_location (location), company (record-reference).
Key detail: Values are keyed by attribute slug. Most attributes accept an array (Attio supports multiselect by default). String shortcuts work for emails and domains.
Workspace
└── Objects (people, companies, deals, custom)
├── Attributes (name, email, phone, custom)
└── Records (individual people, companies)
└── Values (attribute data on each record)
└── Lists (pipelines, boards, custom groupings)
└── Entries (records added to a list with list-specific attributes)
Output
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.
