# Attio With the Reo.Dev and Attio integration, your GTM teams can access all Reo developer and account intelligence data—directly inside Attio. You can seamlessly sync contacts, accounts, segments, and audiences, and send qualified leads straight to your CRM. By unifying product and revenue insights in one place, your team gets a complete, actionable view of growth activity. Requirements: * You must be admin of Reo.Dev app * You must be an admin of your Attio CRM instance ### Connect Attio **Step 1**: Navigate to **Setting** → **Integrations** → **CRM**

**Step 2**: Go to Output Integrations > CRM > Click on Connect on the Attio Card.

**Step 3**: You will be redirected to the Authorization flow. Review the permissions and click **Confirm**.

And your Attio instance will be integrated with Reo.Dev. Click on Continue to further configure export and sync Settings on Reo.

### **Attio Export Settings** After the Attio App is connected, you will be redirected to Attio Settings screen on [Reo.Dev](http://reo.dev) to configure the Export and Sync settings.

There are two options to Export data from Reo.Dev: * **Accounts:** You can select Accounts if you want to only export accounts from Reo.Dev to Attio. * **Accounts and Contacts** You can select Accounts and Contacts if you want to only export accounts from Reo.Dev to Attio. Under Accounts and Contacts, you have an option to sync contacts associated with an account automatically or manually. If you select manually, the users will have need to select contacts from the developers tab for each accounts and click on **Send to Attio.** ### **Attio Field Mapping** Map all the fields from Reo.Dev that you want to send to Attio and update existing Accounts and Contacts. This mapping will be used to create new accounts and contacts in Attio. You can also select which fields should be updated in Attio whenever there is any change in Reo.Dev. Please note that when we export data from Reo.Dev, we check if the company or contact exists in the Attio record or not. If the record is present, we update the corresponding fields based on the mapping preference selected by you and in case the record is not present, we create a new records. We use the following fields as unique identifiers to prevent duplication: Accounts → Company Domain Name * Accounts → Company Domain Name Contact → email ID * Contact → email ID ### **Accounts Field Mapping** We have provision to export following fields for Accounts object to Attio.

Reo.Dev Field	Attio Field
Company Name*	Name
Company Domain*	Domain
Location	Primary Location
Employee Range	Employee Range
Annual Revenue	Estimated ARR
Founded In	Foundation date
Last Activity Date*	Reo: Last Activity Date
LinkedIn Company Page	linkedin_company_page
REO Customer Fit Score*	REO: Customer Fit
REO Developer Activity Score*	REO: Developer Activity Score
REO: Segment Name*	REO: Segment Name
REO Account Link*	REO Account Link
REO: Account Summary*	REO: Account Summary
REO: Tags*	REO: Tags
REO: Activity Score (Numeric)*	REO: Activity Score (Numeric)
REO: Company Audience*	REO: Audience
REO: Tech Functions	REO: Tech Functions Summary

* **Company Domain** is a mandatory field and is already mapped. * Fields with prefix REO are automatically created in Attio and mapped to corresponding Reo.Dev field. * For Rest of the fields you can map the corresponding field in Attio from the dropdown. If you select Auto Overwrite checkbox, then we will overwrite the existing data in Attio during creation and sync operations. {% hint style="info" %} Recommendation: Fields with prefix REO should always have Auto-Overwrite checkbox as TRUE. {% endhint %} Quick Note here: Attio does not provide default lifecycle stages, so account stages (e.g., Pipeline, Discovery) cannot be identified. If you've created a custom field (e.g., 'Lifecycle Stage'), you can select that and Reo will automatically create all the corresponding stages from the selected field.

You can learn more about Reo's Account Lifecycle Stages [here](https://docs.reo.dev/accounts/account-lifecycle-stage). ### **Contacts Field Mapping** We have provision to export following fields for Contacts object to Attio. | Reo.Dev Field | Attio Field | | ------------------------------- | ----------------------------- | | Full Name | Name | | Business Email ID\* | Email address | | Designation | Job Title | | Location | Primary location | | LinkedIn ID\* | REO: Linked In Profile | | Last Activity Date\* | REO: Last Activity Date | | REO: Developer Summary\* | REO: Developer Summary | | REO: Segment Name\* | REO: Developer Segment Name | | REO: Tags\* | REO: Developer Tags | | REO: Activity Score (Numeric)\* | REO: Activity Score (Numeric) | | REO: Audience Name\* | REO: Audiences | **Business email ID** is a mandatory field and is already mapped. We fetch the Business email ID of the developers from third part enrichment service providers. In addition to the Business Email ID, **Personal Email IDs** will also be synced **if collected through first-party sources**, including: * Signup Forms on your website or documentation pages * Product login or signup forms. In the Reo.Dev UI, when users hover over the email icon on a profile, if a Personal Email has been enriched and mapped to that profile, it will be displayed alongside the Work Email. Fields with prefix REO are automatically created in Attio and mapped to corresponding Reo.Dev field. For Rest of the fields you can map the corresponding field in Attio from the dropdown. If you select Auto Overwrite checkbox, then we will overwrite the existing data in Attio during creation and sync operations. ### **How Reo.Dev Handles Multiple Email Records in Attio** For each **unique email ID** we treat it as a **separate contact record** in Attio. Depending on whether an email already exists in the CRM, the contact is either **updated or created** as per the following scenarios: | Scenario | | | --------------------------------------------- | ------------------------------------------------------------------------------ | | One Email ID exists in CRM | Update existing contact with latest REO data | | One Email ID does not exist in CRM | Create a new contact record | | Two Email IDs → First exists, second does not | Update existing contact for first email, create a new contact for second email | | Two Email IDs → Neither exists | Create two separate contact records (one for each email) | | Two Email IDs → Both exist in CRM | Update both contacts separately with latest REO data | These cleanups are **rare and limited strictly to Reo.Dev-originated data**, and are performed to maintain data accuracy and reliability. For example, if a developer contact's work email becomes invalid (e.g., they’ve switched jobs), and a new valid email is identified, Reo.Dev may update or clean up the outdated email to ensure your CRM reflects the most current information. Rest assured, no third-party or manually added CRM data is ever deleted by Reo.Dev. *** ### **What Happens When a Contact is Updated?** * If an email already exists in Attio, Reo.Dev **updates the mapped fields** (as configured in CRM settings) with the latest developer data. * Updates **do not overwrite existing CRM data outside the mapped REO fields**. *** ### **How New Contact Records Are Linked to the Same Company/Account** When Reo.Dev creates new contacts, all the captured data—including the **Company Website (Domain Name)**, job title, LinkedIn profile, and other mapped fields—remains the same across contact records associated with the same company. **This ensures that:** * You can easily identify multiple contacts belonging to the same organization in Attio. * Company-wide insights remain consistent, regardless of whether contacts have different email IDs. * Your CRM data stays structured and organized, preventing fragmented company records. By maintaining consistent company-level details, Reo.Dev enables seamless account-based contact tracking, helping sales and marketing teams engage with all relevant stakeholders. {% hint style="info" %} **Recommendation:** Fields with prefix REO should always have Auto-Overwrite checkbox as TRUE. {% endhint %} *** ### **Send Tags to Your CRM** You can now send **Account Tags** and **Developer Tags** directly to your CRM. These tags are fully customizable and provide quick context and insights on already enriched data. **Why it matters:**\ Tags make it easy to: * Identify key account traits or developer activities at a glance. * Segment and prioritize accounts more effectively. * Provide your sales team with richer, actionable insights to drive better conversations.
**Want to learn more?**\ Check out our [Tags Handbook](https://www.reo.dev/tags-handbook) — a comprehensive guide to tagging and segmenting developers in Reo.Dev. It includes **15+ use case examples** designed to help DevTools GTM teams prospect smarter, increase pipeline, and close deals faster. *** #### CRM to Revenue: Data In Playbooks * [Revive Cold Opportunities in your CRM Using Developer Activity Signals](https://www.reo.dev/playbook/revive-cold-opportunities-in-your-crm-using-developer-activity-signals) * [Monitor Dev Activity in your assigned CRM accounts](https://www.reo.dev/playbook/monitor-dev-activity-in-your-assigned-crm-accounts) * [Detect Deal Stalls Early: Monitor & Act on Active CRM Opportunities](https://www.reo.dev/playbook/detect-deal-stalls-early-monitor-act-on-active-crm-opportunities) **Explore the Playbooks Now** → [View All](https://www.reo.dev/playbook-collection/crm) *** ### **User Settings** You can manage permissions for your team by defining specific users who can send data to HubSpot. Click on **Configure** in User Settings.

You will be redirected to Users Section. You can turn on the toggle button in the CRM access column to allow specific users to send data to HubSpot.

### Export and Sync Frequency Users will have options to send: * **Segments to Attio** User can create a segment and click on **Send to Attio** * **Accounts to Attio** User can select an account(s) from the Account list and **Send to Attio** * **Developers to Attio** If Manual contact sync is selected for contacts, users can select developer(s) from the developer tab under Account Details screen and Send to Attio
In case of Accounts and Developer, the export happens in real time and Attio icon will appear against the record on UI immediately but for segments it may take some time depending on the size of segment. Once the Accounts and Developers are exported, Reo.Dev will sync data back to Attio on a daily basis. All the accounts and developers that have been synced with Attio, will have a Attio Icon next to the name. *** ### **Disconnect Attio** You can disconnect Attio from the Integrations section 1. **Open Reo.Dev** 2. Navigate to **Integrations → CRM** and click Configure 3. Under Attio and click Disconnect at the top right corner {% hint style="danger" %} Please note that all the field mappings and user permissions will be lost. {% endhint %}