How to Automate Salesforce

The Salesforce org is the number the company is measured on

Salesforce, which half its users call the CRM and the other half call SFDC, is the system a company describes its revenue in. Sales Cloud holds the leads, accounts, contacts and opportunities, and the pipeline they add up to. When the board asks how the quarter is going, somebody opens a dashboard built on those objects and reads it out.

It is almost never used as it shipped. Every org is bespoke: custom objects and fields, validation rules, record types and page layouts that an admin has spent years shaping around how this particular company sells. That is its strength, and the reason nobody leaves.

It also means the record is load-bearing well past the sales team. Commissions are calculated off closed-won. Finance plans against the pipeline. Onboarding starts when a stage changes. An opportunity sitting in the wrong stage is not untidiness. It is somebody's commission and somebody else's hiring plan.

A rep types for an hour so a dashboard can be right

The complaint is old and still fair: the people who feed the CRM are not the people it helps.

A rep comes off a call and spends twenty minutes writing the notes, moving the stage, logging the next step and pushing out a close date. Before the next call they open the prospect's website, their news page, their careers page and the last email thread, and paste the useful parts onto the account. Someone in revenue operations exports closed-won deals each month and rekeys them into a commission tool that has no connector. Someone checks whether an invoice on a signed deal was actually paid, in a finance system nobody in sales can open. Someone dedupes a contact list by eye.

At quarter end the forecast is only as trustworthy as those hours were thorough, which is a strange foundation for the number everyone is judged on.

Salesforce

Accounts researched before the call The prospect's own site, their recent news and their open roles gathered into a briefing on the record the night before anyone dials.

Closed-won that carries on working The commission record, the onboarding checklist and the first invoice picked up in the systems that never had a connector to the org.

Contacts checked against reality Champions who quietly changed employer flagged now, and duplicate records surfaced for a person to confirm rather than to go hunting for.

An admin can build almost anything that stays inside

Salesforce automates far more than most orgs switch on, and exhausting the built-ins is the right first move.

Flow Builder is the centre of it: record-triggered, scheduled and screen flows that fire on a record change, on a timetable or when a user starts them, then create records, update fields, call actions and branch. Approval processes route a record to the right people and hold it until they answer, and a flow can call an approval process directly. Einstein Activity Capture syncs a connected Microsoft or Google account and attaches email and calendar activity to the related contact, lead, opportunity and account, so the timeline fills without anyone logging a call. Reports and dashboards roll the lot up by rep, team or region, and Agentforce will now draft a flow from a plain description of the process.

Every one of those runs on data the org already holds, or on a system somebody integrated first.

That is the ceiling. A flow cannot open a browser tab. It cannot read a prospect's careers page, check a balance in a billing portal, or find out that a champion changed employer last month, unless a connector was built for it.

A pipeline checked against facts the org never captured

Two things change once something can open a browser on the org's behalf, and they run in opposite directions.

Facts arrive. Ahead of a discovery call, the prospect's own site, their recent funding news and their open roles are sitting in a briefing on the account, written the night before. A named contact who has quietly changed employer gets flagged now rather than found in month nine. A contact list is checked against the outside world, so the duplicates are ones a person confirms instead of ones a person hunts for.

And work leaves. A deal moves to closed-won and what should follow actually follows: the record raised in the commission tool that never had a connector, the onboarding checklist opened, the first invoice checked against the ledger. Quota attainment read across the team and pushed out while there is still a month to act on it. A clawback condition on a deal that unwound, caught in the week it unwound rather than in the next commission run.

The shape repeats. The org is either the trigger or the destination, and the useful step happens in a system it cannot reach. Gathering runs unattended. A quote, a customer email, a stage change that feeds the forecast, all get drafted and wait.

The looking up and the writing down stop being a person's job

Reading a screen in one system and typing what it says into another is the whole of it. That has never been work that needed a salesperson.

WebRun is an agent that works a real Chrome browser, signed in as you. It opens the systems that never appeared on the AppExchange, reads them the way a rep would, and writes the answer onto the account, contact or opportunity it belongs to. No private app to register, no integration user, no sandbox.

It runs on your schedule inside your own private environment, you can watch a run and stop it mid-way, and anything that reaches a customer drafts and waits.

Each workflow below names what it opens and what it writes.