Skip to main content
Before you configure the Salesforce Connector, make sure you have the following credentials and connectivity:
  • Follow the steps in Getting started.
  • Salesforce access: An active account in the Salesforce production or sandbox environment.
  • Network connectivity: Verify that your network routes traffic between the Salesforce environment and Grand Central iPaaS. For supported options, see Network connectivity.

​
Configuration guide

Follow these steps to initialize and authorize your Salesforce Connector.

​
1. Establish connectivity

Share connectivity details between Grand Central and Salesforce as described in Network connectivity.

​
2. Salesforce authentication

The Salesforce Connector uses OAuth 2.0 authentication for API access. To configure authentication, create a Secrets Operations (SOPS) secret. For more information, see How to create SOPS.
To share credentials between Salesforce and Grand Central, consider using 1Password.

​
3. Environment configuration

To initialize the Salesforce Connector, define the required environment variables in your gc-applications-live repository. These variables are stored in values.yaml for configuration common to all connectors, and in the following files for connector-specific configuration:
ConnectorPropertyDescription
gc-salesforce-party-connectorparty-v0.values.yamlOutbound party v0 connector for CRM operations
gc-salesforce-party-connectorparty-v2.values.yamlOutbound party v2 connector for CRM operations

​
Define common parameters

These variables are stored in values.yaml and are used across all Salesforce connectors:
ParameterDescriptionExample value
existingSecretNameReference to SOPS secret containing Salesforce credentials.salesforce
gc.sf.client.loginUrlLogin URL for Salesforce environment.https://login.salesforce.com
Store all sensitive credentials (client ID, client secret, username, password) in a SOPS secret. Never include credentials directly in values files.
The following example shows the values.yaml configuration: 
# Common Salesforce Configuration
# Place this in: values.yaml
connector:
  existingSecretName: salesforce
  properties:
    # Salesforce Connection Settings
    # gc.sf.client.loginUrl: <Salesforce_Login_URL>
  traits:
    knativeservice:
      minScale: 0
    logging:
      level: INFO

​
Define party v0 connector parameters

Configure the party v0 connector with secret reference (party-v0.values.yaml): 
# Salesforce Party v0 Connector Configuration
# Place this in: party-v0.values.yaml
connector:
  existingSecretName: salesforce
  traits:
    knativeservice:
      minScale: 0
    logging:
      level: INFO

​
Define party v2 connector parameters

Configure the party v2 connector with secret reference (party-v2.values.yaml): 
# Salesforce Party v2 Connector Configuration
# Place this in: party-v2.values.yaml
connector:
  existingSecretName: salesforce
  traits:
    knativeservice:
      minScale: 0
    logging:
      level: INFO
Place the values files at the following paths: 
iPaaS/azure/runtimes/{runtime}/values/gc-salesforce/
├── values.yaml
├── party-v0.values.yaml
└── party-v2.values.yaml

​
Testing your integration

To access the Unified API, include your Grand Central subscription key in the request header. If you don’t have a key, contact the Grand Central Support Team to request one.
HeaderValue
api-key<your_subscription_key>
Test the API using the Postman Collection.

​
Troubleshooting

If your connector isn’t responding as expected, check these common scenarios.
Cause: The Grand Central gateway cannot establish a handshake with the Salesforce endpoint. This typically indicates an upstream service outage at Salesforce or a network routing failure.Solution: Verify the operational status of the Salesforce environment. Check the Salesforce status page or contact Salesforce support. If the service is operational, contact Grand Central Support.
Cause: The request to Salesforce exceeded the configured timeout period. This may indicate performance issues at Salesforce or network latency problems.Solution: Verify the operational status of the Salesforce environment and check for any performance degradation. If the service is operational and performing normally, contact Grand Central Support.
Cause: The OAuth credentials provided during setup are incorrect, expired, or you lack the required permissions in Salesforce.Solution: Re-verify your credentials with your Salesforce administrator and ensure you have the required permissions. Contact the Grand Central team to update the connection credentials if needed.
Cause: The party ID (Salesforce contact ID) provided in the request is invalid or does not exist in Salesforce.Solution: Verify that the party ID is a valid Salesforce contact ID. Check that the contact exists in your Salesforce org and the ID format is correct.
Cause: The number of incoming requests exceeds the defined threshold for your subscription tier. This “429 Too Many Requests” response protects the stability of the Grand Central and Salesforce infrastructure.Solution: Review your app’s request patterns to identify unexpected spikes. If you need higher throughput, contact the Grand Central team to request a higher rate limit.

​
Need more help?

Contact support

Contact the Grand Central team for help with environment setup or rate limit increases.