Salesforce

Connect Salesforce and Expertise becomes a colleague inside your CRM. It can find and summarize records, answer pipeline questions with real SOQL, inspect your schema, run and even build reports, and, with your explicit approval, create and update records. This is a native integration built and maintained by Expertise (not a third-party relay). Every call goes straight to your org’s Salesforce REST API using OAuth credentials scoped to the connected user.

​

What you can ask

“How many leads did we create this quarter vs last quarter?”

“Find the contact with email jane@acme.com and show her account, title, and open opportunities.”

“Which opportunities close this month with no activity in the last 14 days?”

“Create a summary report of open opportunities grouped by stage, in the Sales Ops folder.”

“Update the Acme renewal opportunity to Negotiation and set the close date to Aug 15.” (asks for approval first)

“Every Monday morning, message me the pipeline changes from last week.” (scheduled task)

​

Connecting

1. Open Connections in the dashboard and click Salesforce → Connect.
2. Sign in at login.salesforce.com and approve the request.
3. That’s it. Ask Expertise something about your CRM to confirm it’s live.

Expertise requests the api, refresh_token, id, and web OAuth scopes. Two things to know about access:

• Your permissions are the ceiling. Expertise acts as the connected Salesforce user. Field-level security, sharing rules, and profile permissions all apply exactly as they do for you, Expertise can never see or change anything you can’t.
• Tokens refresh automatically. The connection stores an encrypted refresh token, so you won’t be asked to reconnect when the access token expires. Disconnect any time from the Connections page, or revoke the app under Setup → Connected Apps in Salesforce.

​

Reading: records, queries, and metadata

Read tools run without approval, they can never change your org. Custom objects work everywhere: anywhere a tool takes an object name, API names like Custom_Object__c are fine, and Expertise will describe_object first when it isn’t sure about your schema.

​

Reports

Expertise speaks the full Salesforce Reports & Dashboards REST API: Report creation is typed and validated: Expertise passes a name, report type, detail columns, and an optional group_by, and the connector builds the Salesforce report metadata, validating the fields against your live report type before posting. It also absorbs two classic Salesforce sharp edges for you: report names longer than 40 characters are rejected up front, and a grouped field is automatically kept out of the detail-column list (Salesforce errors when a grouping field is also a selected column).

​

Writing: always behind an approval

These six tools change data in your org, and every call pauses for an approval card in chat showing the exact object, record, and field values before anything is sent:

• create_record (POST /sobjects/{object})
• update_record (PATCH /sobjects/{object}/{id})
• upsert_record (PATCH by external ID); set create_if_missing: false for update-only behavior that will never create a record
• delete_record (DELETE /sobjects/{object}/{id})
• create_report and update_report, as above

Two extra guardrails apply beyond the approval itself:

• Limit preflight. Before proposing create-style work, Expertise checks get_org_limits; if your API or data storage limits are exhausted it tells you instead of queueing a doomed approval.
• Validation-first writes. Object and field names are checked against describe_object metadata before the approval card is shown, so what you approve is what will succeed.

​

Troubleshooting