Salesforce integration

The Salesforce connection is designed for the Accounts, Contacts and Opportunities scope on Salesforce Hosted MCP. Brings account, contact and opportunity data to a CRM assistant through Hosted MCP. That means an assistant uses the permitted live-system context instead of guessing from a document. The result still depends on the freshness of the source system and the permissions granted to the connection.

A useful request makes clear which record is needed for which team. For this connection, a reliable flow is identifying the account, contact or opportunity in the connected org, then assessing the result under Salesforce field security and sharing rules. This makes filters and source records easier to inspect than asking for a broad list to be summarised.

tools that create, update or delete records require single-use confirmation; Salesforce permissions and KobiGPT department grants both apply. This is more than a technical detail: an incorrect action in a financial, customer, production or legal record can have real consequences. Reading a result and changing an external system are not the same level of authority.

Before rollout, decide which assistants and departments can see this data. If a result is unexpectedly broad, reduce the access scope; if data is absent, do not let the assistant invent the missing record. The underlying system record and the accountable owner remain the final check for every consequential result.

connects to the ready Salesforce Hosted MCP server with OAuth2 authorization code and is distinct from the self-hosted REST option. At setup, use a separate connection identity with least privilege so the accessible data does not exceed the operational need. For OAuth connections review the consent screen; for bearer connections review token scope, storage and ownership with the responsible team.

hosted CRM scope and 0.1 Kobi Credits per call. This statement comes from the catalog or tool definition; no extra count is invented for a vendor-managed changing surface. During a pilot, observe real questions, returned records, confirmation steps and unnecessary calls. That evidence makes cost visible and exposes over-broad permissions early.