Salesforce
Salesforce Event Monitoring + Setup Audit Trail. Pulls EventLogFile entries (logins, API usage, report exports) and SetupAuditTrail (admin config changes).
- Connector id:
salesforce - Category: saas
- Authentication: OAuth
Configuration
| Field | Label | Type | Required | Default | Notes |
|---|---|---|---|---|---|
instance_url | My Domain URL | string | yes | — | — |
client_id | Connected App Consumer Key | string | yes | — | — |
client_secret | Connected App Consumer Secret | secret | yes | — | encrypted at rest |
refresh_token | Refresh Token | secret | no | — | encrypted at rest · Provided automatically when you connect via OAuth. |
client_secret, refresh_token are encrypted at rest by the credential vault before the row is written, and decrypted only at poll time. The value is never logged and never returned by the API — a read of the saved connector shows the field as set, not its contents. See credential vault.
Setup
- In the console, go to Connectors → Add connector and pick Salesforce.
- Fill in the fields above and run Test connection. The test is read-only and does not save anything.
- Save. Polling starts on a jittered schedule within about a minute; the connector row shows
last_synconce the first poll completes.
last_sync stays emptyThe first poll is the honest signal that the credential works. A connector that saves cleanly and never syncs usually means the credential lacks a scope the vendor requires for reads — check the connectors service log for the vendor's own error, which is passed through verbatim rather than summarised.
Vendor-specific setup notes go here: which console page issues the credential, which scopes to grant, rate limits, and anything the schema cannot express. This section is preserved when the page is regenerated.