Integrations
Connect 11x to your GTM stack. Native Salesforce, HubSpot, Pipedrive, and Zoho 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, Pipedrive, and Zoho 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.
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.
Integration categories
CRM
Salesforce, HubSpot, Pipedrive, Zoho. Bi-directional sync of accounts, contacts, activities, and outcomes.
Email & calendar
Gmail, Outlook, Google Calendar. Sending, and booking against real availability.
Slack
Real-time alerts for replies, bookings, qualifications, and flagged calls.
Reviews & intent
G2 category and comparison research as a buying signal.
Lead routing
ChiliPiper and similar routers for inbound assignment.
Webhooks & API
Push data in, pull outcomes out, trigger motions from any system.
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 |
| HubSpot | Native — setup guide |
| Pipedrive | Native |
| Zoho | Native |
| Anything else | REST API |
What syncs
- 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.
- 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.
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.
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.
Email and calendar
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.
Use a dedicated sending subdomain for outbound rather than your primary corporate domain, so outbound reputation stays isolated from transactional and internal mail.
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.
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.
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.
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.
Setup order
CRM first
Everything else depends on it. Map ownership and opportunity state before anything else.
Email and calendars
Sending domain authentication for Alice; rep calendars for both workers.
Slack
So booked meetings and escalations reach the right person immediately.
Signals and routing
G2, website visitor tracking, and your routing rules.
Webhooks and API last
Add custom automation once the core motion is stable.