Why "Less is More" in Salesforce Automation

How Zon Projects Solved the "Naming Conflict" for a UK Charity

Efficiency in Salesforce isn't just about what you automate; it’s about knowing when to stop. For a recent charity client, we encountered a common hurdle: an existing automation for FinDock payments was becoming too complex to manage, specifically when it came to naming conventions for new Community Donations.

The Challenge: The "Mega-Flow" Trap

The charity was using a single, heavy Flow to rename Opportunities. While it worked for standard payments, Community Donations were different. These records are often cloned for subscriptions or edited manually by fundraisers. The existing automation was "too heavy," and trying to bake in every exception was making the system brittle.

The Zon Projects Solution: The Strategic Pivot

Instead of adding more complexity to the existing logic, we took a step back and simplified:

• Separation of Concerns: We excluded the Community Donation record type from the original heavy Flow entirely.

• The "Create-Only" Rule: We built a dedicated, lightweight Flow specifically for Community Donations.

• User Autonomy: By triggering the automation only on Record Creation, we ensured the initial name was professional and consistent, but left the door open for fundraisers to manually edit or clone records without the system overwriting their changes.

The Result

A system that is easier to maintain and a fundraising team that feels in control of their data. By avoiding the "Mega-Flow" trap, we’ve ensured the charity’s Salesforce org remains agile as they grow.