Automation is the highest-leverage skill a Salesforce admin can develop. The shift from clicks-not-code to prompts-not-clicks compresses 8-hour tickets into 8 minutes. This page is about the patterns that work in production, the patterns that look good in demos and break in production, and how to tell the difference.
04 steps · 04 FAQs
“Most Salesforce automation breaks not because the logic is wrong, but because the data flowing through it was never validated.”
Practical steps
On paper, in 4 boxes: trigger, decision, action, side-effect. If you can't fit it on a sticky note, the Flow won't fit in your head either.
Every Flow that touches data needs entry conditions tighter than you think. The cost of a no-op Flow run is 2ms. The cost of a corrupt-data Flow run is a weekend.
Run 200 records through it in sandbox. If it doesn't bulk-safely complete, it's not bulk-safe. Most Flow patterns work for 1 record and silently fail for 50.
Log the trigger condition, the input record, and the output. When something breaks, the diff is the difference between a 5-minute fix and a 2-day investigation.
Related reading
From the library
Score
Quick reference for the 30 most common Salesforce SetupAuditTrail action types. What each entry means operationally, severity classification, and what to do when you see it.
Score
The 4 permission layers and how they really resolve, 10 named anti-patterns, the SOQL query bank, real-world breach stories, and a cleanup sequence that won't break access. Spring '26 current.
Avg readiness
A comprehensive checklist to evaluate your Salesforce org's readiness for AI, covering data quality, automation maturity, user adoption, and integration preparedness.
Frequently asked
Lead assignment with deduplication. It's the workflow most reps interact with daily, the one most likely to leak revenue when broken, and the one most easily measurable. Build it well, document it, and it pays for itself in 3 weeks.
Flow, every time, in 2026. Process Builder is on the deprecation path. New builds should be Flow-only. Existing Process Builder workflows should be migrated as part of any touch, don't let them sit untouched and accumulate technical debt.
When you hit any of three constraints: (1) you need to call out to an external system synchronously, (2) you need to traverse more than 5 levels of related-record relationships, or (3) you're processing more than 200 records and Flow's bulkification can't keep up. Until then, Flow.
Document the trigger, the entry conditions, the actions, and the rollback plan in a single page. Your architect doesn't want to read your Flow XML; they want a 200-word brief. Treat that brief as part of shipping the automation, not optional.
More for admins
Hand the actual work to Clientell AI your AI agent for Salesforce automation, flows, data ops, and user management.
Unlimited messages · No credit card required