Salesforce integration
Connect Salesforce to 11x with the native connector. Authorize access, map fields, set exclusion rules, and verify bi-directional sync before going live.
Salesforce connects to 11x through a native connector with no middleware. You authorize it with OAuth using a Salesforce user that has API access, map the objects and fields, configure exclusion rules, and verify a test record end to end. Budget 30–60 minutes, and confirm who owns Salesforce admin access before you start.
Who this applies to: 11x workspace Admins with Salesforce admin access. This is a prerequisite for launching either digital worker.
Prerequisites
| Requirement | Why |
|---|---|
| Salesforce user with API Enabled permission | The connector authenticates as this user |
| Object-level read/write on the objects you sync | Otherwise the sync silently omits data |
| Knowledge of your ownership model | Drives exclusion rules |
| A test Account and Contact you can safely write to | For end-to-end verification |
Use a dedicated integration service account rather than a person's credentials. Personal credentials break when that person changes role, loses a permission set, or leaves.
Step 1 — Prepare the Salesforce user
Confirm API access
The user's profile or permission set must include API Enabled. Without it the OAuth flow completes but no data moves.
Grant object permissions
Read and write on the objects 11x will use — typically Account, Contact, Lead, Opportunity, Task, and Event. Grant the minimum your motion needs.
Grant field-level access
Any field you intend to map must be visible to this user. Field-level security is the most common cause of a field mapping that appears configured but never populates.
Step 2 — Authorize the connection
Open the integration
In 11x, go to Settings → Integrations and select Salesforce.
Complete the OAuth flow
Sign in as the service account and approve the requested scopes. If your org restricts connected apps, an admin may need to pre-approve 11x.
Choose your Salesforce environment
Connect a sandbox first if you want to validate mapping before touching production data. Re-run the flow against production when you're satisfied.
If your org enforces IP restrictions on API access, allowlist 11x before authorizing. The OAuth flow will otherwise appear to succeed and then fail on the first sync.
Step 3 — Map objects and fields
Map what 11x reads and what it writes back.
| Salesforce 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 | Any segment, tier, or region field your ICP depends on |
| Data | Typical destination |
|---|---|
| Emails sent and replies | Activity / Task records on the Contact |
| Call status, outcome, transcript | Activity records 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 — ICP score, qualification reason, research summary — rather than overloading existing fields. 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: a digital worker contacting an account a rep already owns.
At minimum, exclude:
- Accounts with an open Opportunity
- Accounts flagged as existing customers
- Accounts with an assigned owner where your policy reserves them for that rep
- Competitors and partners
- Anything on your do-not-contact list
- Contacts who have opted out
Exclusion rules are only as good as your CRM hygiene. If account ownership is stale in Salesforce, it will be stale in 11x. Audit ownership before launch, not after the first complaint.
Step 5 — Verify the sync
Check the read direction
Confirm 11x sees a test Account with the correct owner, opportunity state, and custom fields. If a field is blank, check field-level security first.
Run a test record through a motion
Send one test outreach or run one test inbound lead, then open the Salesforce record.
Confirm the write direction
Verify the activity, transcript, score, and outcome all landed on the objects and fields your reporting expects.
Confirm an exclusion fires
Take an account that should be excluded and confirm the digital worker skips it. Testing the negative case matters more than testing the positive one.