Connector
Salesforce
Read Salesforce objects with SOQL, and write records back.
Settings
What the connection form asks for. Every connection has a Staging side, which it needs, and an optional Production side with values of its own; both ask for the same settings.
| Instance URL | Your org's domain, e.g. https://acme.my.salesforce.com. |
| API version | Blank uses 60.0. |
| Method | Client credentials suits a connected app; the password grant is for a username with the security token appended to the password. Choices: OAuth2 client credentials; Username + password + security token. |
| Consumer Key (Client ID) | |
| Consumer Secret | Stored encrypted, and never shown again after you save it. |
| Username | Shown when Method is Username + password + security token. |
| Password + security token | The password with the security token appended, no separator. Shown when Method is Username + password + security token. Stored encrypted, and never shown again after you save it. |
Testing the connection
Test exchanges the credentials for a Salesforce access token. That exchange is the check: a wrong key, secret or password fails.
Good to know
- Two ways to sign in: OAuth2 client credentials for a connected app, or a username with the security token appended to the password.
- The output's delete sends records to the Recycle Bin; Trinium never hard-deletes in Salesforce.