> ## Documentation Index
> Fetch the complete documentation index at: https://docs.introw.io/llms.txt
> Use this file to discover all available pages before exploring further.
# CRM
> Connect HubSpot, Salesforce, or Pipedrive, set the partner object, filter and import records, configure attribution, map fields back, and embed Introw in the CRM.
**Open in Introw:** [Integrations → CRM & Data](https://app.introw.io/settings/integrations?category=crm)
## How it works
The CRM integration is one connection that does four jobs. You set it up in this order:
1. **Connect & sync** - authorize HubSpot, Salesforce, or Pipedrive via OAuth. Only one CRM can be connected at a time. Records then sync in on a schedule and through webhooks (contacts, companies, deals, leads, plus owners, pipelines, and currency rates), and select Introw data is pushed back.
2. **Store & import partners and contacts** - tell Introw which object represents partners, filter which records count, and import them with their contacts. New matches can sync automatically.
3. **Attribute** - tell Introw how deals/objects link to partners. It supports whichever method you already use, no code required.
4. **Map back & embed** - push tiers, managers, roles, and contact access to the CRM, and add the Introw cards/components so reps work from the record.
Status pills show whether the integration is connected, syncing, or needs attention.
```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
crm["HubSpot, Salesforce, Pipedrive"] <-->|"OAuth two-way sync"| introw["Introw"]
introw --> portal["Partner portal"]
introw --> embed["CRM embed on the record"]
```
## Prerequisites
* Admin access to your HubSpot, Salesforce, or Pipedrive account (to authorize the app and accept all scopes).
* Integrations write access in Introw.
* For Salesforce, know whether you are connecting a sandbox or production org.
* For write-back mappings (tiers, managers, roles, access), the target CRM properties must exist and be writable.
## Settings & configuration
Everything lives under [Integrations → CRM & Data](https://app.introw.io/settings/integrations?category=crm), plus a few partner/settings screens for write-back mappings.
### Connect the CRM
Use the HubSpot, Salesforce, or Pipedrive tile to authorize via OAuth. Accept **all** requested scopes - declining any blocks the connection. Salesforce supports sandbox or production login and may install a managed package.
### How partners are stored
In the wizard, choose the CRM object that represents partners - Company/Account by default, or **any custom object** you use to manage partners at scale.
### Filter & import (with contacts)
Filter the partner object by CRM property, choose all matches or specific records, and enable **automatically sync new partners** so future matches import on their own. A partner's contacts are pulled in with it and kept current. See [Sync partners & contacts](../guides/sync-partners-and-contacts).
### Attribution
Configure how each object links to partners on the **Object Linking** screen. Methods include a custom property, a HubSpot association label, a Salesforce lookup or relation table, or a one-click property Introw creates for you. Configure **Deal/Opportunity** at minimum. See [Attribution options](../guides/attribution-options).
### Map Introw data back to the CRM
* **Tiers & managers** - at [Tiers](https://app.introw.io/settings/tiers), map a partner's tier and partnership manager to CRM properties.
* **Partner team roles** - at [Partner roles](https://app.introw.io/settings/team/partner-roles), map roles to CRM properties.
* **Contact portal access & role** - from a partner's **People** dialog at [Partners](https://app.introw.io/partners), map access and role to CRM contact properties.
### Embed Introw in the CRM
Add the **Partner Connect card** (HubSpot) or **Introw component** (Salesforce) to record pages, drop **workflow actions** into HubSpot workflows, and rely on **app events** to post partner activity to the CRM timeline. See the embed guides below.
## Setup walkthrough
Authorize HubSpot, Salesforce, or Pipedrive via OAuth and accept all scopes.
Tell Introw how partners are stored (standard or custom object).
Scope which records sync and import them with their contacts; enable automatic sync.
On Object Linking, configure how deals/objects attribute to partners.
Map tiers, managers, roles, and access to the CRM, then add the Introw cards/components.
## How-to guides
Have files partners upload on a shared deal in Introw automatically pushed to the HubSpot deal's attachments, so all partner-supplied documents live in your CRM.
Compare every way to attribute revenue to partners in HubSpot and Salesforce - properties, associations, lookups, relation tables, and custom objects - and how Introw configures each one.
Use the Introw card on a HubSpot deal or ticket to share the record with a partner and exchange comments without leaving the CRM.
Connect HubSpot, choose how partners are stored, filter which records sync, and link deals to partners so attribution flows both ways.
Enable and connect Pipedrive, choose how partners are stored, filter which records sync, and link deals to partners via custom properties.
Connect a Salesforce org, choose how partners are stored, filter which records sync, and link opportunities to partners for accurate attribution.
Spin up an Introw partner portal for a company without leaving HubSpot, using the Introw workflow action or the Introw Copilot card.
Safely disconnect a HubSpot, Salesforce, or Pipedrive connection and understand exactly what stops flowing.
Install the Introw managed package, add the Introw component to record pages, and grant access so reps work with partners from Salesforce.
Attribute HubSpot deals to the partner who influenced them using a custom property, an association, or Introw's one-click setup.
Attribute Salesforce opportunities to the partner who influenced them using a custom field or a relation table.
Map portal access and contact roles to CRM properties so the CRM controls who logs in and how contacts are grouped.
Push partner tiers, tier programs, partnership managers, and team roles back to CRM properties so sales sees them without leaving the CRM.
Use the Introw card on a HubSpot deal to register a new partner deal or link the deal to an existing partner, keeping attribution accurate.
Get Introw partner activity onto the HubSpot timeline and into reports by keeping the app installed with current scopes - events flow automatically.
Authorize the Introw app in HubSpot and add the Introw cards to deal, ticket, and company records so reps work with partners without leaving the CRM.
Surface Introw partner course enrollments and certificates on HubSpot records by adding the Introw course cards to your record layouts.
Surface Introw partner course enrollments and certificates on Salesforce Account and Contact records by adding Introw's related lists to your page layouts.
Pull all your partner accounts and their contacts live from the CRM, drive portal access from a CRM field, and build dynamic segments on account and contact data.
Diagnose and fix a CRM sync that shows a needs-attention status, from expired authorization to missing scopes and over-tight filters.
Drop Introw actions into HubSpot workflows to create or update partners, enroll them in a journey, or issue a certificate automatically.
## Limits & gotchas
Only one CRM can be connected at a time. The CRM is the source of truth, so most fields are edited in the CRM, not Introw - and a write-back target property must exist in the CRM first. Attribution mechanics differ by CRM (HubSpot uses associations; Salesforce uses lookups/relation tables). Object and property labels sync from the CRM, so rename them there. The Salesforce component must be added to each record page layout by an admin.
## Troubleshooting
* **Records are not appearing** - check the partner object and filters, and confirm the sync is healthy.
* **The integration needs attention** - re-authorize; for HubSpot, missing scopes require **Install update**.
* **A deal is not attributed** - revisit the Object Linking configuration and the selected property/association/relation.
* **A tier or role is not writing back** - confirm the mapped CRM property exists and is writable.
* **A card is blank or missing** - confirm the app/component is installed and added to the record layout, and that the record is linked to a partner.