Skip to content
Help Center
Submit a request Sign in

Configure Salesforce synchronization

Salesforce synchronization connects customer, contact, product and case information to the support workflow. Configure each object independently so import and export directions reflect the ownership of your data.

Applies to: Supportbench Core. Location: Settings → Integrations → Salesforce. Access and available controls depend on your role and account capabilities.

Before you begin

  • Confirm a compatible Salesforce connected app and that the organization permits the username-password authentication used by the current Core connector. New connected-app creation is restricted by Salesforce; do not substitute another authentication flow or weaken policy to follow older setup instructions. See the Salesforce API access and compatibility guide at https://support.supportbench.net/ar-20/.
  • Confirm you can administer integrations and have access to the intended provider workspace.
  • Record the existing connection and routing choices. Use a representative test record before enabling broad synchronization.
  • Obtain credentials through your approved provider process; do not place secrets in articles, screenshots or support messages.

Configure and verify

  1. Open Settings → Integrations → Salesforce. Confirm the intended Environment and authorized integration identity before entering Consumer Key, Consumer Secret and Username/Password with security token.
  2. Choose Save Changes for the intended connection settings, then Test connection. The test checks the current form without saving it; if you change a value during diagnosis, save the correction separately. Resolve the provider error before enabling additional flows.
  3. Start with the needed Company Import flow. Review Only active, object filters and field mappings, and save the settings. Confirm source/destination field identity and the customer records included and excluded by the filters.
  4. Use Refresh status and inspect the existing synchronization cycle and representative records. Synchronize now does not directly enqueue a new job; read its response and verify the eventual result rather than interpreting the click as completed synchronization.
  5. Configure Contact Import or Import + Export only after satisfying the Company dependency and reviewing field ownership. Verify a representative Company/Contact pair before adding other object flows.
  6. For Case Export, satisfy the displayed Salesforce Case/Task field requirements, choose the intended lookback and mappings, save, and inspect an approved representative result. A working connection alone does not validate the exported data.
  7. Use Resynchronize all only after reviewing its wider scope: it marks enabled objects and Data Table domains for full synchronization on the existing cycle. It is separate from verification and is not a one-record retry.

Settings reference

Connection and operating controls

SettingWhat it controlsHow to choose
EnvironmentSelects the Salesforce environment for the connection.Confirm whether the credentials belong to the intended production or test environment.
Consumer Key / Consumer SecretApplication credentials for the selected Salesforce connection.Use the approved connected application and enter secrets only in the credential fields.
Username / Password and security tokenSalesforce username plus the password immediately followed by its security token. Stored secrets are not displayed; blank password/secret fields preserve the configured values.Use the authorized integration identity. Reveal controls show newly entered values only.
Test connectionChecks the current form’s provider connection without saving its settings.Save and verify the intended connection before enabling flows. A test of changed form values does not save those changes.
Failure notification emailRecipient for connection/synchronization failures.Use a monitored operational mailbox.
Refresh statusReloads current integration status.Review it after save and synchronization.
Synchronize nowUses the existing service cycle; the native action does not directly enqueue a new job.Save intended settings first, read the response, then verify synchronization status and representative records.
Resynchronize allMarks enabled object and data-table domains for full synchronization on the existing service cycle.Review the full scope and mappings before confirming. It is not an immediate one-record retry.

Objects, filters and mappings

SettingWhat it controlsHow to choose
CompanyDisabled or Import, with Only active and optional filters.Confirm Salesforce is the source for the selected company fields.
ContactDisabled, Import or Import + Export; Only active and filters are available.Review the Company dependency and avoid conflicting writers.
Asset / Product and Company AssetDisabled or Import; Company Asset has a related-company dependency.Verify the parent customer and product mappings first.
CaseDisabled or Export, with a lookback of 1, 7, 14, 30, 60 or 90 days.Choose the smallest lookback that covers the intended records.
Object filtersUp to two optional filters for supported objects. Rows combine with AND; comma-separated values within a row combine with OR.Use clear inclusion rules and test records on both sides of each boundary.
Field mappingsMaps Supportbench fields to Salesforce fields for the selected object.Check type, identity and required-field compatibility.
Data Table tabsUp to six configured tables, with Enabled, Salesforce object, relationship and mappings.Verify the selected relationship identifies the intended parent.

Required case/activity fields

SettingWhat it controlsHow to choose
Case fieldsSetup guidance lists bench_case_id__c, bench_owner__c, bench_queue__c and bench_outcome__c.Review and satisfy the displayed Salesforce requirements before exporting cases.
Task fieldsSetup guidance lists bench_activity_id__c, bench_activity_type__c, bench_email_to__c and bench_email_cc__c.Use the prescribed fields so activities can be correlated accurately.

Behavior to know

  • Company, Contact, Product, Company Asset and Case options have different supported directions. Do not assume every object is bidirectional.
  • Provider compatibility was reviewed on 28 October 2026. Existing compatible connections and new connection setup have different prerequisites; review ar-20 before creating credentials.

Recommended use

  • Identify an operational owner and a monitored failure-notification address. Document which system owns each mapped field before enabling both directions for Contacts.
  • Enable and verify the smallest necessary object flow first. Compare included and excluded records and related Company/Contact identity before broadening scope.
  • Review saved settings, mapping compatibility and existing data before Resynchronize all. Retain evidence of the initial result and investigate partial failures before repeating a broad operation.

Worked example: bring customer organizations into support with reliable Contact links

  1. A B2B support team needs the approved Salesforce customer organizations visible in Supportbench. Confirm the production or test Environment and authorized connection identity. Test the current form’s connection, resolve errors, and save the credentials/settings before relying on them.
  2. Enable Company Import for the intended population, review filters and map the actual required identity and business fields. Start with a controlled representative scope and save. Do not map a support-maintained field to a competing source without deciding which system should own it.
  3. Inspect Refresh status and the existing service cycle, then compare a representative Company on both sides. Check identity, selected field values and an excluded record. A successful test connection is not evidence that the Company was imported correctly.
  4. After the Company dependency is satisfied, configure the required Contact direction and mappings. Verify a Contact is associated with the correct Company and inspect the actual mapped fields. Keep Import + Export off unless the operation needs both directions and the field-ownership rules are clear.
  5. Only then consider Case Export, with the required Salesforce Case/Task fields and a deliberate lookback. Inspect a controlled Case and its activity correlation rather than treating the entire integration as verified by one Company match.
  6. If a record is missing, inspect enabled flow, filters, saved mappings, dependency and synchronization status. Reserve Resynchronize all for a reviewed full-synchronization need; it marks enabled domains for the existing cycle and does not provide an immediate isolated fix.

Troubleshooting

ProblemWhat to check
Connection verification failsConfirm Environment, approved identity and current application credentials. Review the provider error. A blank stored secret/password preserves its saved value; it does not prove the credential is current.
Verification succeeded but saved behavior did not changeVerification tests the form without saving. Save the intended settings and reopen them before checking the existing synchronization cycle.
A Company is missing or has incorrect fieldsCheck Company Import, Only active, object filters, field mappings and integration status. Compare a representative source record and the saved destination rather than broadening every filter.
Contact synchronization is unavailable or links the wrong organizationCheck the Company import dependency and actual Company identity/mapping first. Then review Contact direction, filters and required fields.
A Case or activity does not export as expectedCheck Case Export, lookback, mappings and the displayed required Salesforce Case/Task fields. Inspect status and a representative Case/activity pair.
Synchronize now did not immediately produce a recordThe action uses the existing service cycle and does not directly enqueue a new job. Inspect its response, Refresh status and representative records after processing.
Considering Resynchronize all for a single failed recordReview the enabled objects and Data Table domains first. This marks them for full synchronization on the existing cycle; diagnose a mapping or dependency issue before repeating broad processing.
  • Integrations → Use the data synchronization log
  • Organization → Configure agent roles and division access

For additional setup and usage context, see these related guides:

Was this article helpful?