Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.partneros.ai/llms.txt

Use this file to discover all available pages before exploring further.

Connecting Salesforce lets PartnerOS keep your partner records in sync with your CRM automatically. Changes flow in both directions: updates you make in PartnerOS push to Salesforce, and changes your team makes in Salesforce pull into PartnerOS using Change Data Capture for near-instant delivery.

​
Prerequisites

Before connecting, confirm the following:
  • You have a Salesforce account on Professional, Enterprise, Unlimited, or Developer edition. API access is required; Salesforce Essentials does not include API access.
  • The user who completes the OAuth flow must have the API Enabled permission in their Salesforce profile.
  • The user needs at least Read access on the objects you want to sync (Account, Contact, Opportunity, Lead).
  • For bidirectional sync, the user also needs Create and Edit access on those objects.
  • You are a PartnerOS Owner or Admin — only Owners and Admins can connect integrations.

​
Connect Salesforce

1

Open Settings > Integrations

In PartnerOS, navigate to Settings > Integrations. You will see a card for Salesforce with a Connect Salesforce button.
2

Start the OAuth flow

Click Connect Salesforce. You are redirected to the Salesforce login page. Sign in with the Salesforce user that has API access.
3

Grant permissions

Salesforce shows the consent screen listing the permissions PartnerOS is requesting. Click Allow to grant access. Do not remove any requested permissions — missing scopes will cause sync failures.
4

Confirm the connection

After granting access, you are redirected back to Settings > Integrations. The Salesforce card should show Active status with your Salesforce org ID displayed.
5

Let PartnerOS discover your schema

PartnerOS immediately reads your Salesforce object schema (fields and their types). This takes a few seconds. You will see the object count and total field count update on the connection card once discovery completes.

​
What syncs

PartnerOS discovers and syncs the following Salesforce objects by default:
ObjectDescription
AccountPartner company records
ContactIndividual contacts at partner companies
OpportunityDeals and pipeline records
LeadInbound leads associated with partners
In addition to these standard objects, PartnerOS also discovers any custom objects (those ending in __c) and custom metadata types (ending in __mdt) that are queryable in your org. These appear in the field mapping configuration so you can choose whether to include them.
Not every discovered field is mapped by default. You choose which fields to sync during the field mapping step. PartnerOS only reads or writes the fields you explicitly include in your mapping configuration.

​
Set up field mappings

Field mappings tell PartnerOS which Salesforce field corresponds to which PartnerOS field for each object.
1

Open the connection detail

Click the Salesforce connection card in Settings > Integrations to open the detail page.
2

Select an object pair

Choose the PartnerOS object (for example, Partners) and the Salesforce object (for example, Account) you want to map together.
3

Run AI mapping suggestions

Click Suggest Mappings. PartnerOS uses AI to compare field names, labels, and types between the two objects and produces a list of suggested pairings, each with a confidence score.
4

Review and confirm suggestions

Each suggestion is shown with its confidence level:
  • Auto-mapped — high confidence; these are applied automatically but you can override them.
  • Suggested — the AI has a candidate but wants your confirmation. Click Confirm to accept or pick a different CRM field from the dropdown.
  • Unmapped — no confident match found. Assign a CRM field manually or mark the field as Ignored if you do not want to sync it.
5

Set sync direction

For each object pair, choose a sync direction:
  • Bidirectional — changes flow both ways (recommended for most objects)
  • PartnerOS to Salesforce — PartnerOS is the source of truth
  • Salesforce to PartnerOS — Salesforce is the source of truth
6

Save and trigger a sync

Click Save Mappings. Then click Trigger Sync on the connection detail page to run the initial backfill and confirm data flows correctly.
If you override an AI mapping suggestion, PartnerOS records your correction to improve future suggestions for your organization. Mapping corrections are logged in the audit log.

​
Sync behavior

​
Bidirectional sync

With bidirectional sync enabled, PartnerOS applies a conflict resolution policy when the same field is updated in both systems between syncs. You configure the policy per field mapping rule:
  • PartnerOS wins — the PartnerOS value overwrites the Salesforce value
  • CRM wins — the Salesforce value overwrites the PartnerOS value
  • Newest wins — whichever record has the more recent LastModifiedDate wins

​
Change Data Capture (CDC)

For incremental sync, PartnerOS uses Salesforce Change Data Capture. When a record changes in Salesforce, PartnerOS receives a notification within seconds rather than waiting for a scheduled poll. This keeps partner data fresh without consuming large numbers of Salesforce API calls. CDC must be enabled for each synced object in your Salesforce org:
  1. In Salesforce, go to Setup > Integrations > Change Data Capture.
  2. Select the objects you are syncing (Account, Contact, Opportunity, Lead).
  3. Click Save.
Salesforce retains CDC events for only 3 days. If your PartnerOS connection is inactive for more than 3 days, CDC events for that period will be lost. PartnerOS will fall back to polling-based sync and you should trigger a full backfill to re-establish the baseline. See troubleshooting CDC issues.

​
API rate limits

Salesforce enforces a rolling 24-hour API call limit that varies by edition. PartnerOS monitors how many calls remain and warns you in the Integration Health dashboard when fewer than 10% of your daily allocation is left. If you approach the limit, pause active syncs and wait for the window to reset before resuming.

​
Refresh schema after field changes

When a Salesforce admin adds, removes, or renames fields, your existing field mappings may become stale. PartnerOS detects schema changes automatically within 24 hours, but you can trigger an immediate refresh:
  1. Open the connection detail page in Settings > Integrations.
  2. Click Refresh Schema.
  3. Review any field mappings that now show a warning — they reference fields that may no longer exist or have changed.
  4. Update or remove affected mappings, then trigger a manual sync to confirm everything is working.
After a Salesforce admin makes schema changes, it is good practice to click Refresh Schema immediately rather than waiting for automatic detection.

​
Disconnect Salesforce

To remove the Salesforce connection, open the connection detail page and click Disconnect. This stops all sync operations and removes the stored access tokens. Existing partner records in PartnerOS are not deleted. The action is logged in the audit log.