# Build Salesforce Flows from a sentence, and fix them in one edit. > SyncOnAI 360 Flow Builder is a canvas that matches Salesforce's Flow Builder, with AI beside it. Describe a Flow or edit it by hand, see everything that runs when its record is saved, add fault paths to every element in one edit, rename safely across references, and propose the result for approval. Source: https://synconai360.com/features/flow-builder ## Key facts - **1**: Edit to add fault paths to every element that can fail - **Every**: Reference updated when you rename an element - **All**: Flows fixed at once for an org-wide issue - **0**: Changes reach the org without an approved proposal ## Why Flows become the hardest part of an org to change Flows replaced Workflow Rules and Process Builder, and now every org has dozens of them. They are easy to start and hard to maintain: missing fault paths, several Flows on the same trigger, hardcoded ids and loops that query records one at a time. - **Silent failures.** A Flow without fault handling fails with an email to whoever built it, often someone who has left. Users see a generic error and the record is not saved. - **Nobody knows what else runs.** Before-save Flows, validation rules, triggers and after-save Flows all fire on one save. Without the order in front of you, changing one Flow is a gamble. - **Renames break references.** Rename a resource and every formula, decision and assignment that used it needs finding by hand. Miss one and the Flow fails at runtime. - **The same fix, Flow by Flow.** When an audit finds a hardcoded id in twenty Flows, the fix is the same twenty times over, made by hand and reviewed one at a time. ## How do you build a Salesforce Flow with AI? Describe the process in the chat, or name an existing Flow and it opens on the canvas beside the conversation. The AI checks what already runs on the object, builds to your org's own fields, queues and conventions, and shows its edits as a preview you accept or reject. The builder explains a Flow before you edit it: an overview in plain sentences first, then the canvas. Every edit is recorded as a version you can step back through and restore, and large Flows can be read one path at a time with Focus. - Describe it, or open any Flow in the org by name - AI edits shown as previews you accept - A plain-language overview before the canvas - Every edit versioned and restorable ## How do you add fault handling to a Salesforce Flow? One edit adds fault paths to every element in the Flow that can fail, as a single change you can review. Paste the "An error occurred at element" email Salesforce sends and the canvas selects the element that failed and the path the run took. When an issue spans the org, such as a hardcoded id, one fix can be applied to every affected Flow at once and reviewed as one set. Missing fault paths and hardcoded ids are also among the checks the org audit runs, so the work and the evidence stay together. - Fault paths added to every risky element in one edit - Paste a failure email to find the failing element - One fix across every affected Flow ## What else runs when a Salesforce record is saved? What Else Runs lists everything that fires when this Flow's record is saved, in Salesforce's order of execution: before-save Flows, validation rules, Apex triggers and after-save Flows. Overlaps are obvious at a glance. Org drift tells you if someone saved the Flow in Salesforce after you opened your draft, and what moved. A summary paragraph you can hand over lists the objects the Flow reads and writes, and flags queries or updates inside loops. - Everything that runs on save, in order - Drift warnings when the org's copy changes under you - Objects read and written, and work done inside loops ## How does a Flow get from the canvas to production? When the Flow is ready, create a proposal. It carries named pre-flight checks, a before and after view, and the blast radius of the change. Sandbox deploys go straight through so you can test; production needs an approval from an admin other than the author. A simulated run can be kept as a Salesforce Flow test. Copy elements in from any Flow in the org, see what a Screen element displays without running the Flow, and rename anything with every reference updated, including inside formulas. - Proposals with checks, blast radius and approval - Simulated runs kept as Flow tests - Copy elements from any Flow in the org - Safe renames, formulas included ## How do you understand a large or unfamiliar Salesforce Flow? Start with the overview: a plain-language description of what the Flow does, written before you see a single element. Then read it on the canvas, or switch on Focus to follow one path at a time through a large Flow instead of scrolling a sprawling diagram. The summary you can hand over lists the objects the Flow reads and writes and flags any queries or updates inside loops. See a Screen shows what a Screen element displays without running the Flow, and you can copy an element in from any other Flow in the org when the pattern you need already exists. - A plain-language overview before the canvas - Focus to read one path at a time - Objects read and written, and work inside loops, summarised - See any Screen without running the Flow ## How the Flow Builder works 1. **Describe or open.** Describe the automation, or open an existing Flow by name. 2. **Understand.** Read the overview and see what else runs on save. 3. **Edit.** Accept AI previews or edit by hand; add fault handling in one edit. 4. **Test.** Simulate a run, keep it as a Flow test, deploy to a sandbox. 5. **Approve.** Propose for production, approved by a second admin, with a receipt. ## Flows, with and without SyncOnAI 360 | Without | With SyncOnAI 360 | |---|---| | Fault paths added element by element | Fault handling across the whole Flow in one edit | | Order of execution worked out by hand | Everything that runs on save, listed in order | | Renames that break formulas | Renames that update every reference | | The same fix in twenty Flows | One fix applied to every affected Flow | | Flows activated straight in production | Proposals approved by a second admin | ## Who uses the Flow Builder - **Salesforce admins.** Build and fix Flows on a canvas that matches Salesforce's own, with the Flow explained in plain sentences before you edit it. - **Consultancies.** Apply one fix across every affected client Flow at once and review it as one set, instead of repeating the same change Flow by Flow. - **Salesforce developers.** See exactly what a Flow change does in a before and after view, validated against the org before it is proposed. - **Approvers.** Review Flow changes with their checks and blast radius, and keep production behind a second admin's approval. ## Frequently asked questions ### Can AI build Salesforce Flows? Yes. Describe the automation in SyncOnAI 360 and the AI builds the Flow on a canvas that matches Salesforce's Flow Builder, using your org's own fields and queues. Its edits appear as previews you accept, and nothing deploys without approval. ### Does it replace Salesforce Flow Builder? It works alongside it. The canvas matches Salesforce's Flow Builder and adds what it does not offer, such as fault handling in one edit, order of execution and safe renames. The result is ordinary Flow metadata in your org. ### How does fault handling in one edit work? One edit adds fault paths to every element in the Flow that can fail, routed the way you choose, as a single change you can review before accepting. ### Can it help debug a failing Flow? Yes. Paste the error email Salesforce sends and the canvas selects the element that failed and the path the run took. ### Which Flow elements can be edited? Most elements can be edited on the canvas. Decision outcomes, Screen components, Wait events, Transform mappings and orchestration steps can currently be viewed but not changed. ### Can we create Flow tests? A simulated run can be turned into a Salesforce Flow test. Generated tests should be run in Salesforce to confirm them before you rely on them. ### What if someone edits the Flow in Salesforce while we work? Org drift detection tells you if the Flow was saved in Salesforce after you opened your draft, and shows what moved. ### How do Flow changes reach production? As a proposal with named pre-flight checks and its blast radius. Sandbox deploys go straight through; production needs an approval from an admin other than the author, and every deploy has a receipt and rollback. ### Can we fix the same problem in every Flow at once? Yes. A fix such as removing a hardcoded id can be applied to every affected Flow in the org at once and reviewed as one set. ### Is the Flow Builder included on the free plan? Every plan includes every feature. Free covers one user and one production org with its sandboxes, on your own Anthropic or OpenAI key, with no credit card and no time limit. Paid plans include AI and cover more people and production orgs. ### Does the Flow Builder work with Flows built in Salesforce? Yes. Open any Flow in the connected org by name. The canvas reads the org's own Flow metadata, and the result of an edit is ordinary Flow metadata deployed through a proposal.