Attio

​

What’s Supported

​

Supported Actions

• Read Actions, including full historic backfill and incremental read.
• Write Actions.
• Subscribe Actions. Ampersand creates and manages the Attio webhook subscription on your behalf when the customer installs your integration — no manual webhook setup is required in the Attio UI.
• Proxy Actions, using the base URL https://api.attio.com.

​

Supported Objects

​

Subscribe events

• Standard and custom objects (People, Companies, Users, Deals, Workspaces, and any custom object) are subscribed through Attio’s generic record events (record.created, record.updated, record.deleted), scoped to the specific object. They support create, update, and delete events.
• Core objects are subscribed through object-specific events: Notes, Tasks, and Lists support create, update, and delete; WorkspaceMembers supports create only. Note that Lists events fire on the list object itself (a list being created, updated, or deleted) — not on records being added to or removed from a list.

• Standard objects must be activated. Attio delivers record.* events only for objects that are active in the workspace. People, Companies, and Deals are active by default; Users and Workspaces are optional standard objects that must be enabled under Workspace settings → Objects before they can be subscribed to.
• Watched fields are not supported. Attio webhook payloads do not include changed-field data, so field-level update filtering (requiredWatchFields) is not available. Use watchFieldsAuto: all for update events — they fire on any change to the record, and Ampersand fetches the full updated record for you.
• Scopes gate webhook creation and delivery. Your Attio app must be granted read-write access to the Webhooks scope (to create the subscription) and read access to record objects (so Ampersand can fetch the changed record). Grant these under Workspace settings → Developers → [your app] → Scopes; without them, subscription creation fails with a 403.

subscribe:
  objects:
    - objectName: people
      destination: attioWebhook
      inheritFieldsAndMapping: true
      createEvent:
        enabled: always
      updateEvent:
        enabled: always
        watchFieldsAuto: all
      deleteEvent:
        enabled: always
    - objectName: notes
      destination: attioWebhook
      inheritFieldsAndMapping: true
      createEvent:
        enabled: always

​

Example integration

​

Before You Get Started

• Client ID
• Client Secret

​

Create an Attio Account

• Go to the Attio Sign Up page.
• Sign up using your preferred method.

​

Creating an Attio App

1. Log in to your Attio account.
2. Click on New app to open the New app dialog.
3. Enter a name for the application in the name section and click Create app.
4. Navigate to the OAuth section and enable OAuth switch to view the Client ID and Client Secret.
5. In the Redirect URIs section, click New redirect URI, add the Ampersand Redirect URI: https://api.withampersand.com/callbacks/v1/oauth.
6. Click Configure scopes, enable the necessary scopes, and click Save changes.

​

Add Your Attio App Info to Ampersand

1. Log in to your Ampersand Dashboard.
2. Select the project where you want to create an Attio integration.
3. Select Provider Apps.
4. Select Attio from the Provider list.
5. Enter the previously obtained Client ID in the Client ID field and the Client Secret in the Client Secret field.
6. Click Save Changes.

​

Using the connector

• Create a manifest file using the example.
• Deploy it using the amp CLI.
• If you are using Read Actions or Subscribe Actions, create a destination.
• Embed the InstallIntegration UI component.
• Start using the connector!
  • If your integration has Read Actions or Subscribe Actions, you’ll start getting webhook messages.
  • If your integration has Write Actions, you can start making API calls to our Write API.
  • If your integration has Proxy Actions, you can start making Proxy API calls.