Skip to main content
Push new list subscribers into Attio as people. Map a Sequenzy list to an Attio list, and each join upserts the person by email, optionally matches a company from the email domain, and adds them to that Attio list. This is outbound only. Attio does not send events back to Sequenzy, and there is no inbound webhook to configure.

​
How it works

  1. Connect with an Attio access token from Workspace settings → Developers
  2. Map each Sequenzy list you care about to an Attio list
  3. When someone joins a mapped list (subscriber.list_subscribed), Sequenzy upserts them as a person in Attio and adds them to the mapped list
  4. If company matching is on, a non-free-mail domain (not Gmail, Outlook, and similar) is upserted as a company and linked on the person
Unmapped lists are ignored. Leaving a Sequenzy list does not remove the person from Attio — the sync is add-only.

​
Connecting Attio

​
Dashboard

  1. Go to Settings → Integrations in Sequenzy
  2. Find Attio under CRM
  3. Click Connect
  4. In Attio, open Workspace settings → Developers, create an access token, and grant object_configuration:read, record_permission:read-write, list_configuration:read, and list_entry:read-write
  5. Paste the token into Sequenzy and connect
  6. Map your Sequenzy lists to Attio lists, then save
Name matches are suggested when nothing is saved yet (for example a Sequenzy list named “Field Guide” maps to an Attio list with the same name).

​
API, CLI, and MCP

Attio uses connectMethod: "api_key". There is no webhook URL.
  • API - POST /api/v1/integrations/connect with { "provider": "attio", "apiKey": "attio_..." }. Optional settings.listMap (Sequenzy list id → Attio list UUID or api slug) and settings.syncCompanyFromDomain (default true). Connect docs
  • CLI - sequenzy integrations connect attio --api-key attio_... --attio-list list_123=field-guide. Reconnect with --attio-clear-lists to remove every mapping, or use --attio-enable-company-domain / --attio-disable-company-domain to change company matching.
  • MCP - connect_integration with provider: "attio" and apiKey
Reconnect with the same call to replace the stored token. Mapping after connect is done in the dashboard (Map lists).

​
What gets synced

Gmail, Outlook, and other free-mail domains are never used for company matching.

​
Things to know

  • Add-only. Unsubscribing, leaving a list, or deleting a subscriber in Sequenzy does not remove the person from Attio.
  • No backfill. People already on a Sequenzy list are not pushed until they join (or rejoin) after the list is mapped.
  • No inbound webhook. Point nothing at Sequenzy; the access token is enough.
  • Live only. Sync runs when someone is added to a mapped list, not on a schedule.
  • Activity. Each upsert is logged on the integration’s Activity view.

​
Scopes

The Attio token needs object_configuration:read, record_permission:read-write, list_configuration:read, and list_entry:read-write so Sequenzy can identify the workspace, list compatible people lists, upsert people and companies, and add list entries. Sequenzy rejects active tokens that are missing any of these permissions.