Ssyncingbeam.app

guides

Salesforce

Validation pending

Production setup or live validation is incomplete. Contact us before using these setup instructions.

The Salesforce adapter is implemented, including OAuth, collection, scheduling, and storage. Production OAuth credentials are not configured, and a live production sync has not been verified.

What it collects

The adapter uses aggregate SOQL for lead, opportunity, stage-entry, and campaign-member metrics. It does not fetch Contact/person rows or retain source Lead or Opportunity IDs. It does fetch and store Campaign IDs and names, and processes customer-controlled labels such as lead source, status, and stage name. Keep personal data out of these labels.

  • Daily lead counts by source and status.
  • Monthly opportunity counts and amounts by stage, campaign, and currency.
  • Current open-pipeline snapshots.
  • Campaign rollups and campaign-member counts.
  • Daily stage-entry counts and amounts from OpportunityHistory.

Permissions

The connector requests api and refresh_token OAuth scopes. The API scope is broader than read-only access. SyncingBeam’s adapter uses describe and SOQL query operations; configure a dedicated integration user with the minimum object and field permissions required.

Salesforce recommends External Client Apps for new integrations. Existing Connected Apps can still be used, but creation of new ones is restricted. See Salesforce’s current authorization guidance ↗.

What the data cannot establish

Current pipeline snapshots and aggregate stage entries do not provide record-level opportunity timelines or deterministic marketing attribution. Campaign-to-UTM comparisons require explicit mappings; similar names alone do not establish a match.

Amounts remain separated by currency. The adapter checks the account’s currency configuration during each sync and uses a bounded 24-month history. Changes outside the recomputation window may not be reflected. Oversized aggregate result groups fail rather than being silently treated as complete.

Preparing a connection

  1. Contact us to arrange a sandbox validation and confirm the API objects and fields your account exposes.
  2. Configure the approved OAuth app, callback, and integration-user permissions.
  3. Complete authorization from the intended SyncingBeam workspace and client.
  4. Verify token refresh, a successful collection, currency handling, and the response to revoked access before production activation.

Connection failures

Missing authorization or revoked credentials require reconnection. Quota exhaustion schedules a retry. A configuration or scale error needs investigation before the data can be treated as complete. These behaviors are implemented; production account validation remains outstanding.