Skip to main content
The Attio connection links Flexprice to one Attio workspace through an Attio access token. Flexprice uses the token to read won deals with their companies and people, to write subscription details to deals, and to record invoices in Attio. It also uses the token to register the webhook that tells Flexprice when a deal is won, so the only thing you create in Attio is the token.

What the Attio integration syncs

Flexprice does not sync plans, prices, or payment methods with Attio, and it does not read deals or invoices back from Attio. Attio has no quote object, so the Attio integration has no quote sync.

Before you connect Attio

  • Attio admin access. Only workspace admins can create access tokens.
  • The Deals object turned on in Attio. Attio turns off Deals in new workspaces. Customer sync and deal sync both work from deals. To turn it on, open Workspace settings → Objects and click Activate next to Deals.
  • The Flexprice environment for the connection. The webhook that Flexprice registers in Attio carries the tenant and environment IDs of that environment, so create the connection in the environment you want customers to land in.
  • A free object slot in your Attio plan, if you plan to use invoice sync. Flexprice records invoices in a custom object, which counts toward your plan’s object limit.

Step 1: Create an Attio access token

1

Open the developer settings

In Attio, click your workspace name at the top left, select Workspace settings, then select Developers in the settings sidebar. The Access tokens tab opens.
2

Create the token

Click Create access token. In the New access token dialog, enter a Name such as Flexprice.
3

Set the scopes

Each scope in the dialog has a dropdown set to Disabled. Set the scopes for the syncs you plan to use to the levels in the table below, then click Save.
New access token dialog in Attio, named Flexprice, with Records, Object Configuration, and Webhooks set to Read-write and every other scope Disabled
4

Copy the token

Copy the new token from the Access tokens tab. Attio tokens do not expire, so store the token like a password.

Attio scopes for each Flexprice sync

Leave every other scope at Disabled. In the API, these levels are the scopes record_permission:read, record_permission:read-write, object_configuration:read, object_configuration:read-write, and webhook:read-write. Deal sync and invoice sync need Object Configuration at Read-write because Flexprice adds its own attributes to your Deals object and creates its own Flexprice Invoices object. Customer sync needs Webhooks at Read-write because Flexprice registers its webhook through the Attio API. The Connect Attio sheet in Flexprice reminds you to create the token with the Records, Object Configuration, and Webhooks scopes. Use the table above for the level each sync needs.

Step 2: Create the Attio connection in Flexprice

Connecting Attio from the Flexprice dashboard

1

Open the Attio integration

In the Flexprice dashboard, open Integrations and click Connect on the Attio card. Set Category to CRM to find it next to HubSpot.
Attio card next to HubSpot on the Integrations page, filtered to the CRM category
2

Enter the name and token

Fill in Connection name, then paste the Access token from Step 1.
Connect Attio sheet on the Credentials step with the scopes note, the connection name, the masked access token, and the won stage
3

Pick the won stage

Won stage lists the stages of your Deals object. Pick the stage that marks a deal as won. It defaults to Won 🎉, the won stage Attio creates by default. Flexprice stores the stage’s ID, so renaming the stage in Attio later does not break customer sync. Click Continue.
Won stage list in the Connect Attio sheet with Lead, In Progress, Won, and Lost, and Won selected
4

Choose what syncs

On the Sync step, turn on Pull customers, Push deals, and Push invoices for the syncs you want. All three are off by default. Click Continue.
Sync step with the Pull customers, Push deals, and Push invoices switches turned on
5

Review the webhook

The Webhook step shows the URL that Flexprice registers in Attio and the deal events it subscribes to. There is nothing to copy: Flexprice creates the webhook itself when you connect with Pull customers on.
Webhook step with the Flexprice webhook URL for Attio and the record.created and record.updated events
6

Save the connection

Click Connect Attio. The Attio card moves under Connected on the Integrations page.
Integrations page with the Attio card under Connected

What Flexprice checks when you save the connection

  1. The token. Flexprice calls Attio’s GET /v2/self to confirm the token is active and holds the scopes for the syncs you turned on. If a scope is missing, Flexprice does not save the connection and names the missing scope.
  2. The won stage. Flexprice looks up the stage on the stage attribute of your Deals object and stores its ID.
  3. The webhook. When Pull customers is on, Flexprice creates its webhook with Attio’s POST /v2/webhooks and stores the signing secret that Attio returns, encrypted.

Creating the Attio connection with the API

If you leave out sync_config, every sync is off. Customers only sync inbound, and deals and invoices only sync outbound, so Flexprice rejects the other direction for each of them.

How Flexprice receives Attio deal events

Flexprice registers one webhook for each Attio connection. It points at this URL:
The filters keep every other Attio change, such as an edited deal name or a new note, from reaching Flexprice. Attio events carry record IDs only, so after each event Flexprice reads the deal, its company, and its people through the Attio API. Flexprice checks the Attio-Signature header on every request, an HMAC-SHA256 of the request body signed with the webhook’s secret, and discards requests that fail the check. Attio retries a delivery that does not get a 2xx response up to 10 times over about three days, so a won deal is not lost when Flexprice is briefly unreachable. The webhook is listed in Attio under Workspace settings → Developers, on the Webhooks tab. Flexprice manages it, so do not edit or delete it there: customer sync stops if its URL or events change.

Changing Attio connection settings

To change the connection name or the syncs, open Integrations in the Flexprice dashboard and click Configure on the Attio card. The settings sheet does not show the access token or the won stage.
Attio connection settings with the connection name, the sync switches, the webhook, and Disconnect, but no access token or won stage
  • Turning off Pull customers deletes the Flexprice webhook from Attio. Turning it back on registers a new one.
  • Turning on Push deals or Push invoices later needs the matching scopes. Raise them on the token first, under Workspace settings → Developers → Access tokens in Attio, then turn on the switch.
To use a different access token or won stage, click Disconnect Attio in the same sheet, then connect Attio again. Disconnecting also deletes the Flexprice webhook from Attio. Links between Flexprice customers, subscriptions, and invoices and their Attio records are stored separately from the connection, so they are kept.

Troubleshooting the Attio connection

Attio sync guides

Customer sync

How the company on a won Attio deal becomes a Flexprice customer.

Deal sync

How the subscription’s value, plan, and status reach the Attio deal.

Invoice sync

How invoices appear in Attio and follow payments and voids.