Salesforce connector
Query and manage accounts, contacts, leads and opportunities
Governed actions
24
individual actions a WorkStream step can call
2
batch operations for bulk reads and writes
Authentication
OAuth 2.0 (authorization code)
A named user signs in to the vendor and grants VeroTX access. Refresh tokens are rotated and stored in the platform credential vault.
Requires an interactive sign-in and consent screen from an authorized user of the vendor account.
Configuration fields
- Client ID
- Client secret
- Redirect URL
- Requested scopes
- Vendor account or instance
How VeroTX governs the Salesforce connector
- Credentials are held in the platform credential vault. Agents never see them.
- Every call runs as a step in a versioned WorkStream Playbook, so the rules that apply are the rules that were published.
- Actions that cross a policy threshold stop at a tollgate and wait for the named approver.
- Each call is written to the Execution Ledger with the inputs, the result and the Playbook version in force.
What the Execution Ledger records for a Salesforce call
- 1
Credential resolved
OAuth 2.0 (authorization code) credential released from the vault to the connector runtime. The step never sees the secret.
- 2
Action called
A WorkStream step called Salesforce with the inputs recorded on the step, under the Playbook version in force.
- 3
Policy evaluated
Thresholds on the step were checked. Anything over the limit stops at a tollgate and waits for the named approver.
- 4
Result written
The response from Salesforce, the timing and the Playbook version were written to the Execution Ledger.
Where this connector is used
Customer, deal and pipeline data used to validate counterparties and drive quote to cash.
Other crm connectors
See it run
Connectors only matter inside a WorkStream. The product tour walks a request from intake through a tollgate to a recorded result.