> ## 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.
# Integrations
> Keep your CRM as the single source of truth and connect the rest of your stack - HubSpot and Salesforce, Crossbeam, Stripe, Slack, and Teams.
export const Headless = ({prompts = []}) => {
const PromptRow = ({prompt}) => {
const [copied, setCopied] = useState(false);
const copy = () => {
try {
navigator.clipboard?.writeText(prompt);
} catch {}
setCopied(true);
setTimeout(() => setCopied(false), 1600);
};
return ;
};
return <>
Introw is headless by design: run everything here in plain language from Claude, ChatGPT,
Slack, Teams, or your own CRM through Introw's MCP server, with every
action written straight back to your CRM source of truth. The portal is one surface, never the only one.
{prompts.length > 0 ? :
The agentic playbook - lifecycle deep dives and a Claude Code skill library that run your partner program
from Claude, ChatGPT, Slack, and your CRM.
}
;
};
> Introw runs on your CRM, not beside it. Connect HubSpot or Salesforce as the source of truth, layer on ecosystem and billing data, and fan partner activity out to Slack and Teams - so everything stays in sync and partners get reached where they already work.
## What this area does
The **CRM** connection is the foundation - one integration that connects HubSpot, Salesforce, or
Pipedrive, pulls in partners and their contacts live, attributes deals to partners using whatever
method you already use, and embeds Introw on the CRM record. It writes tiers, managers, roles, and
portal access back, so the CRM stays the single source of truth in both directions.
Beyond the CRM, **Chat** posts partner activity and runs the support agent in Slack or Teams,
**Billing** syncs Stripe and Chargebee data that powers commissions, **Crossbeam** brings in partner
ecosystem overlap, and **Zapier**, **MCP**, and the **API** let you automate and build on Introw
programmatically. Every integration reinforces the same principle: the CRM stays authoritative, and
partner work happens in the tools people already use.
## Why it matters
* **CRM-native** - HubSpot and Salesforce stay the system of record, two-way synced, so the CRM admin keeps their object model and nothing important ever drifts into a second database.
* **Time to value** - Connect the CRM once and the program populates itself from records you already have. There is no middleware to build and no data to migrate, so setup is measured in minutes, not an integration project.
* **Work where you already are** - The same connections fan activity out to Slack, Teams, and email, so nobody has to open the portal to stay in the loop.
## How it fits together
The CRM stays authoritative while the rest of the stack connects around Introw:
```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
crm["CRM, source of truth"] <-->|"two-way sync"| introw["Introw"]
billing["Billing"] --> introw
crossbeam["Crossbeam"] --> introw
introw --> chat["Slack and Teams"]
introw --> ai["AI clients over MCP"]
```
## Capabilities
Connect HubSpot, Salesforce, or Pipedrive: sync partners and contacts, attribute revenue, and embed Introw on the record.
Post partner activity and run the agent in Slack or Teams.
Sync Stripe and Chargebee data to power commissions.
Bring in partner ecosystem overlap.
Automate Introw with no-code workflows.
Connect AI clients like Claude and ChatGPT.
Build on Introw programmatically.
## Who works in this area
Connects the CRM and owns the sync.
Configures mapping and channels.
Authorizes connections and access.
## Headless
## All guides
{/* ROLLUP:START - generated content goes here */}
Choose which billing objects to import from Stripe or Chargebee, identify the partner on each, and auto-link records so revenue attributes correctly.
Connect Chargebee with your site name and API key so Introw can import subscriptions, customers, and invoices to power partner commissions.
Authorize Stripe in live or test mode so Introw can import customers, subscriptions, and invoices to power partner commissions.
Map internal channels to keep your team informed, choose which partner events post, and open shared channels with each partner for collaboration.
Authorize Microsoft Teams so Introw can post partner notifications, run shared partner channels, and keep your team in the loop without leaving Teams.
Authorize Slack so Introw can post partner notifications, run shared partner channels, and keep your team in the loop without leaving Slack.
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.
Authorize Crossbeam, align each Crossbeam partner with its Introw partner, and track your record export usage so ecosystem overlap attaches to the right partner.
Generate a Zapier API key, connect the Introw app in Zapier, and build a Zap from a partner event so onboarding, notifications, and syncs run automatically.