# Attio integrations: records and lists

> Create a record, create a list and add a record to a list in Attio, and start a workflow when Attio sends “Record created”.

**Canonical page:** https://tray.ai/connectors/attio-integrations/
**Categories:** Sales
**Connects through:** HTTP Connector

## Overview

Attio is a customizable CRM where teams model their own objects and lists, then track records, notes, tasks, and comments against them. Tray.ai connects to Attio through the HTTP Connector, so your workflows can call the Attio API alongside the rest of your stack.

## Use cases

### Records

Read, create, update, and delete records in Attio from any Tray.ai workflow. The Attio API covers calls such as list records and create a record.

- List records
- Create a record
- Update a record

### Lists

Read, create, and update lists in Attio from any Tray.ai workflow. The Attio API covers calls such as list all lists and create a list.

- List all lists
- Create a list
- Update a list

### List entries

Read, create, update, and delete list entries in Attio from any Tray.ai workflow. The Attio API covers calls such as list entries and add a record to a list.

- List entries
- Add a record to a list
- Update a list entry

### Notes

Read, create, update, and delete notes in Attio from any Tray.ai workflow. The Attio API covers calls such as list notes and create a note.

- List notes
- Create a note
- Update a note

### Tasks

Read, create, update, and delete tasks in Attio from any Tray.ai workflow. The Attio API covers calls such as list tasks and create a task.

- List tasks
- Create a task
- Update a task

### Comments

Read, create, and delete comments in Attio from any Tray.ai workflow. The Attio API covers calls such as list threads and create a comment.

- List threads
- Create a comment
- Delete a comment

## Challenges Tray.ai solves

### Keeping Attio credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Attio credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Attio API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Attio API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Attio?

Yes. Tray.ai connects to Attio through the HTTP Connector, which calls the Attio API directly. Any call the Attio API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Attio?

The Attio API uses a bearer token and OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Attio connector?

Attio runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Attio connector from the Attio API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/