Before connecting Attio to Enginy, make sure your workspace meets the following requirements. This article covers what you need on the Attio side — for step-by-step connection instructions, see How to Configure Your Attio Integration.
What Enginy will do with your Attio
With the permissions granted, Enginy will be able to:
Read and create/update people and companies in your workspace.
Read the configuration of your custom objects and fields so they can be mapped correctly.
Add and remove entries in your lists, and read how they're configured.
Read the workspace users (needed to assign owners).
Create and read notes on contacts to log your campaign activity.
Required Attio plan
Any Attio plan works — Free, Plus, Pro, or Enterprise. Attio's public API is not restricted by plan, so you don't need to upgrade just to connect Enginy.
User Permissions
When authorizing the integration, these scopes are granted:
Technical scope | What it allows |
| Read and modify records (people and companies) |
| Read the configuration of your custom objects and fields |
| Read the configuration of your lists |
| Add and remove entries in lists |
| Read the workspace users (to assign owners) |
| Create and read notes on contacts |
Authentication
Enginy connects via OAuth 2.0.
Relevant security detail: Attio access tokens don't expire, and Attio doesn't issue refresh tokens. This means that, unlike other CRMs, there's no periodic automatic refresh — the same token stays valid indefinitely until revoked.
Sandbox
Not supported.
Security
As explained above, the token doesn't expire and there's no refresh token — this makes manual revocation even more important than with other CRMs if you ever want to cut off access.
You'll need to manually revoke access from your Attio settings — removing the integration from Enginy doesn't do this automatically.