Snapshot/
—
The original post in the GoHighLevel Official Facebook group asks for assistance with snapshot and ecosystem naming conventions. The user mentions having a spreadsheet to map out the snap-pipeline-workflows-forms and is about to finalize their snapshot structure and naming convention.
The user seeks guidance from the community, specifically mentioning if any videos or links related to naming conventions have been shared in the past 3-6 weeks that they might have missed. They acknowledge that there are individuals in the group with expertise in this area.
As an expert in GoHighLevel CRM software, I can understand the user's need for a clear and organized naming convention within the GoHighLevel ecosystem. Establishing a consistent naming convention is crucial to ensure efficient workflow management and effective communication within the platform.
While I don't have specific knowledge of any recent videos or links related to snapshot and ecosystem naming conventions, I encourage readers to read the comments below this article and check the source link provided for any updates or responses from the GoHighLevel community.
It is highly likely that other GoHighLevel users in the Facebook group have shared valuable resources or insights on this topic, which can provide further guidance and assistance to the user seeking help with their snapshot structure and naming convention.
Source
1AA11
Module# – Asset Type – Asset ID
1-A-A11 – with the dividing lines in for reference.
This tells you in the snapshot what system is this part of, and your documentation what type of snapshot asset it is. (super useful for easy grouping of similar items in the database together via filters, and also for auto creating naming conventions using a formula/dropdowns.)
It also gives you flexibility to associate similar assets together.
Workflow A = A00
Message Template 1 in workflow A = A01