J
Jazmin Gorski
Problem Statement:
Currently, there is no centralized way within the platform to track where a Custom Field or Custom Value is being used. These variables can appear across multiple assets, including:
Email templates
Workflow messages
Funnel or website elements
Forms and surveys
SMS templates
calendars
and automation logic
This lack of visibility creates a major risk for error when modifying or deleting custom fields/values, since their dependencies are hidden. Users have no way of knowing what will break — until it’s too late.
High-Impact Use Case:
A common scenario involves users purchasing pre-built snapshots that come with little to no documentation. These snapshots often include dozens (or hundreds) of pre-configured fields and values that are woven throughout the system.
Without visibility into where these variables are used:
Users can’t confidently customize or localize the snapshot
Small changes to a value or field can unintentionally break workflows, automations, or live client funnels
It becomes nearly impossible to clean up unused fields or safely scale the system
This is a growing issue as the marketplace for templates and snapshots expands.
Proposed Solution:
Introduce a "Connected Asset Viewer" or "Usage Audit Tool" for Custom Fields and Custom Values, featuring:
A list of all system assets where a specific field or value is used
Links to each instance of use (e.g., “Workflow: ‘Lead Nurture’ – Step 2 SMS Message”)
Visibility during the editing or deletion process with warnings for active dependencies
Option to export or print usage data for documentation
Impact:
Increases confidence in system edits
Reduces unintentional breakage
Speeds up onboarding for new team members or clients
Makes snapshot adoption and customization far more manageable