I will build fix and optimize salesforce flow automation and CRM processes


About this gig
Salesforce Flow should remove manual work, not create new problems. A poorly designed flow can update the wrong records, run twice, fail silently, hit limits or conflict with validation rules and other automation.
I will build, troubleshoot or optimize Salesforce Flow around the business process you actually need.
I can help with record triggered flows, scheduled flows, screen flows, lead and case routing, task creation, field updates, notifications, approvals, decision logic, loops, entry criteria, debugging and migration from older Workflow Rules or Process Builder where appropriate.
For an existing problem, I trace the flow path, check conditions and dependencies, reproduce the issue and correct the logic. For a new automation, I map the process first, build it cleanly, test expected and edge cases, and document the result.
This gig focuses on Salesforce configuration and Flow. Apex development, large managed package conflicts or enterprise wide redesigns should be discussed before ordering.
Get to know Elisabeth Peter
CRM Systems Automation and Web Integration
- FromGermany
- Member sinceSep 2026
- Avg. response time1 hour
Languages
German, Italian, English
Other Software Development Services I Offer
FAQ
Which Salesforce Flows can you work with?
Record triggered, scheduled, screen and other standard Flow configurations can be reviewed depending on the project.
Can you repair an existing Flow instead of rebuilding it?
Yes. I first determine whether repairing the existing logic is safer and cleaner than replacing it.
Can you migrate Workflow Rules or Process Builder automation to Flow?
Yes, when appropriate. I review the old logic first so outdated or duplicated behavior isn't blindly recreated.
Can you fix a Flow that runs twice or updates the wrong record?
Yes. Entry conditions, execution paths, recursion and conflicting automation are part of the troubleshooting process.
Do you write Apex?
Apex is not included in these standard packages. If custom code is required, the scope should be discussed first.
Should changes be tested in a Salesforce sandbox?
For changes with meaningful production impact, a sandbox is strongly preferred when available.
Can you troubleshoot managed package conflicts?
I can diagnose how Flow interacts with the environment. Complex third-party package development may require a separate scope.

