Bob with Salesforce: keep the CRM current from the work itself

Matthew, founder of Bob · Published July 30, 2026

Short answer

Connect Salesforce and Bob can use the authenticated CRM actions exposed by the live catalog connection. Salesforce offers several data APIs for object records and queries, including REST and composite operations. Salesforce's own data API overview explains why the right interface depends on the job.

Bob does not claim every Salesforce endpoint. His access is limited by the connection's action set, the connected user's profile and permission sets, sharing rules, field-level security, OAuth scopes, and tenant configuration.

Five useful Bob and Salesforce workflows

1. Prepare an account brief

"Brief me on the Contoso account before tomorrow's call. Include the opportunity stage, recent Outlook thread, open Jira issues, and unresolved risks."

Salesforce provides the commercial record while the other connections provide the current operating reality.

2. Find pipeline gaps

"List opportunities closing this month that have no next step, stale activity, or an amount mismatch with the forecast workbook."

Start read-only and verify the filters against a Salesforce report before scheduling it.

3. Prepare a CRM update from the conversation

"Based on this approved renewal decision, prepare the Salesforce stage and close-date changes. Show me every field before updating."

Bob can inspect whether the live connection supports the required record update and asks before writing.

4. Reconcile Salesforce and a spreadsheet

"Compare Salesforce renewals with the Excel tracker. Explain every mismatch and tell me which system appears newer."

The comparison is safer than blindly syncing both directions. Ownership should be decided field by field.

5. Deliver a weekly revenue brief

"Every Monday, summarize stage movement, slipped close dates, and deals without a next action. Post only material changes."

Bob's schedule can deliver the brief in Slack when the necessary read actions are available.

Connection scope and setup

1. Ask Bob in Slack to connect Salesforce.
2. Open the hosted OAuth flow and sign in to the intended Salesforce org.
3. Review the requested access and connected-user permissions.
4. Return to Slack and retry the original CRM request.

Salesforce is a workspace-scoped catalog connection in Bob today. Use a dedicated least-privileged identity or a carefully chosen team identity. Do not connect a system administrator simply to avoid configuring the right permissions.

Limits worth knowing

• Available actions vary. Bob discovers the catalog action set at run time.
• Salesforce permissions are layered. Object, field, sharing, record, and connected-app controls all matter.
• Custom orgs need precise requests. Custom objects, validation rules, flows, and required fields can change what a write requires.
• Writes ask by default. CRM updates can affect forecasts and customer work, so review the exact record and fields.

FAQ

How does Bob connect to Salesforce?

Through a hosted OAuth catalog connection that is workspace-scoped today.

What can Bob do with Salesforce?

Bob uses the authenticated actions exposed by the live connection and allowed for the connected Salesforce user.

Does Bob ask before updating Salesforce?

Yes. Creating or changing CRM records asks by default.

Can Bob bypass Salesforce permissions?

No. Salesforce and OAuth permissions continue to govern everything the connection can access.

Start with a report someone already checks

Have Bob reproduce one account or pipeline view and verify it against Salesforce. Then connect Outlook, Excel, Gmail, or Google Sheets when the decision spans systems.