Skip to main content

​
Introduction

Qobra connects to Attio through an application, which needs to be installed via an Oauth check. The integration is used to synchronize your Attio data, both Objects (standard and custom) and Lists, with their fields and their content. This integration is readonly and does not write anything in your Attio workspace.

​
Access

​
Oauth authentication & scopes

To connect your Attio to Qobra, you’ll need to go through an Oauth flow, granting us access to several read-only scopes:
  • record_permission:read (Read the content of your records)
  • object_configuration:read (Read objects and their attributes)
  • list_configuration:read (Read lists and their attributes)
  • list_entry:read (Read list entries)
  • user_management:read (Read your workspace members)
You’ll find more information about Attio scopes here.

​
Synchronization

​
Refresh Frequency

Qobra keeps your Attio data up to date through regular synchronizations:
  • Scheduled Full Refresh: on a recurring schedule, we perform a complete sync of all your Attio data
  • On-Demand Updates: Need the latest data right away? Just click the refresh button in your integration settings

​
Total synchronization

This integrations does total synchronization, meaning the whole document will be synced at every refresh. Unlike CRMs such as Salesforce or Hubspot, Attio does not expose a record-level last modified date. As a result, Qobra performs a complete refresh of your data on every synchronization rather than an incremental one.

​
Supported tables

The integration relies on Attio’s schema discovery, so it supports all the data available in your workspace:
  • Objects: all standard objects (such as People, Companies, Deals) as well as any custom object defined in your workspace, with their standard and custom attributes.
  • Lists: each list is synchronized as its own table, including its list attributes and its parent record.
User attribution in Qobra is based on your Attio workspace members, not on the standard Users object (which represents the end-users of your own product).

​
Supported types

You’ll find below the fields types supported by the Qobra integration, and their mapping to Qobra types.

​
Multi-currency amounts

Attio’s built-in currency attribute only stores a single ISO currency code per workspace, which is not enough when your records mix currencies. To work around this, Qobra lets you map any number attribute to Qobra’s amount type and pick a separate attribute that carries the ISO currency code for each record. Use this when you need to import amounts (revenue, ACV, commission base…) whose currency varies from one record to the next.

​
Configure the currency code source

  1. In Qobra, open the field mapping for a number attribute imported as an amount.
  2. Under Currency code, either keep Company currency (the default, applied to every record) or pick an Attio attribute to read the code from for each record.
  3. Save. The new mapping is applied on the next import — existing rows keep their previously imported currency until then.
  4. Trigger a manual refresh from the integration settings if you want the change to take effect immediately.

​
Supported source attributes

The currency code can come from any of these Attio attribute types on the same table: Multi-select select and status attributes are not eligible — a multi-valued attribute has no single code to read.

​
ISO code requirement and fallback

Values (or option labels) must be a valid ISO 4217 code such as EUR, USD, or GBP. If the value is empty, unrecognized, or non-string, Qobra silently falls back to your company currency. Casing and surrounding whitespace are normalized, so usd, USD and USD are treated the same. For select and status sources, name the options directly with the ISO code (for example, an option labeled EUR rather than Euro), otherwise the record will fall back to the company currency.

​
Attio Lists

For a List table, the currency code attribute must live on the List itself, not on the parent Object. Only attributes exposed on the same List entry can be resolved during import. Contact Qobra support for more information.