Connect any Salesforce org. Read, toggle, snapshot and revert every automation — grouped by type and object. Built for migrations.
Select your environment and click Connect. You'll be taken to Salesforce to log in — direct to Salesforce by default; nothing is ever stored server-side.
Before a migration or a large data load, the automation in an org has to come off — validation rules reject rows that are valid in the source system, flows and triggers rewrite fields mid-load, and workflow rules fire on records that aren't finished yet. Doing that by hand means walking Setup one rule at a time, and then trying to remember the exact state everything was in when you put it back.
SF Automation Switch reads every automation in a connected org through Salesforce's own APIs, groups it by type and object, and lets you toggle individually or in bulk. Before any bulk change it takes a snapshot of the exact active or inactive state of every record, so the revert restores what was actually there rather than switching everything on.
Does my Salesforce data leave my browser?
No. By default every API call goes directly from your browser to your own Salesforce instance. There is no database and nothing is stored server-side. An optional relay exists for orgs that can't add a CORS entry — it is off by default, stateless, and described in full on the trust page.
Why do I have to add a CORS entry to my org?
Because the call is genuinely cross-origin and browsers enforce the same-origin policy, so your org has to state that it permits this site. Chrome extensions skip it by running with extension privileges; server-backed tools skip it by proxying the call, which means your token reaches their server. See the CORS setup guide if the Apex shortcut fails in your org.
Can I deactivate a managed package trigger?
No, and neither can any other tool. Packaged code is locked in the subscriber org. This tool detects packaged automations, badges them, and leaves them out of bulk operations so a run doesn't half-complete. Background: INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY.
What happens if my session expires halfway through a bulk disable?
The queue is crash-resumable. Reconnect and it picks up where it stopped, rather than leaving the org in a state nobody has a record of.
Does it work in production?
Flows, processes, validation rules and workflow rules, yes. Apex triggers are the exception — Salesforce does not allow Apex to be modified directly in production, so those need a deployment with the trigger marked inactive, or a bypass built into your own trigger handler.
Can I undo a single toggle?
Yes. Every manual toggle goes onto a session change stack that can be reversed individually, separately from the snapshot system.
Is there a way to try it without connecting an org?
Yes — the Playground runs on simulated data with no login, no CORS setup, zero network calls and zero storage writes.
Does it change my records?
No. It works on the metadata layer only. It never reads or writes business records.
What does it cost?
Nothing. No account, no trial, no paid tier.