Salesforce package

Overview

Sumble's Salesforce integration enables bi-directional sync between your Salesforce instance and Sumble.

Sync from Salesforce to Sumble:

• Account list — Keep your Sumble account universe in sync with Salesforce

• Account assignments — Personalize the Sumble experience for your AEs and SDRs based on their assigned accounts

• Contacts — Enable champion tracking alerts and indicate whether contacts on Sumble are present in your CRM

Sync from Sumble to Salesforce:

• Custom enrichments — Write firmographic and technographic enrichments relevant to your company back to Salesforce

• Contacts/Leads — Add contacts identified on Sumble back to your CRM

• Signals — Surface job changes, champion alerts, and other signals directly in Salesforce on Account records

Each feature can be enabled individually, with only the narrow set of permissions required for that feature assigned to the integration user.

Note: Requires Salesforce Enterprise Edition or higher to use Bulk API 2.0 functionality.

---

Managed Package

In addition to the data sync capabilities above, Sumble provides a managed package that adds:

• Account Page Widget: A Lightning component (Sumble Enrichments) that displays enrichment data directly on Account record pages, with deep links back to Sumble for detailed information:

  
• Signals Custom Object: A managed Signal__c object that stores signals — such as job changes, champion alerts, and recent hires — linked directly to Account records. Sumble populates these automatically.

• Signals Tab: A dedicated Sumble Signals tab where users can browse, filter, and group all signals for their assigned accounts:

  
• Account Signals Widget: A Lightning component (Sumble Account Signals) that shows signals specific to an Account, embeddable on any Account record page:

  
• Admin Setup UI: A configuration interface for connecting to Sumble and managing enrichment settings

---

Installation

Step 1: Install the Package

1. Navigate to the installation URL: https://login.salesforce.com/packaging/installPackage.apexp?p0=04tHr000001GiBPIA0

2. Log in to your Salesforce org if prompted

3. Select "Install for All Users"

4. Click Install

Note: The Sumble Setup page is restricted to Salesforce administrators only. Users without the "Customize Application" or "Modify All Data" permission will see an "Administrator Access Required" message.

---

Configuration

After installation, navigate to the Sumble Setup tab to configure the integration. The setup wizard guides you through three steps: Connect, Configure, and Complete.

Step 1: Connect to Sumble

Connect your Salesforce org to your Sumble account. The setup page offers two connection modes:

Option A: Quick Setup

Use your current Salesforce user's credentials for the connection. This is the simplest way to get started.

1. On the Connect step, select Quick Setup and click Connect to Sumble

2. A popup window will open with the Sumble login page

3. Log in to your Sumble account and authorize the connection

4. The popup will close automatically and you'll see a success message

Important: The Salesforce user who completes this OAuth flow is the user that Sumble will use to connect to your Salesforce instance.

Option B: Integration User (Recommended for production)

Use a dedicated integration user for the Salesforce connection. This is recommended for production environments because the connection is tied to a service account rather than an individual user — it won't break if someone leaves the organization or changes roles.

The integration user setup is a two-step process:

Step 1 — Salesforce to Sumble: A Salesforce admin clicks Set up with Integration User, then clicks Connect on the first step. This registers your Salesforce org with Sumble. You'll see a green checkmark once the connection is established.

Step 2 — Sumble to Salesforce: Log into Salesforce as your dedicated integration user (a separate browser or incognito window works well). Then visit the URL shown on the setup page — it will look like:

https://sumble.com/integrations/salesforce/start?org_id=<your-salesforce-org-id>

This authorizes Sumble to access Salesforce using the integration user's credentials. Once complete, return to the Sumble Setup page and click Continue to Configuration.

Tip: Create a dedicated Salesforce user (e.g., "Sumble Integration") with the minimum required API permissions. This keeps the integration independent of any individual's account.

Once connected via either method, you'll see a green status bar showing the connected customer name and timestamp.

---

Step 2: Configure

The Configure step has three sections:

Section 1: Select and Order Enrichments for Widget Display

Choose which enrichments appear in the Account page widget and their display order.

• Check/uncheck enrichments to show or hide them in the widget

• Use the up/down arrows to reorder enrichments

• New enrichments added to your Sumble account will appear automatically at the end of the list

Section 2: Choose Where to Store Enrichments

Select where Sumble should write enrichment data in Salesforce.

Option A: Account custom fields (Default)

• Enrichments are written directly to fields on the Account object

• Simplest setup—just map fields in Section 3

Option B: Custom object

• Enrichments are written to a related custom object

• Select your custom object from the dropdown

• See #custom-object-requirements below

Section 3: Map Enrichments to Salesforce Fields (Optional)

Map each enrichment to a specific Salesforce field for data sync.

• For each enrichment, select a destination Salesforce field from the dropdown

• Fields are shown with their API name, label, and type (e.g., Website (Website) - Text)

• Leave as "-- None --" to skip syncing that enrichment

• Each Salesforce field can only be mapped to one enrichment

• Enrichments with URLs also have a separate URL field you can map

Click Save when you're done configuring.

---

Step 3: Complete

After saving, you'll see confirmation that setup is complete, along with instructions for adding widgets to Account pages.

---

Adding Widgets to Account Pages

After completing setup, add the Sumble components to your Account page layout:

1. Navigate to any Account record page

2. Click the gear icon (⚙️) and select Edit Page

3. In the Lightning App Builder, find the Sumble components in the Components panel:

   • Sumble Enrichments — displays enrichment data for the account

   • Sumble Account Signals — displays signals for the account

4. Drag the desired component(s) onto your page layout

5. Click Save and Activate the page

Both widgets will automatically hide if there's no data for an Account, keeping your page clean.

---

Custom Object Requirements

If you choose to write enrichments to a custom object instead of Account fields, your custom object must meet these requirements:

Required Configuration

Requirement	Details
Master-Detail Relationship	The custom object must have a Master-Detail relationship to the Account object
External ID Field	Must have a field named External_Id__c
External ID Settings	The External_Id__c must be a `Text(18)` field and must be marked as External ID.

---

Disconnecting

To disconnect your Salesforce org from Sumble:

1. Navigate to the Sumble Setup tab

2. Click the Disconnect button in the green status bar

3. Confirm the disconnection

This will clear the stored credentials. You can reconnect at any time by clicking "Connect to Sumble" again.

Signals

Sumble automatically populates signals in Salesforce — such as job changes, champion alerts, and new hires in key functions — directly on Account records.

Signals are stored in the managed Sumble Signal (Signal__c) custom object, which has a Master-Detail relationship to the Account object. Each signal includes details like the person's name, title, LinkedIn profile, and the organizations involved.

Signals Tab

Navigate to the Sumble Signals tab to see all signals across your assigned accounts in a single feed.

• Filter by priority — Focus on high, medium, or low priority signals

• Filter by type — Show only specific signal types (e.g., champion alerts, job changes)

• Group by type — Toggle grouping to organize signals by category, with counts per type

• Pagination — Click "Load More" to see older signals

Signals are shown based on Account ownership. By default, you'll see signals for accounts where you are the Owner.

Account Signals Widget

The Sumble Account Signals Lightning component can be added to any Account record page to show signals specific to that account.

• Displays signals with priority badges, person details, and links to LinkedIn and Sumble

• Supports the same priority and type filters as the Signals tab

• Includes pagination for accounts with many signals

Configuring Signal Ownership (Admin)

By default, signals appear for accounts where the current user is the Account Owner. Administrators can expand this to include additional ownership fields:

1. Navigate to the Sumble Signals tab

2. Click the gear icon (⚙️) in the top-right corner to open the Signal Ownership Configuration

3. Select which Account fields determine signal visibility:

   • OwnerId (default) — the standard Account Owner field

   • Custom user lookup fields — e.g., SDR_Owner__c, CSM__c, or any custom Lookup(User) field on the Account object

4. Optionally enable Include Account Team members to show signals for accounts where the user is an Account Team member

5. Click Save

Example: If you select OwnerId and SDR_Owner__c, both the Account Owner and the assigned SDR will see signals for that account on their Signals tab.

---

Account data + Sales Territories

Sumble uses the follow fields for account matching:

Field	Required	Default field
Account ID		Id
Account Name		Name
Account URL		Website
Account Linkedin URL
Country		BillingCountry
Parent Account ID		Parent Id
Ultimate Parent Account ID

If there's other fields that are potentially relevant, we can load those into Sumble's system as well.

To understand your sales team's account assignments, Sumble's app reads the following fields and objects:

• Account Owner (Owner.Name and Owner.Email)

• Custom fields for other roles (e.g. SDR_Owner__r.Name and SDR_Owner__r.Email)

• The AccountTeamMembers table, if used

Technical Details

Data Retrieval (pull from Sumble)

• Uses Bulk API 2.0 Query endpoint

• Resource usage:

  • Consumes up to 6 of 10,000 available daily jobs

  • Pulls only pre-configured fields

  • Downloads all accounts in the instance

Signals Sync

• Signals are synced to the managed Signal__c custom object

• Each signal is linked to an Account via a Master-Detail relationship

• Signals include metadata: type, priority (high/medium/low), person details, organization changes, LinkedIn URLs, and timestamps

• Sumble manages the full lifecycle — signals are created and updated automatically

Data Updates (push from Sumble)

• Uses Bulk API 2.0 Ingest endpoint

• Processing details:

  • Submits jobs with up to 250k rows

  • Up to 6 updates per day for each organization

  • Example scale: For 1.2M accounts

    • Each run takes 5 jobs

    • Processes 7.2M of 150M available daily row updates

  • Updates custom fields on Account object

Book a time to chat with us