Integrations / Salesforce
Salesforce
Salesforce CRM platform for managing accounts, contacts, leads, opportunities, and cases
OAuth 2.0
Indexes
Actions
Events
What Telara does
Capability matrix
Before you connect
Prerequisites
A Salesforce org.
A user who can approve connected apps, usually an admin.
Vendor setup
Get the credential
1
Click Connect in Telara
Settings → Integrations → Salesforce. Approve access in Salesforce.
2
Confirm the org
Sandbox and production are different. Connect the org you mean.
Permissions Telara requests
- apiOAuth 2.0
- refresh_tokenOAuth 2.0
In Telara
Connect in Telara
OAuth 2.0
In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.
Fields Telara asks for
- Instance Url
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Object schema | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Object schema | Up to 1 day | Removed records disappear on the next full sync |
Data handling
Permissions & data handling
The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.
Excluded from semantic search: Object schema.
After connect
Verify it worked
This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.
Honesty
Known limitations
API-disabled profiles connect and then return nothing. Check the authorizing user’s profile if the graph is empty.
Experience Cloud / community users are usually the wrong identity for this connector.