Migrating to the new CRM Revenue Insights connector

Time required: about 10-20 minutes.

The Spekit package is deliberately minimal. It installs two components and nothing else:

• Revenue Insights API Connection — an External Client Application
• Revenue_Insights_API_Connection_oauth — its OAuth settings

There are no custom objects, no custom fields, no Apex, no Visualforce pages, no tabs, and no remote site settings. The package exists purely to register Spekit's OAuth client in your org. It does not read or write any data on its own — all data access happens through the Salesforce user who authorizes the connection in Step 3.

• Decide which Salesforce user will run the integration. Many customers use a dedicated integration style user rather than a named administrator. Either works. This user's permissions determine what the connector can see. Also, please note an API only user will not be able to login and accept the OAuth request so the Salesforce user being used for this must be able to access the UI. 
• Confirm the Salesforce user's data access. The integration user needs:
  • The API Enabled system permission.
  • Read access, including field-level security, on: 
    1. Account
    2. Opportunity
    3. Contact
    4. Lead
    5. User
    6. OpportunityContactRole
  • The package does not grant any of this. Object and field access comes entirely from that user's profile and permission sets, which you control.
• Your previously synced data is retained. Disconnecting does not delete it. However, your field mappings will be reset, so plan to review them after reconnecting (Step 4). If you have custom mappings, note them before you disconnect.

1. On the Connect page again (https://app.spekit.co/app/accounts), find the CRM Revenue Insights for Shared Content tile.
2. Click Disconnect.

This step must be performed by a Salesforce user with the Download AppExchange Packages permission.

1. Log in to Salesforce as that user.

2. Open the install link:

   • Production Salesforce: https://login.salesforce.com/packaging/installPackage.apexp?p0=04tTN000000CYcDYAW
      

   ⚠️ Important: Log in to the correct org before opening the link, or log in when prompted. Installing into the wrong org is the most common mistake here.

    

3. Optionally click View Components to review exactly what's being installed.
4. Choose a security setting. Install for Admins Only is fine — see the note below if you're using a non-admin integration user.
5. Click Install.
6. Because the package contains no code or custom objects, installation should be rather quick. Verify it under Setup → Installed Packages.

About the "Install for Admins Only" option

Salesforce's install security setting controls which profiles are granted access to a package's components — custom objects, fields, Apex classes, Visualforce pages, and tabs. This package contains none of those.

As a result, the choice has no practical effect on this package, and "Install for Admins Only" will not block a non-admin integration user from connecting. Access to an External Client Application is governed by the app's own policies in your org, not by the package install setting.

Spekit recommends Install for Admins Only as the least-privilege default.

External Client App policies

After installation, the app appears in Setup → External Client App Manager (not under Manage Connected Apps — External Client Apps are a separate, newer Salesforce framework).

The app ships with Permitted Users set to All users may self-authorize. This means your integration user can complete the OAuth approval in Step 3 without any pre-assignment. Nothing further is required.

If you prefer to lock this down, you can change Permitted Users to Admin approved users are pre-authorized on the app's Policies tab. If you do, you must then explicitly assign your integration user's profile or permission set to the app under App policies. If you skip that assignment, the OAuth approval in Step 3 will fail with an error such as OAUTH_APP_BLOCKED or "This app is blocked".

1. Return to the Spekit Connect page: https://app.spekit.co/app/accounts
2. On the CRM Revenue Insights for Shared Content tile, click Connect.

3. You'll be redirected to Salesforce. Log in as the Salesforce user you want the integration to run as — the integration user you identified in "Before you begin", not necessarily the admin who installed the package.

   ⚠️ Important: If you're already logged in to Salesforce as a different user in that browser, log out first or use a private/incognito window. Salesforce will otherwise silently authorize the wrong user, and the connector will inherit that user's permissions.

    

4. Review the requested permissions in the OAuth request and click Allow.
5. You'll be returned to Spekit and the tile will show as connected.

1. After the connection has been completed, a Salesforce field mapping screen will automatically appear. 
2. Verify these mappings rather than assuming your previous configuration carried over by comparing the current default mappings to the ones captured in Step 1 above
3. Once you've confirmed the mappings in all of the sections are correct, you can close this window.

1. Click Sync Salesforce data. This triggers the first sync on the new connection. 
2. All Done!