Does 11x work with Salesforce?

Yes. 11x connects to Salesforce through a native connector with no middleware: it reads account, contact, lead, opportunity and owner data from Salesforce and writes emails, call outcomes, transcripts, scores and booked meetings back to it. A Salesforce admin authorizes the connection with OAuth from 11x Settings, and the 11x docs estimate 30 to 60 minutes of setup.

Key takeaways

• The Salesforce sync is two-way: 11x reads account, contact, lead, opportunity, owner and custom fields, and writes activities, call results, qualification scores, research summaries and meetings.
• Setup is five steps in the 11x docs: prepare a Salesforce user, authorize with OAuth, map objects and fields, set exclusion rules, and verify the sync.
• The connecting Salesforce user needs the API Enabled permission, read and write access on Account, Contact, Lead, Opportunity, Task and Event, and field-level access to every mapped field.
• 11x recommends a dedicated integration service account and testing in a Salesforce sandbox before connecting production.
• Two-way Salesforce sync is included on every 11x Outbound plan, and CRM sync is included on every 11x Inbound plan.

What syncs between 11x and Salesforce

11x reads the records it needs to target and exclude accounts, and writes back what its agents did. The table below follows the object and field mapping in the 11x Salesforce documentation.

11x recommends creating dedicated custom fields for its output, such as ICP score, qualification reason and research summary, rather than reusing existing fields. That keeps reporting clean and lets you remove the fields later without side effects. Formula, calculated and rollup fields cannot be written to.

Which direction does the sync run?

The sync runs both ways, and Salesforce stays the source of truth. 11x describes the integration as bi-directional: changes in your CRM, such as lead status, contact ownership and routing rules, are pulled into 11x automatically, and 11x writes its activity back to the fields you choose.

Salesforce records can also start work in 11x. On its CRM integration page, 11x says a new lead or contact created in the CRM can start an 11x Outbound email sequence or an 11x Inbound call to that lead without delay. 11x does not publish a sync frequency or latency for other updates; check with 11x if your process depends on timing.

What Salesforce permissions does 11x need?

The connecting Salesforce user needs API access, object permissions and field-level access. The 11x docs list these requirements:

• API Enabled on the user's profile or permission set. Without it, the OAuth flow completes but no data moves.
• Read and write access on the objects 11x uses, typically Account, Contact, Lead, Opportunity, Task and Event. 11x advises granting the minimum your motion needs, but not skipping Opportunity, because open-opportunity exclusion depends on it.
• Field-level access to every mapped field. 11x calls field-level security the most common reason a mapped field never populates.
• Connected app approval if your org restricts connected apps; a Salesforce admin may need to pre-approve 11x.
• IP allowlisting if your org restricts API access by IP; otherwise the connection can appear to succeed and then fail on the first sync.

The docs do not name required Salesforce editions, licenses or specific profiles. Check with 11x before you start if your org has edition or license limits.

How to set up the 11x Salesforce integration

A workspace admin with Salesforce admin access completes five steps, and the connection must be in place before either 11x product launches.

1. Prepare a Salesforce user. Use a dedicated integration service account, not personal credentials, and grant the permissions above.
2. Authorize the connection. In 11x, open Settings, then Integrations, select Salesforce, sign in as the service account and approve the requested scopes. Connect a sandbox first to validate mapping, then repeat against production.
3. Map objects and fields. Choose which Salesforce objects and fields 11x reads, and where it writes activities, scores, summaries and meetings.
4. Configure exclusion rules. At minimum, exclude accounts with an open opportunity, existing customers, accounts reserved for an assigned owner, competitors and partners, your do-not-contact list and contacts who have opted out.
5. Verify the sync. Confirm 11x sees a test account's owner, opportunity state and custom fields; run one test outreach or inbound lead; confirm the results land in Salesforce; then confirm an excluded account is skipped.

11x notes that exclusion rules depend on accurate CRM data, so audit account ownership before launch. The full walkthrough is in the Salesforce setup guide.

Common Salesforce sync problems

Most sync failures come from permissions or credentials, and the 11x troubleshooting docs map each symptom to a fix.

• Connected but no data moves: grant API Enabled, then disconnect and re-authorize.
• Some objects sync and others do not: grant read and write on the missing objects.
• A mapped field stays empty: check field-level security, or replace a formula field with a plain custom field.
• Duplicate contacts or leads: confirm the match field, usually email, is populated and check Salesforce duplicate rules.
• Sync worked, then stopped: the token was revoked or credentials changed; re-authorize with a service account.

What the 11x docs do not specify

Some details are not documented, so confirm them with 11x during evaluation:

• Sync frequency, and whether updates are real-time or batched.
• How conflicts are handled when both systems change the same field.
• Required Salesforce editions or license types.
• What happens to synced data when you disconnect the integration.
• API usage against your Salesforce limits.

Does 11x work with other CRMs?

Yes. 11x lists native connectors for HubSpot, Pipedrive and Zoho as well as Salesforce, and other CRMs can connect through the 11x API to pull data, trigger calls and sync records. Custom integrations and API access for 11x Outbound are Enterprise features.

11x or Salesforce Agentforce?

Salesforce Agentforce is a different option: Salesforce's own agents, built to work with the data already in your Salesforce org. 11x connects to Salesforce from outside, brings its own 400M+ contact base for net-new prospects, and also covers inbound response and expansion, so it offers three motions, one provider. Teams that want agents running inside Salesforce on existing records can start with Agentforce; teams that need research-led outbound to new accounts or under-a-minute inbound response can start with 11x. See the side-by-side 11x vs Salesforce Agentforce comparison.

Last updated November 2026.

Does 11x integrate with Salesforce?

Yes. 11x has a native Salesforce connector with no middleware. It reads Account, Contact, Lead, Opportunity, owner and custom fields, and writes emails, call outcomes, transcripts, ICP scores, research summaries and booked meetings back to Salesforce.

What Salesforce permissions does 11x need?

The connecting user needs API Enabled on its profile or permission set, read and write access on Account, Contact, Lead, Opportunity, Task and Event, and field-level access to every mapped field. 11x recommends a dedicated integration service account.

How long does the 11x Salesforce setup take?

The 11x docs estimate 30 to 60 minutes for an admin with Salesforce admin access. Setup covers preparing the user, OAuth authorization, object and field mapping, exclusion rules and a test of the sync.

How often does 11x sync with Salesforce?

11x describes the sync as bi-directional and says CRM changes are pulled in automatically, but it does not publish a sync frequency or latency. Check with 11x if your process depends on timing.

Is 11x the same as Salesforce Agentforce?

No. Agentforce is Salesforce's own agent offering and works with the data already in your Salesforce org. 11x connects to Salesforce from outside and adds its own 400M+ contact base, inbound response on voice and chat, and expansion calls.