Salesforce support

Last updated date:

Connect, reconnect, and troubleshoot Salesforce without sharing credentials or customer content through support channels.

1. Before you start

  • Choose the Salesforce organization and exact objects and fields Seedling should index.
  • Create a dedicated API-only execution user with read access only to that intended population.
  • Configure a Connected App or External Client App with the api OAuth scope and client-credentials flow.
  • Do not send Salesforce credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
Salesforce OAuthSalesforce's official OAuth and REST API authorization guide.

2. Connect Salesforce

  1. Enable the client-credentials flow and select the dedicated execution user in Salesforce.
  2. In Seedling, open Connections, select Salesforce, and choose personal or workspace scope.
  3. Enter the client ID and secret plus any non-default login URL, instance URL, API version, or organization label.
  4. Connect, confirm the verified organization ID, and allow schema and record synchronization to complete.

3. Authorization and connection problems

OAuth client rejected
Confirm client credentials are enabled, the app secret is current, and an approved execution user is assigned.
Object unavailable
Grant the execution user object Read permission and API visibility without adding write access.
Field missing
Check field-level security, record type, API name, and whether the field was removed or renamed.

4. Missing or delayed data

  1. Confirm the execution user can query the affected object and field through the REST API.
  2. Check organization sharing, ownership, roles, territories, queues, teams, and permission-set changes.
  3. Confirm the object remains in the configured population and the record is not represented by a processed deletion event.
  4. Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
  5. If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.

5. Rotate or replace access

Never use email or an ordinary support ticket to transfer the old or replacement credential.

  1. Rotate the Salesforce app client secret without changing the organization or execution user.
  2. Replace the client secret on the exact Seedling connection and confirm the same organization ID.
  3. Revoke the old secret after Seedling verifies the replacement.