Simplify your setup: empty fields and redundant automations
A deterministic advisor flags fields that are almost always empty and automations that are duplicated or conflicting, with evidence. It only suggests; nothing changes without you.
Over time, a setup accumulates fields nobody fills in and automations that repeat or contradict each other. The simplification advisor sweeps this for you deterministically, with no AI and no cost, and points out what to review with the evidence next to it. It NEVER archives, turns off, or deletes anything: it only suggests, and you decide.
Always-empty fields
For each object with enough records, the advisor measures in how many of them each field is filled. A field that shows up filled in almost no records (2% or less) becomes a candidate to archive. For safety, it never suggests a required field, a system field, or a recently created one (which has not had time to be used yet). Objects with few records are skipped, because there would be no evidence to judge.
Duplicate or conflicting automations
The advisor compares your automations (workflows, field rules, and journeys) by normalizing trigger, conditions, and actions. It flags three situations: duplicates (same object, trigger, conditions, and identical actions), overlaps (same trigger and conditions but different actions, which can conflict or double the effect), and stale ones (automations turned off for a long time that could perhaps be removed). Different types are never compared with each other.
How to use it
- Ask the assistant (Copilot): "which fields are always empty?" or "do I have duplicate or conflicting automations?".
- It answers with the list, the object, and the reason (for example, "never filled in 120 days" or "2 identical automations: Notify won, Notify won (copy)").
- You review each suggestion and decide whether to keep it, archive the field, or turn the automation off. The action is always yours.