Skip to main content
The Salesforce integration retrieves and updates customer party data and manages activities (Task and Event) in Salesforce CRM through the Salesforce API v56.0. Grand Central delivers the integration as outbound (synchronous) connectors. For setup steps, see Get started.

Configuration properties

Common properties

Set these properties in values.yaml. They apply across Salesforce connectors.

gc-salesforce-activity-connector

Set these properties in activity-v0.values.yaml. They configure create activity (POST /activities), update activity (PUT /activities/{activityId}), get activities by party (POST /activities/partyId), and get activities by employee (POST /activities/employeeId).
Replace regex.party-id.pattern and regex.party-id.failure-message with regex.salesforce-record-id.pattern and regex.salesforce-record-id.failure-message. Migrate any tenant overrides in activity-v0.values.yaml before deploying a connector build that includes get-by-employee.
Create and update map Grand Central activity payloads to Salesforce Task or Event using JOLT specs in gc-salesforce-activity-connector, including SDK enrich transforms for Task recurrence bitmask/month and Event duration, start time, and RRULE. For get-by-party and get-by-employee, the connector runs SOQL against Task and Event using the field lists you set in configuration, then maps results to the Grand Central activity response contract. Set the recurrence map properties in activity-v0.values.yaml for create and update; they aren’t bundled as defaults in the connector JAR.

SOPS secrets

The connectors read the Salesforce OAuth 2.0 credentials from the salesforce SOPS secret. Which secret fields are required depends on gc.sf.client.authType (USERNAME_PASSWORD by default; also REFRESH_TOKEN or CLIENT_CREDENTIALS).

Supported operations

The Salesforce connectors expose party and activity operations of the Grand Central Unified API. For the operation-to-endpoint tables, see Overview. For the full contract, see the unified API specifications.

Get activities by party request fields

POST /activities/partyId accepts the following fields in the request body (from the Grand Central Unified API). For the full contract, see the unified API specifications.

Get activities by employee request fields

POST /activities/employeeId accepts the following fields in the request body (from the Grand Central Unified API). For the full contract, see the unified API specifications. Pagination and date filtering behave the same as get-by-party. The connector queries Task and Event in parallel for both get operations, merges the results (Tasks then Events), then applies the from/size page slice. If from multiplied by size exceeds the fetch limit of 2000, the connector returns Grand Central error GC051.

Events

gc-salesforce-party-connector and gc-salesforce-activity-connector are synchronous and don’t publish or consume events.

Error mapping

The connectors map Salesforce error codes to Grand Central status codes. For the full list, see Error codes.

Dependencies

  • Salesforce API v56.0 (outbound), reachable through the environment configured by gc.sf.client.loginUrl.
  • salesforce-connector-sdk (shared HTTP configuration, Salesforce OAuth handling, and activity JOLT enrich transforms).