> ## 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 = ({children, intro = true}) => {
  const [copied, setCopied] = useState(null);
  const copy = event => {
    const row = event.target.closest("li");
    if (!row) return;
    const text = row.textContent.trim();
    try {
      navigator.clipboard?.writeText(text);
    } catch {}
    setCopied(text);
    setTimeout(() => setCopied(null), 1600);
  };
  return <>
      {intro ? <p>
          Introw is <strong>headless</strong> by design: run everything here in plain language from Claude, ChatGPT,
          Slack, Teams, or your own CRM through Introw's <a href="/features/developer/mcp">MCP server</a>, with every
          action written straight back to your CRM source of truth. The portal is one surface, never the only one.
        </p> : null}

      {children ? <div className="not-prose" data-prompts="block">
          <div data-prompts="head">
            <span>{copied ? "Copied" : "Try it from your LLM"}</span>
          </div>
          <div data-prompts="rows" onClick={copy}>
            {children}
          </div>
          <a href="/headless/prompts" data-prompts="more">
            See all prompts
          </a>
        </div> : <Card title="See the headless motion" icon="wand-magic-sparkles" href="/headless">
          The agentic motion - lifecycle deep dives and a Claude Code skill library that run your partner program from
          Claude, ChatGPT, Slack, and your CRM.
        </Card>}
    </>;
};

export const Rail = ({children}) => <div className="not-prose" data-overview="rail">
    {children}
  </div>;

export const Impact = ({children}) => <div className="not-prose" data-overview="impact">
    {children}
  </div>;

export const Personas = ({children}) => <div className="not-prose" data-overview="personas">
    {children}
  </div>;

export const Pains = ({children}) => <div className="not-prose" data-overview="pains">
    {children}
  </div>;

> 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.

## The problem it solves

<Pains>
  | Without Introw | With Introw |
  | - | - |
  | A PRM means a second database | Your CRM stays the source |
  | Migrating data comes first | It reads what you already have |
  | Partners only hear in the portal | It fans out to Slack and Teams |
  | Commissions run on estimates | Real billing data feeds them |
</Pains>

## Impact

The CRM is where your team already works, and your partner's team too. Building the program there instead of beside it is the difference between a portal they are sent to and a program they are in.

<Impact>
  for your business

  * **In your CRM**
    HubSpot and Salesforce stay the system of record, two-way synced, so nothing important drifts into a second database
  * **Live in days**
    Connect the CRM once and the program populates itself from records you already have, with no middleware to build
  * **No new tool**
    The same connections fan activity out to Slack, Teams and email, so nobody opens a portal to stay in the loop

  for your partners

  * **Self-serve**
    Their access follows a CRM field, so getting in and staying in does not need a request
  * **Enabled**
    Their reps get partner context on the CRM record they already have open, and the agent in chat
  * **Efficient**
    One shared reality: their update and yours are the same record, not two to reconcile

  [A day in the life of a co-sell partner](/days-in-the-life/co-sell-partner)
</Impact>

<Personas>
  * **RevOps** - the CRM stays authoritative
  * **Partner Operations** - mapping and channels, no code
  * **IT & Admins** - connections they can authorise
  * **Partners** - reached where they already are
</Personas>

## How this area works

The **CRM** connection is the foundation - one integration that connects HubSpot or Salesforce,
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.

The CRM stays authoritative while the rest of the stack connects around Introw.

**Where this sits in a setup.** First, always. Every [setup track](/tracks) starts by connecting and mapping the CRM, because almost nothing downstream resolves without it.

<Rail>
  * ![The CRM & Data integrations, with HubSpot, Salesforce, Crossbeam, Power BI and Looker and the state of each connection.](https://assets.introw.io/docs/features/integrations/crm/shots/catalog.png)

    [**CRM**](./crm)

    HubSpot or Salesforce, two-way.

    [How to · 23 guides](./crm/technical)

  * ![The Communication integrations, with Slack, Microsoft Teams, WhatsApp and Zapier and the state of each connection.](https://assets.introw.io/docs/features/integrations/chat/shots/catalog.png)

    [**Chat**](./chat)

    Partner activity and the agent in Slack or Teams.

    [How to · 4 guides](./chat/technical)

  * ![The Billing integrations, with Chargebee and Stripe, the sources a commission plan can read revenue from.](https://assets.introw.io/docs/features/integrations/billing/shots/catalog.png)

    [**Billing**](./billing)

    Stripe and Chargebee revenue behind commission calculations.

    [How to · 3 guides](./billing/technical)

  * ![The CRM & Data integrations, where Crossbeam is connected alongside HubSpot and Salesforce to bring account overlaps in.](https://assets.introw.io/docs/features/integrations/crossbeam/shots/catalog.png)

    [**Crossbeam**](./crossbeam)

    Ecosystem overlap, where you collaborate.

    [How to · 1 guide](./crossbeam/technical)

  * ![The Communication integrations, where Zapier sits beside Slack, Teams and WhatsApp as the no-code route to everything else.](https://assets.introw.io/docs/features/integrations/zapier/shots/catalog.png)

    [**Zapier**](./zapier)

    Introw events, out to thousands of apps.

    [How to · 1 guide](./zapier/technical)

  * ![The MCP category of the integrations catalog, with the Claude and ChatGPT connectors that expose the program to an AI assistant.](https://assets.introw.io/docs/features/integrations/mcp/shots/connectors.png)

    [**MCP**](./mcp)

    Connect AI clients like Claude and ChatGPT.

    [Read more](/features/developer/mcp)

  * ![The API Keys page in Developer settings, with the API credit meter and the control that mints a scoped key.](https://assets.introw.io/docs/features/integrations/api/shots/keys.png)

    [**API**](./api)

    Build on Introw programmatically.

    [Read more](/features/developer/api)
</Rail>

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.

One clarification worth making early, because it comes up in nearly every rollout: the **Billing**
integration reads Stripe or Chargebee so commissions can be *calculated* on invoiced revenue. It is
not how partners get *paid*. That is [Introw Pay](/features/commissions/introw-pay), part of
Commissions rather than an integration, and it has no payment account for you to connect.

## When your tool is not on this list

The most common integration question is about a tool that has no tile: a ticketing system, an ERP,
a finance suite, a marketing automation platform, a data warehouse, a quoting or e-signature tool.
The answer is almost never "no", and it is usually not a new connector either.

| What you want | The route | Why this one |
| - | - | - |
| Read data your other tool already writes to the CRM | Nothing to build | Your ERP, billing, or support tool most likely syncs to HubSpot or Salesforce already. Introw reads CRM properties, so that data can drive [commission plans](/features/commissions/commission-plans), [segments](/features/partners/segments), [forms](/features/forms), and [reports](/features/reporting) without touching the other system |
| Push partner events into another tool | [Zapier](./zapier) | Introw events out, thousands of apps in, no code |
| Two-way, on your own terms | [Public API](/features/developer/api) | Every partner, form, deal, task, commission and payout object, with scoped keys |
| Let an assistant do the work | [MCP](/features/developer/mcp) | Claude, ChatGPT, and HubSpot agents act on the program directly |
| Show partners a dashboard from your BI stack | [Power BI](/features/reporting/power-bi) | Embed a real report in the portal |

Two things follow from this. Because the CRM is the source of truth, a tool that integrates with your
CRM effectively integrates with Introw, which is why the list of native connectors stays deliberately
short. And where a route needs building, it is the [API](/features/developer/api) or
[Zapier](./zapier) rather than a professional-services project.

The native connectors are HubSpot and Salesforce for the CRM, Stripe and Chargebee for
billing, Slack, Microsoft Teams and WhatsApp for chat, Crossbeam for ecosystem overlap, Power BI for
embedded reporting, and MCP for AI clients. Everything else runs through the four routes above.

## Run it from your AI assistant

<Headless>
  * Show Acme's open deals synced from HubSpot.
  * Update a deal property and sync it back to Salesforce.
  * Register a deal for Acme from Slack or your CRM.
</Headless>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.