a salesforce assistant that checks the record first

what a bot can do in Salesforce

choose the record type and review question first. an opportunity review should cite the opportunity details; a lead intake check should stay with the lead fields. the actions below support those bounded jobs without requiring a bot to roam through every crm object.

composio, the connection service dusk bot uses for apps, lists 327 Salesforce actions (catalog version 20261104_00, read 12 november 2026⁴). dusk bot treats 175 of them as reads, 10 as sends and the other 142 as changes. an action counts as a read only when its name starts with a read word like get, list or search, so a bot you allow only to read can never call the rest. a send is anything that reaches a person outside the app or moves money, like create campaign record: it waits for your Allow unless you've given that bot a daily amount it may send alone.

connect Salesforce

1. open Connected apps in the sidebar.
2. pick Salesforce and sign in on Salesforce's own page, so your password goes to them and never to a bot.
3. choose which bots may use it, and whether each may only read or may also change things. your bookkeeper doesn't need your Salesforce.
4. ask in plain words. reading and drafting happen freely; sending asks you first.

allow salesforce for your sales bot in Connected apps. begin with the read actions needed for an opportunity and task review. give the bot the team, record names and fields that define your question. if your crm uses terms in a special way, explain them before scheduling the job.

routines to copy

these are review requests, not instructions to rewrite the pipeline. adapt the business rules to the fields your team actually maintains, and ask the bot to show a gap when a required field is absent.

every monday at 8, find the salesforce opportunities our team expects to close this month. inspect their details and related follow-up tasks where available. list deals with no recorded next step. show the close date and owner as recorded, without changing either.

every weekday at 2, review the leads from the intake list i supplied. flag missing company or contact details and separate them from leads that look ready for our qualification check. do not enrich fields from guesses or convert any leads.

every friday at 10, search salesforce tasks assigned to me that are due this week. compare their recorded status with the related opportunity details you can access. bring me unfinished follow-ups and any unclear links. leave task statuses alone.

what it asks you first

a pipeline reviewer can stay read only. that prevents it from creating follow-up tasks or changing opportunity records, while still letting it bring findings to your chat. permission to read a deal is not permission to advance its stage.

if you later allow task creation or opportunity edits, put "ask me before you change anything" into the routine when review is required. the sending setting doesn't cover record changes. sends through connected apps follow their separate setting: they ask by default, unless you allow a daily amount. a bot on Full access with no sending rule of its own may send up to 25 a day without asking, so set Ask every time for it.³

what it cannot do

• change stages, owners or tasks with read-only access. grant only the specific writing actions needed if you decide to add record maintenance later.
• fill missing lead details from evidence that is not there. an empty field should be reported as empty, with a question for its owner.
• use every action that sounds like a lookup under read-only permissions. some lookups count as changes in dusk, for example querying contacts by name, so stick to the search and get actions above.
• deliver a scheduled pipeline note while your own computer is asleep or the app is closed. an always-on dusk cloud machine can keep the schedule.

a missing next step needs a definition

tell the bot what your team calls a next step and where you record it. a field value, a linked task and an informal note are different evidence. ask it to say which one it found, rather than collapsing them into an unsupported verdict that a deal is healthy.

use lead research for a separate research brief. teams using hubspot should start with that app's own record actions.

keep customer mail separate

the salesforce connection is not a gmail connection. if a review needs correspondence from gmail, connect that account separately and specify which correspondence belongs in the review. otherwise ask the bot to stick to the crm evidence it can retrieve.