Reference · built on requestConnectorCRM & sales

Salesforce Sales Cloud

Leads, accounts, contacts, opportunities, and activities from a Salesforce org, with change events as records move.

Request accessPricing ↗

About

Salesforce Sales Cloud holds the pipeline for many sales teams: leads, accounts, contacts, opportunities, and the tasks and events logged against them. Its REST API exposes every standard and custom object as an sObject resource under /services/data/vXX.X/, and Change Data Capture publishes an event when a record is created, updated, deleted, or undeleted.

Through Fibric, an operator watches those records and events, then proposes a change, such as a stage move, a reassignment, or a follow-up task, for a person to approve. Each approved change is written once and leaves a receipt: what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Salesforce Sales Cloud and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Lead, Account, Contact, Opportunity, Task, and Event records through sObject resources under /services/data/vXX.X/sobjects/
  • SOQL results through the Query resource, following nextRecordsUrl when a result set is returned in parts
  • Change Data Capture events for record creation, update, deletion, and undeletion on the objects you select
  • Org allocations from the Limits resource, including DailyApiRequests and DailyBulkV2QueryJobs with Max and Remaining
  • Custom objects and custom fields, since sObject resources cover standard and custom objects alike

Proposed actions

  • Target capability: propose an Opportunity stage or amount update through its sObject resource, shown to a person first
  • Target capability: propose a Lead or Opportunity owner change for the sales manager to approve
  • Target capability: propose a follow-up Task on a Lead, Contact, or Opportunity with a due date and owner

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Answer a new lead before it goes cold

    A change event fires when a Lead is created. The operator drafts a first reply and a Task for the owner, and a person approves both before anything is sent.

    With Lead Response

  • Flag opportunities that stopped moving

    Opportunities whose stage has not changed past a threshold you set are listed with the last activity date. The operator proposes an owner nudge or a stage review.

    With Stale Pipeline

  • Catch duplicate leads at intake

    New Leads are matched against existing Leads and Contacts by email and domain. The operator proposes a merge or a link for a person to confirm.

    With Duplicate Lead

  • Keep forecast and pipeline in step

    Opportunity amounts and close dates are compared with the committed forecast. Variances beyond your tolerance land in a weekly note with the records that moved.

    With Forecast Variance

Requirements

  • An org on Enterprise, Performance, Unlimited, or Developer Edition, or Professional Edition with the API access add-on
  • A user with the API Enabled permission, or a Salesforce Integration user license for API-only access
  • An external client app configured for OAuth 2.0; creating new connected apps is restricted as of Spring '26
  • Change Data Capture turned on for the objects you want events from
Authentication
An external client app, or an existing connected app, authorized through an OAuth 2.0 flow; REST API accepts the access token in the Authorization header as a Bearer token.

Limits

  • API requests are allocated per org per 24 hours; the Limits resource reports DailyApiRequests as Max and Remaining
  • Without an add-on, Change Data Capture allows 5 selected entities and 50,000, 25,000, or 10,000 delivered events per 24 hours by edition
  • A change event message over 1 MB is not delivered and is replaced by a gap event
  • Change Data Capture is listed for Enterprise, Performance, Unlimited, and Developer editions only

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Salesforce Sales Cloud ↗

Questions and answers

Which Salesforce editions can Fibric connect to?
Enterprise, Performance, Unlimited, and Developer Edition orgs have API access by default. Professional Edition can add API access as an add-on. The calling user needs the API Enabled permission, or an API-only Salesforce Integration user license.
Does the connector poll, or does Salesforce push changes?
Both paths are documented. Change Data Capture publishes create, update, delete, and undelete events for selected objects. For objects outside that set, or for history loads, the connector runs SOQL through the Query resource and follows nextRecordsUrl.
What happens if the org hits its daily API allocation?
The Limits resource returns DailyApiRequests with Max and Remaining. The connector reads it and paces history loads. Anything that cannot be fetched inside the allocation is marked missing rather than guessed.
Ask about Salesforce Sales Cloud

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Salesforce Sales Cloud through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy