Salesforce is not a current native connector. Threetone does not provide its installation or consent flow. The steps below prepare an external service and tool contract.
Prepare the CRM workflow
You need an organization administrator, the intended application authorization model, and an explicit object-and-field allowlist.1
Review OAuth and user access
Salesforce’s OAuth scope reference distinguishes
api access from the broader full scope. Request the access needed for the operation and review the connected user’s permissions. Avoid selecting broad scopes merely to bypass a permissions error.2
Bind the organization and record
Resolve the organization and record ID before reading. Return only allowed fields and relationships. Require review when an email address or name matches multiple records. Keep production and sandbox credentials and identifiers separate.
3
Review a field-level change
Show the record, current values, and proposed replacements. Confirm ownership changes and customer-visible effects separately. Re-read stale state before writing. If the response is uncertain, inspect the record before retrying rather than assuming the update failed.
Frequently asked questions
Does the api scope grant access to every Salesforce field?
Does the api scope grant access to every Salesforce field?
Do not treat a scope as a substitute for organization, object, and field permissions. Review the actual account and operation before returning data.
Should a missing record be created automatically?
Should a missing record be created automatically?
No. A missing or inaccessible lookup result is not authorization to create a new record. Review duplicates and required fields in a separate creation workflow.