Skip to main content

​
Overview

Before using this tool group, save a Salesforce connection in Config -> Connections. See Salesforce for OAuth, server-to-server, and merge opt-in settings.Merges are permanent — Salesforce repoints child records and deletes the losers. Agents can preview and submit a proposal to Action Review, but they cannot approve their own proposal. When review_required is true, a genuinely authenticated human must approve it through Action Review before execution. If Salesforce refuses the single merge request, the outcome is not_applied; an uncertain provider response is reconciliation_required and must not be retried. See the CRM merge API outcome contract.

​
Tool Name

​
Purpose

The salesforce_connector_tools group integrates Genesis with Salesforce CRM. Query records with SOQL, inspect object metadata, create, update, upsert, and delete records, and run the Action Review-governed merge workflow for duplicate Lead, Contact, and Account records.

​
Functions Available

  1. salesforce_connector: Bounded Salesforce reads, record mutations, and merge preview / request / execute actions.

​
Input Parameters

​
salesforce_connector

Parameters
Read-only connections: When the connection locator sets read_only to a truthy value, or access_intent to read or read_only, write and merge actions are refused.Merge opt-in: preview_merge, request_merge_approval, and execute_merge require merge_enabled on the connection locator and a valid merge_survivorship_policy JSON object. See Salesforce.Deleting a Lead, Contact, or Account: an agent’s delete_record of one of these types goes to Action Review, because updating one record, moving its related records, and deleting the other has the same effect as a merge. Object names are matched case-insensitively. The agent’s call deletes nothing and returns pending_review: true; a person must approve the request in Action Review, and Genesis then sends the one delete. Tell the user it is waiting for approval; do not retry the call or reach the same result another way. A person always decides these requests, whatever the Action Review policy says. Deletes of other object types, and every create, update, and upsert, run at once as before.
Merge workflow: Always follow preview_merge → request_merge_approval → Action Review → execute_merge. A proposal ID beginning with ap_ identifies an Action Review proposal. If review_required is true, an authenticated human must approve it in Action Review; when it is false, proceed to execution. There is no unmerge. If execution times out or the transport fails, the merge may already have succeeded in Salesforce — reconcile state instead of retrying blindly.If the governed merge is refused before its first write, execute_merge returns the handler’s refusal reason and optional detail; see the Action Review response contract.
Example — SOQL query
Example — merge preview

​
Use Cases

  1. Inspect CRM data — soql_query, get_record, or describe_object when a user asks about Salesforce accounts, leads, or contacts.
  2. Update a record — update_record or upsert_record when a workflow should write back to Salesforce.
  3. Duplicate review — preview_merge to show what an Account, Lead, or Contact merge would do before any write.
  4. Governed merge — request_merge_approval after preview, then inspect the returned review_required value; if it is true, a human approves the Action Review proposal, then execute_merge with the returned approval_id.