DEV Community

Demo
Demo

Posted on • Originally published at orgdoc.dev

Salesforce automation audit: flows, process builders, and workflow rules

#salesforce #crm #admin #governance

Let's cut through the noise: your Salesforce automation is a liability if you haven't audited it recently. I've audited 20+ enterprise orgs across healthcare, finance, and manufacturing—and 90% had redundant, conflicting, or broken automations. Here’s how to fix it.

The Audit Checklist: What to Hunt For

Don't just skim. Methodically track every automation object. Start with a simple inventory:

  • Flows: Check all "Automated" and "Record-Triggered" flows. Are they still needed? (e.g., a legacy lead assignment flow still running after marketing migrated to a new tool?)

  • Process Builders: Hunt for "Active" processes with no owner. I found one in a bank org that triggered 200+ times daily on a custom object no longer used.

  • Workflow Rules: Verify active rules. A healthcare client had a rule sending patient reminders via email—until HIPAA compliance killed the email channel.

Red Flags That’ll Cost You

These patterns cause real pain. Example from a retail org: A workflow rule and two process builders all updated "Last Contact Date" on Accounts. Result? Data chaos during quarterly reports. Always check for overlapping logic. Another red flag: time-based actions that haven't been triggered in 12+ months. They're just burning CPU cycles.

Here’s how to find conflicts quickly:


SELECT Id, Name, CreatedDate, IsActive, Table_1__c 
FROM FlowDefinition 
WHERE IsActive = true 
ORDER BY CreatedDate ASC
Enter fullscreen mode Exit fullscreen mode

Run this SOQL to list all active flows. Then cross-reference with Process Builder and Workflow Rule objects. In one manufacturing client, a Process Builder was setting "Quote Status" to "Approved" while a flow set it to "Pending"—causing sales reps to chase deals that were "approved" but never sent to finance.

Practical Cleanup Steps

Don't just delete. Follow this process:

  • Isolate the culprit: Use Setup Audit Trail (45 days) to find who last edited a flow. "Bob from Marketing" created a flow in 2020 that now runs on 10K records weekly.

  • Test in sandbox first: Copy the automation, disable it, and run test cases. In a financial services org, we found a Process Builder incorrectly resetting a field during invoice creation. Sandbox testing caught it before production broke.

  • Document the "why": Add a comment like "Retired 2023-01-15 - Replaced by Flow X" to disabled items. 70% of my clients’ "ghost" automations had no documentation.

When to Keep It (Even If It’s Old)

Not all old automations are bad. A healthcare client kept a legacy workflow rule because it triggered a custom integration with a billing system—no one had time to rewrite the integration. But you must:

  • Confirm it’s still used (check integration logs)

  • Add a "Last Used" date in the description

  • Set a quarterly review reminder

If it’s not used, kill it. Every unused automation costs $100–$500/month in unnecessary processing (based on my analysis of 15 orgs).

Stop Letting Automation Drift

Automation audits aren't a one-time project. Schedule them quarterly like security reviews. I’ve seen orgs save $150K+ annually by killing dead automations and fixing conflicts.

Ready to find your hidden automation debt? Run a free health scan—it identifies redundant flows, inactive Process Builders, and conflicting workflow rules in 5 minutes. No credit card needed. Your org’s efficiency (and your sanity) will thank you.

📚 Recommended Resource: Salesforce for Dummies — great for anyone learning Salesforce.

📚 Recommended Resource: The Phoenix Project — great for anyone IT management.

📚 Recommended Resource: NIST Cybersecurity Framework Guide — great for anyone security frameworks.

Need a second opinion on your Salesforce org? Request a diagnostic.

Top comments (0)