Connect Salesforce once to start tying buyer engagement to your pipeline. Setup is an admin task. After you connect, map your fields, and run the initial sync, engagement resolves to your Salesforce records automatically, and reps do not need to do anything. This guide covers requirements, connecting, field mapping, syncing, and validating your data.
ℹ️ Admin setup, no rep setup: A Salesforce Admin connects Revenue Insights once, using a dedicated Integration User. Reps have nothing to configure. Once setup is complete, their shared content resolves to the right accounts and opportunities on its own.
1. What to know before you connect
| What to check | Detail |
|---|---|
| Prerequisite | Trackable Links or Deal Rooms must be enabled. Contact your CSM or support@spekit.co if needed. |
| Who connects | A Salesforce Admin, authenticating with a dedicated Integration User. |
| What Spekit accesses | Read access to six Salesforce objects: Account, Opportunity, Contact, Lead, User, and OpportunityContactRole. Spekit never creates, edits, or deletes Salesforce records. |
| API Enabled | The authorizing user must have API Enabled on their profile, or the connection will fail. |
| OpportunityContactRole | This object needs its own Read permission. Read access on Opportunity does not include it. |
| View All Records (optional) | By default, Spekit only syncs records visible to the authorizing user under your sharing rules. To sync all records in the org, also grant View All Records on the six objects. |
| Sandbox | Salesforce Sandbox is not supported. Connect a production org. |
Salesforce permissions the connection requests:
- Access the identity URL service
- Manage user data via APIs
- Perform requests at any time
💡 Pro tip: Confirm the connecting user has API Enabled and Read access to all six objects, including OpportunityContactRole, before you start. A missing permission on one object is the most common reason a connection stalls partway.
💡 Pro tip: If reps report that some accounts or opportunities are missing after setup, it is almost always the View All Records permission. Without it, Spekit only sees what the Integration User can see under your sharing rules.
2. Connect your Salesforce instance
A Salesforce Admin sets this up once, using the Integration User credentials.
- Open the Spekit Hub (Web App).
- Navigate to Settings.
- Click Connect.
- Find the CRM Revenue Insights for Shared Content tile.
- Click Connect to Salesforce.
- Log in to Salesforce when prompted, using the Integration User, to complete authentication.
3. Map required fields
Right after authentication, Spekit shows the field mapping step. Mapping is what ensures Spekit tracks data against the correct Salesforce objects and fields.
Review the pre-selected default mappings:
| Object | Default fields mapped |
|---|---|
| Account | Name, Revenue, Industry |
| User | Username, Email, Is Active |
| Opportunity | Stage Name, Status, Is Closed, Name, Close Date, Deal Size |
| Contact | Title, Department, Email, First Name, Last Name |
If a default is not the right field for your org, adjust it. For example, if Amount is not the Salesforce field that captures your opportunity Deal Size, map Deal Size to the correct field. Click Exit (X) to save your initial mappings.
ℹ️ Updating mappings later: You can change field mappings anytime from Settings. See Managing Your Revenue Insights Connection.
💡 Pro tip: Map Deal Size to the field your team actually forecasts on. If it points at the wrong field, your influenced pipeline and revenue numbers will be off even though everything else is set up correctly.
4. Sync your Salesforce data
Once mapping is complete, run the initial sync to pull your Salesforce records into Spekit.
- Open the Spekit Hub (Web App).
- Navigate to Settings.
- Click Sync Salesforce Data.
- A notification confirms the sync has started. You are notified in the Web App and Chrome Extension once it is complete.
After this initial sync, updates sync automatically about every 10 minutes.
⚠️ To confirm before publishing: the setup guide describes a manual "Sync Salesforce Data" step for the initial pull, while ongoing updates sync automatically about every 10 minutes. Confirm whether the first sync is triggered manually or runs on its own after mapping, and adjust this section to match.
5. Validate your data
After the sync completes, confirm Salesforce data is flowing.
- Open a piece of content that can be shared externally, such as a Spek or File.
- Click the share arrow and select Externally.
- Confirm that your synced Salesforce data (Accounts, Opportunities) appears in the company dropdown.
ℹ️ How the dropdown is ordered: Trackable Links prioritizes options by recent activity in Salesforce and opportunities where you are the owner.
6. Keeping the connection stable: the Integration User
Connecting through an individual admin's account works until that person changes roles or leaves, which breaks the connection and stops the sync.
💡 Pro tip: Authenticate with a dedicated Salesforce Integration User rather than a personal account. It keeps engagement data flowing through team changes and keeps ownership clean.