Docs/Advanced

Lists and linked records

Sync a single Attio list, combine parent and list-entry fields, and pull columns in from one related object.

8 min read · Updated July 2026

Objects and lists aren’t the same

Attio object

What’s in it
Every record of one type you can access
Good for
Company directory, full people export, custom-object reporting

Attio list

What’s in it
Only the entries on that list, plus its list-only attributes
Good for
Deal pipeline, event guest list, fundraising, a qualification queue

A list entry points at a parent record. SheetSync puts the parent’s fields and the entry’s list attributes together, so both can land in the same row.

Set up a list sync

  1. 01

    Connect or reconnect Attio

    Approve list permissions if the setup screen says your current connection can’t read lists.

  2. 02

    Choose List as the source

    The picker shows the lists in your connected Attio workspace.

  3. 03

    Pick one list

    SheetSync works out its parent object for you.

  4. 04

    Map both groups

    Parent-record attributes and list-entry attributes are labeled separately in the picker.

Permissions follow the direction

Attio → Sheet only needs read access. Sheet → Attio and bidirectional also need permission to create and update list entries.

Pull in fields from a related object

A record-reference attribute links one Attio object to another — a Person to a Company, say. Expand that link on the mapping screen and you can put the related object’s fields in the same row.

[ People, with company context ]

Object: People

Its fields: Full name, Email address, Job title

Expanded: Associated company

Its fields: Company name, Domains, Company owner

One linked object per sync

Right now a sync can hold active mappings from a single related object. Need a second relationship? Make a second sync.

Writing to a linked object

If the direction writes into Attio, we need enough to find the related record safely. Map something stable on it — a company domain, or another unique identifier.

  • Don’t use a display name as the only key if duplicates are possible.
  • Keep the relationship attribute mapped consistently.
  • Use the preview to confirm which related object and payload we’d use.
  • If matching stays ambiguous, split the sync or add a stable external ID.
Up nextManaging your syncs