Connecting Attio to Pilea

Connect Attio and Pilea pulls in the customer context your team already keeps there. Companies (and optionally people) become customers in Pilea, notes on those records are analysed as feedback, and call transcripts can be imported as interviews. You can also bring each company’s deal size across, so revenue counts in your priority scores.

It’s a one-way, read-only import. Pilea never writes anything back to Attio.

What you’ll need

Admin access in Pilea
An Attio workspace where you can approve apps (for OAuth) or create API keys (for the API-key option)

How to connect Attio

Step 1: Start the connection in Pilea

In Pilea, go to Integrations in the sidebar under Data Sources.
Find Attio CRM in the catalogue and click Connect.

Step 2: Authorize Pilea in Attio

You’ll be sent to Attio to approve the connection.
Review the permissions and approve. Pilea asks for read access to:
- Records and object configuration: to import companies and people, and to read field names so domains and contract values map across
- Notes: to import notes as feedback
- Meetings and call recordings: to import call transcripts, if you turn them on
You’ll be sent back to Pilea and see an Integration connected message.

Step 3: Choose what to sync

A settings dialog opens for the current workspace. Set Sync from (how far back to import) and tick the data types you want. Everything here can be changed later. The options are explained below.

Connecting with an API key instead

If you’d rather not use OAuth, or you’re connecting during onboarding before your Pilea account is fully set up, Pilea shows an API-key form instead.

In Attio, go to Workspace settings → Developers → API keys and create a key.
Give the key read access to records, object configuration, notes, meetings and call recordings. Attio creates new keys with no permissions at all, so you need to tick each one.
In Pilea, paste the key into the API key field.
Set Import records and notes from, and under Import as customers choose Companies, People, or both.
Click Connect.

Pilea checks the key with Attio before saving it. If the key has been revoked, or is missing permissions, the connection is refused and the error tells you which permissions to add. Better that than a connection that quietly imports nothing.

What syncs from Attio

Open Settings on the Attio CRM card to choose what syncs into the current workspace. The data types are grouped into Core data, Engagements and Calls.

Customers

Attio records are imported as customers in Pilea, so feedback is linked to real accounts. Under Customers, choose which records count:

Companies: your account records, with their domain and, if you choose, their deal size. On by default.
People: individual contacts. Off by default, because a large contact list fills your customer list with one row per person at the same company. Most teams only need companies.

This choice applies to every workspace. Records are re-read on every sync, so edits you make in Attio (a new domain, a changed contract value) show up in Pilea.

Notes

Notes written on your Attio records are imported as feedback and analysed for product requests, pain points and bugs. Pilea reads them as notes, not transcripts: call summaries, meeting debriefs, follow-ups and renewal context, often written in shorthand.

Each note is linked to the company or person it’s attached to in Attio, so it shows up on the right customer in Pilea without any domain guesswork. Notes are only imported from the record types you selected under Customers. In Pilea they appear with the source Attio CRM.

Call transcripts

Tick Call transcripts to import calls recorded in Attio as interviews. It’s off by default, so connecting Attio for CRM data never starts pulling calls by surprise. See Importing call transcripts from Attio for how calls are matched to customers and how to filter which ones come in.

Importing revenue from Attio

Deal sizes power the Revenue Impact signals in your priority scores. Requests from your biggest accounts weigh more. See Customer profiles and deal sizes.

Revenue import is off until you turn it on. Under Customers, tick Revenue, then choose where each company’s deal size comes from:

Auto-detect: Pilea looks for a field like ARR or contract value on each company.
A company field: pick a specific currency or number field on your Attio companies.
Sum of won deals: Pilea adds up the value of each company’s won deals.

If you choose Sum of won deals, Pilea lists your Attio deal stages and asks you to mark each one:

Won: the deal’s value counts toward the company’s deal size.
Open: doesn’t add to revenue, but can affect customer status (see below).
Ignore: counts for nothing.

Stages are pre-marked from Attio: celebrated stages start as Won, and stages named “lost” start as Ignore. Mark at least one stage as Won, or no deals will count.

With Sum of won deals you can also tick Set customer status from deals. A company with a won deal becomes a Customer, and one with only open deals becomes a Lead. This overrides a status set in Pilea. Companies with no deals, or only deals in ignored stages, are left alone.

Revenue settings apply to every workspace. Turning Revenue off stops importing deal sizes, but leaves the ones already in Pilea as they are.

Managing the integration

Sync schedule

Attio syncs automatically every 6 hours. Click Sync now on the Attio CRM card to pull changes straight away. Long syncs run in the background with progress on the card, and you can click Stop sync if needed.

Enable or disable sync per workspace

Integrations are connected once for your organization, but each workspace controls whether it syncs from Attio. Use the Auto sync switch on the Attio CRM card. The workspace that connected Attio starts with it on; other workspaces start with it off. Each workspace has its own Sync from date, data types and call filter.

Re-sync or disconnect

The Advanced tab in the integration’s settings has Full Re-sync from Start, which re-imports everything from your Sync from date without duplicating what Pilea has already processed, and Disconnect Integration.

Troubleshooting

“Missing required scopes” when connecting with an API key Your Attio key doesn’t have all the permissions Pilea needs. Edit the key in Workspace settings → Developers in Attio, tick read access for records, object configuration, notes, meetings and call recordings, and connect again.

No notes appearing Check that Notes is ticked for this workspace and Auto sync is on, then click Sync now. Notes are only imported from the record types selected under Customers, so notes on people won’t come in if only Companies is selected. Also check your Sync from date.

Revenue Impact is 0 in priority scores Make sure Revenue is ticked. With Auto-detect, Pilea needs a currency field like ARR or contract value on your companies. If it can’t find one, pick A company field and choose it yourself. With Sum of won deals, check that at least one stage is marked Won and that your deals are linked to companies in Attio.

“No deal stages found” Pilea couldn’t find any stages on Attio’s Deals object. Check that Deals is enabled in your Attio workspace.

Call transcripts not importing See the troubleshooting section in Importing call transcripts from Attio.

If none of these solve the issue, contact us via the chat bubble in the bottom right. Include your workspace name and a description of what you’re seeing.

Importing call transcripts from Attio - Calls as interviews, customer matching and call filters
Customer profiles and deal sizes - How deal sizes and statuses feed priority scoring
How integration syncing works - Sync cadence, full re-syncs, per-workspace controls and disconnecting

Connecting Attio to Pilea