Grok Bot + Salesforce

How a Bot connects

Connected app with OAuth, or Composio. Use a permission set that grants object access only for the routine's objects. Avoid the browser: Salesforce challenges datacenter logins and Lightning UI is slow for a Bot.

The Bot's identity

Integration User licence if you have one (cheaper), otherwise a standard user with a restricted profile. Never System Administrator. Don't reuse a human's login. If you did, see shared computer cleanup.

Routines we've run

• Nightly — opportunities past close date: list, draft owner nudge, post summary
• On new lead (event via Slack/webhook) — enrich from public sources, score against ICP notes, write score and rationale to a custom field
• Weekly — data quality report: required fields missing, orphaned contacts, duplicate accounts

Each routine follows the four-part shape: when it runs, what it reads (bounded), what it produces, when it stops. See routines best practices.

The thing to gate

Mass updates and anything touching Apex/flows. Bots should read and annotate; admins change automation.

Verdict

Works, with more setup than HubSpot. Worth it if Salesforce is already the system of record; the Bot's value is in the annotation layer, not in replacing admins.

Setup notes

• Test every routine supervised until it's produced the right output three times.
• Add the routine's completion line to your heartbeat log so silent failures show up.
• Put the Salesforce token in the Bot's connector settings or knowledge file, never in a chat message.