> For the complete documentation index, see [llms.txt](https://docs.11x.ai/llms.txt).
> Use it to discover all available pages before exploring further.

# Integrations

Connect 11x to your GTM stack. Native Salesforce, HubSpot, and Pipedrive connectors, plus Slack, calendars, G2, webhooks, and a REST API.


11x connects to your GTM stack through native connectors and an API. There are native connectors for **Salesforce, HubSpot, and Pipedrive** with no middleware in between, plus Slack, email and calendar providers, G2, webhooks, and a REST API for everything else. The CRM connection is the one that matters most — it is the system of record both digital workers read from and write to.

<Callout kind="alert">
Connect your CRM before launching a digital worker. Without it, Alice and Julian cannot see account ownership or open opportunities, and may contact accounts a rep is already working.
</Callout>

## Integration categories

<Columns cols={2}>
  <Card title="CRM" icon="database" href="#crm">
    Salesforce, HubSpot, Pipedrive. Bi-directional sync of accounts, contacts, activities, and outcomes.
  </Card>
  <Card title="Email & calendar" icon="mail" href="#email-and-calendar">
    Gmail, Outlook, Google Calendar. Sending, and booking against real availability.
  </Card>
  <Card title="Slack" icon="message-circle" href="/integrations/slack">
    Real-time alerts for replies, bookings, qualifications, and flagged calls.
  </Card>
  <Card title="Reviews & intent" icon="star" href="#reviews-and-intent">
    G2 category and comparison research as a buying signal.
  </Card>
  <Card title="Lead routing" icon="git-branch" href="#lead-routing">
    ChiliPiper and similar routers for inbound assignment.
  </Card>
  <Card title="Webhooks & API" icon="webhook" href="/integrations/webhooks">
    Push data in, pull outcomes out, trigger motions from any system.
  </Card>
</Columns>

## CRM

The CRM is your system of record. 11x reads accounts, contacts, ownership, and opportunity state from it, and writes every interaction back.

| CRM | Connector |
| --- | --- |
| Salesforce | Native — [setup guide](/integrations/salesforce) |
| HubSpot | Native — [setup guide](/integrations/hubspot) |
| Pipedrive | Native |
| Anything else | [REST API](/integrations/webhooks) |

### What syncs

<Tabs>
  <Tab title="Written to your CRM" icon="upload">
    - Emails sent and replies received
    - Research performed on the account and contact
    - Call status, outcome, and full transcript
    - Qualification result and ICP score
    - Meeting bookings
    - Summaries and custom variables

    New inbound contacts are auto-created as CRM records with their data populated.
  </Tab>
  <Tab title="Read from your CRM" icon="download">
    - Account and contact records
    - Contact ownership and routing rules
    - Open opportunity state
    - Lead status and lifecycle stage
    - Activity history
    - Custom fields you map

    Ownership and opportunity state drive the exclusion rules that stop a digital worker contacting an account a rep already owns.
  </Tab>
</Tabs>

### Field mapping and permissions

- **Custom field mapping** routes data to the exact fields matching your CRM schema, so you don't need workaround fields.
- **Granular read and write permissions** control what 11x can access and modify. Grant the minimum your motion needs.

<Callout kind="tip">
Authorize the connection with a service account that has API access, not an individual's personal credentials. Personal credentials break when that person changes roles or leaves.
</Callout>

## Email and calendar

<Tabs>
  <Tab title="Email sending" icon="send">
    Connect Gmail or Outlook mailboxes for Alice's outbound. Authenticate the sending domain with SPF, DKIM, and DMARC before sending anything — see [set up SPF, DKIM, and DMARC](/help-center/deliverability/set-up-spf-dkim-dmarc).

    Use a dedicated sending subdomain for outbound rather than your primary corporate domain, so outbound reputation stays isolated from transactional and internal mail.
  </Tab>
  <Tab title="Calendars" icon="calendar">
    Connect Google Calendar or Outlook for every rep who will receive meetings. Both Alice and Julian book against real availability, so an unconnected calendar causes double-bookings or silent failures.

    This is a per-rep action — see [Getting started as a User](/help-center/get-started/getting-started-as-a-user).
  </Tab>
</Tabs>

## Reviews and intent

G2 integration surfaces category and comparison research as a buying signal, so an account actively evaluating your category can be routed into a relevant play. See [signals and triggers](/core-concepts).

## Lead routing

Julian is compatible with dedicated lead routers such as ChiliPiper. You can either let Julian route directly using your territory, segment, and ownership rules, or hand off to an existing router and let it make the assignment. Configure this in [Set up Julian → routing and calendars](/julian/setup).

## Webhooks and API

One API spans both Alice and Julian. It is bi-directional:

- **Push in** — custom product data, prospect data, and proprietary data
- **Pull out** — outreach, transcripts, research, replies, and outcomes
- **Trigger** — start an 11x motion from a CRM field change, a product signal, or a form submission
- **Subscribe** — webhooks for real-time automation on the events you care about

See [webhooks and the API](/integrations/webhooks).

## Setup order

<Steps>
  <Step title="CRM first" icon="database">
    Everything else depends on it. Map ownership and opportunity state before anything else.
  </Step>
  <Step title="Email and calendars" icon="mail">
    Sending domain authentication for Alice; rep calendars for both workers.
  </Step>
  <Step title="Slack" icon="message-circle">
    So booked meetings and escalations reach the right person immediately.
  </Step>
  <Step title="Signals and routing" icon="radar">
    G2, website visitor tracking, and your routing rules.
  </Step>
  <Step title="Webhooks and API last" icon="webhook">
    Add custom automation once the core motion is stable.
  </Step>
</Steps>

## Frequently Asked Questions

<Expandable title="Why does my CRM connection fail?">
See [Cannot connect CRM](/help-center/troubleshooting/cannot-connect-crm). Most often the authorizing user lacks API access or object-level permissions.
</Expandable>

<Expandable title="Why is data syncing to the wrong fields?">
Review your custom field mapping. Fix this before you accumulate volume — backfilling misplaced CRM data later is painful.
</Expandable>

<Expandable title="Why did a digital worker contact an owned account?">
Your exclusion rules don't reference account ownership or open-opportunity state. Re-check the CRM field mapping and add those exclusions.
</Expandable>

## Next steps

<Columns cols={2}>
  <Card title="Salesforce" icon="cloud" href="/integrations/salesforce" horizontal>
    Full connection and mapping guide.
  </Card>
  <Card title="HubSpot" icon="layers" href="/integrations/hubspot" horizontal>
    Full connection and mapping guide.
  </Card>
  <Card title="Slack" icon="message-circle" href="/integrations/slack" horizontal>
    Notifications and channel routing.
  </Card>
  <Card title="Webhooks & API" icon="webhook" href="/integrations/webhooks" horizontal>
    Events, triggers, and custom automation.
  </Card>
</Columns>