How to integrate Salesforce with 11x
Connect Salesforce to 11x in five steps. Prepare a service account, authorize with OAuth, map objects and fields, set exclusion rules, and verify the sync.
Connecting Salesforce to 11x takes five steps and about 45 minutes: prepare a service account with API access, authorize with OAuth, map your objects and fields, configure exclusion rules, and verify a test record end to end. Confirm who owns Salesforce admin access before you start — that's the dependency most likely to hold you up.
Who this applies to: 11x workspace Admins with Salesforce admin access. This is a prerequisite for launching either digital worker. For the full technical reference including troubleshooting, see the Salesforce integration documentation.
What you'll need
| Requirement | Why |
|---|---|
| Salesforce user with API Enabled | The connector authenticates as this user |
| Read/write on the objects you sync | Otherwise the sync silently omits data |
| Field visibility on every field you map | Field-level security causes silent failures |
| A test Account and Contact | For end-to-end verification |
Step 1 — Prepare a service account
Use a dedicated integration service account, not an individual's credentials. Personal credentials break when that person changes role, loses a permission set, or leaves — and that's the most common cause of a sync that worked and then stopped.
Confirm API Enabled
Check the user's profile or permission set. Without this permission the OAuth flow completes but no data moves.
Grant object permissions
Read and write on Account, Contact, Lead, Opportunity, Task, and Event. Include Opportunity even if it feels unnecessary — it's what open-opportunity exclusion depends on.
Grant field-level visibility
Every field you intend to map must be visible to this user.
Step 2 — Authorize the connection
Open the integration
In 11x, go to Settings → Integrations and select Salesforce.
Sign in as the service account
Complete the OAuth flow and approve the requested scopes.
Consider a sandbox first
Connect a sandbox to validate your mapping, then re-run the flow against production once you're satisfied.
If your org restricts connected apps or enforces IP restrictions on API access, resolve both before authorizing. Otherwise the flow can appear to succeed and then fail on the first sync.
Step 3 — Map objects and fields
| Object | Used for |
|---|---|
| Account | Firmographics, ownership, customer status |
| Contact / Lead | Contact detail, role, lifecycle stage |
| Opportunity | Open-opportunity exclusion, closed-lost revival plays |
| Owner fields | Routing and ownership exclusions |
| Custom fields | Segment, tier, or region fields your ICP depends on |
| Data | Destination |
|---|---|
| Emails sent and replies | Activity / Task on the Contact |
| Call status, outcome, transcript | Activity plus custom fields |
| Qualification result and ICP score | Custom fields on Lead or Contact |
| Research summary | Custom long-text field |
| Meeting booked | Event record |
| New inbound contacts | Auto-created Contact or Lead |
Create dedicated custom fields for 11x output rather than overloading existing ones. Your reporting stays clean and you can remove them without side effects.
Step 4 — Configure exclusion rules
This is the step that prevents the most damaging failure mode: contacting an account a rep already owns.
Exclude at minimum:
- Accounts with an open Opportunity
- Accounts flagged as existing customers
- Accounts with an assigned owner, per your policy
- Competitors and partners
- Your do-not-contact list
- Contacts who have opted out
Exclusion rules are only as reliable as your CRM data. Audit account ownership in Salesforce before launch — stale ownership means stale exclusions.
Step 5 — Verify the sync
Check the read direction
Confirm 11x sees a test Account with the correct owner, opportunity state, and custom fields. A blank field usually means field-level security.
Run a test record through a motion
Send one test outreach, or run one test inbound lead.
Check the write direction
Open the Salesforce record and confirm the activity, transcript, score, and outcome all landed where your reporting expects.
Confirm an exclusion fires
Take an account that should be excluded and verify the digital worker skips it. The negative case matters more than the positive one.
If something goes wrong
| Problem | Likely cause |
|---|---|
| OAuth completes, no data syncs | Missing API Enabled |
| Some objects sync, others don't | Object-level permissions |
| A mapped field stays empty | Field-level security, or a formula field |
| Duplicates being created | Matching field not populated, or duplicate rules |
| Worked before, stopped now | Token revoked or credentials changed |
Full diagnostics: Cannot connect CRM.
Next steps
Salesforce reference
Full technical documentation.
Set up Alice
Configure outbound now the CRM is live.
Set up Julian
Configure inbound now the CRM is live.
Cannot connect CRM
Connection troubleshooting.
Still need help
Email support@11x.ai with your workspace name, the exact error message, and whether the connection previously worked.