Everything you need as a Salesforce admin: install the package, run a scan, read the results and activate your license.
We recommend installing in a sandbox first, so you can see the dashboard before touching production.
Click the install link for your org.
Recommended: try the sandbox link first. Same package, same install steps, no risk to your production org.
Log in as a System Administrator. Choose Install for Admins Only, then confirm the install.
In Setup, go to Permission Sets and assign Untanglr Admin to every user who will run scans.
Open the App Launcher, search for the Untanglr app, and open the Dashboard tab.
On the Dashboard, click Run Scan. Untanglr reads your Flow metadata only: elements, loops, DML, Get Records, API versions and trigger order. No record data and nothing else leaves your org.
One debt score from 0 to 100 for the org, so you can track whether things are getting better or worse over time.
Automation load per object, including a column for Apex triggers, so you see the full picture, not just Flows.
Every Flow scored and ranked, worst first, so you know which one to open next.
Element counts, loops, DML, Get Records, API version and every metric behind a Flow's score, for the ones you want to dig into.
A prioritized list that names the exact elements at fault, not generic advice.
By default, a scan is incremental: only Flows that changed since the last scan are re-analyzed. Turn on Force full rescan when you want every Flow re-analyzed from scratch, for example after a deploy that touched a lot of automation.
Buy an activation key or a Business subscription on this site. The key arrives by email and is also visible in your portal.
To activate in Salesforce:
The key is tied to your production org’s My Domain and works in all of that org’s sandboxes too, so you only activate once.
Scheduled scans, and the automatic email digest after every scheduled scan, are included with Business subscriptions.
Without a key, the dashboard runs in Free mode: a limited scan with teaser results and no export. The 7-day free trial reveals every recommendation in full; activating a paid key unlocks everything above.
A short reference for once you’re past the first scan.
Each object gets a load score based on how many Flows and triggers touch it, weighted by how risky they are. The before-save and after-save counts tell you how much of that load runs synchronously versus after the record commits. A high load score with a high trigger count usually means the object is a bottleneck: changes there are more likely to break something else.
Recommendations are ranked, so start at the top. Each one names the Flow and the exact element causing the issue (a specific loop, a DML statement, a missing fault path) so you don't have to go hunting. Once you've fixed something in Setup, mute the recommendation and run a rescan to confirm the score improved. If it didn't move the way you expected, the element is probably still there.
Click Export PDF from the dashboard on any paid plan. The report includes the scan summary, the object heatmap and the ranked recommendations, formatted for a stakeholder who won't open Salesforce. Set your name, a brand color and a footer once in settings and every export after that uses them automatically.
Scheduled scans are a Business feature. Set a frequency, the days and a time in settings and Untanglr keeps the dashboard current on its own, with an automatic email digest after every scheduled scan showing the current score, the change since the last scan and the top risks, so you don't have to log in to know if something got worse.
When more than one record-triggered Flow (or a Flow and an Apex trigger) fires on the same object and event without an explicit order, Salesforce picks the order for you, and that order isn't guaranteed to stay the same over time. That's how you end up with a Flow reading a field before another Flow has set it, or two automations undoing each other's work. It's hard to debug because it can look intermittent. Untanglr's recommendations flag these conflicts by name, listing which Flows collide and where to set an explicit order.
Install the package, run a scan, and see what your Flows are costing you.