Home/HighLevel/Features/Account Snapshots/HighLevel snapshot asset dependencies: create, refresh, and load

Workflows and Automation

HighLevel snapshot asset dependencies: create, refresh, and load

In short

Snapshot Asset Dependencies is a feature that automatically adds supporting assets like email templates, custom fields, tags, and pipelines when you capture, refresh, or load a Snapshot. It helps ensure that selected Workflows and Email Templates retain their required components across subaccounts.

AreaAccount Snapshots · Snapshots
Used forDigital marketing agency, Ecommerce store, SaaS startup
Setup steps16 steps in 3 tasks
Last updatedNovember 17, 2026

01Who this is for

  • Agency owners who build reusable client setups, because the feature bundles required assets automatically, reducing manual selection.
  • Marketing teams that rely on Workflows and Email Templates, as dependencies are captured to keep automations functional after transfer.
  • Product managers deploying standard configurations across multiple subaccounts, because the feature lowers the risk of missing linked assets.

02Snapshot Asset Dependencies, explained

The feature scans selected Workflows and Email Templates for any referenced assets such as Email Builder Templates, Custom Fields, Tags, Pipelines, and Brand Colors. When you create or refresh a Snapshot, HighLevel adds those referenced items automatically. During the load process, turning on a toggle will automatically select those dependencies for transfer.

Dependency handling occurs at two moments: snapshot creation or refresh, and snapshot loading. In the creation and refresh steps, HighLevel detects and includes available supporting assets. When loading, the Auto include dependent assets control determines whether those assets are selected alongside the primary ones.

You find the controls on the asset selection screen within the Snapshot workflow, and Version History labels automatically included assets for review.

03How businesses use Snapshot Asset Dependencies

  • Digital marketing agency. The agency creates a Snapshot of a client’s automation set, letting HighLevel automatically pull in the email templates and custom fields each Workflow uses. When the agency rolls out the same setup to a new client subaccount, they enable Auto include dependent assets so all needed pieces arrive together.
  • Ecommerce store. The store selects its order confirmation Workflow and related email template, then refreshes the Snapshot after adding a new tag for VIP customers. HighLevel adds the new tag as a dependency, ensuring the refreshed Snapshot contains the latest configuration before loading it to another store.
  • SaaS startup. During onboarding, the startup loads a Snapshot into a fresh subaccount. By turning on Auto include dependent assets, the system automatically selects the required pipelines and custom objects tied to the chosen Workflows, simplifying the initial setup.

04The numbers and rules that matter

  • Supported dependency types: Email Templates, Custom Fields, Custom Values, Tags, Pipelines and pipeline stages, Custom Objects, Trigger Links, Brand Colors.

05How to set up and use Snapshot Asset Dependencies in HighLevel

Create a Snapshot with Dependencies

  1. Navigate to Agency View > Account Snapshots.
  2. Click the + Create New Snapshot button.
  3. Enter a name for the Snapshot and choose the source subaccount.
  4. Select the Workflows, Email Templates, and any other assets you want to capture.
  5. Press Create; HighLevel will automatically add any detected dependencies.

Refresh a Snapshot to Recheck Dependencies

  1. Go to Agency View > Account Snapshots.
  2. Find the desired Snapshot and click its Refresh icon.
  3. Pick the assets you wish to add or update in the refresh selector.
  4. Click Refresh so HighLevel reassesses the assets and includes new dependencies.

Include Dependencies When Loading a Snapshot

  1. Open the load flow from Agency View > Account Snapshots by selecting Load Updates to Subaccount, then choose the destination subaccount(s) and continue.
  2. Or start from Agency View > Subaccounts, open the three dot menu of the target subaccount, pick Manage Client > Actions > Load Snapshot, and select the Snapshot.
  3. In the Assets step, expand the categories and tick the Workflows or Email Templates you want to import.
  4. Enable the Auto include dependent assets toggle located beneath the asset list.
  5. Click View dependencies to filter the list and see the automatically selected supporting assets.
  6. Use Show all assets to return to the full asset list if needed.
  7. Press Proceed, resolve any conflict prompts, and confirm the load to finish.

06What it looks like in HighLevel

07Settings that matter

  • Auto include dependent assets. Controls whether dependencies are automatically selected during the Snapshot load process.

08Things to know before you rely on it

  • Automatic detection currently works only for Workflows and Email Templates.
  • Dependencies for other asset types are not identified automatically and must be added manually.
  • Auto inclusion can be turned off during loading, which may leave required assets unselected.
  • If a referenced dependency cannot be found, HighLevel skips it without stopping the rest of the Snapshot processing.

09How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

Moving automations between accounts can be frustrating when templates or fields are missing. In my experience, Snapshot Asset Dependencies saves time by gathering related assets automatically, so I can focus on strategy rather than hunting for missing pieces.

If you only need a single workflow and you’re confident every piece it touches is already in the destination, the extra step of turning on autoinclude may feel like overhead. In that case the feature adds little value and you might prefer a leaner manual selection.

Get More InformationOpens on HighLevelPublished November 3, 2026 · Updated November 17, 2026

Common questions

Common questions about Snapshot Asset Dependencies.

Do I still need to select every related asset manually?

For supported Workflows and Email Templates, HighLevel adds available dependencies automatically when you create or refresh a Snapshot. During loading, turn on Auto include dependent assets to select those dependencies automatically.

Why are some assets checked even though I did not select them?

Those assets are required by another selected item. Hover over the information icon to see which asset caused the automatic selection.

What does “dependencies not included” mean?

It indicates that detected dependencies are not part of the current load selection. Use View dependencies and enable Auto include dependent assets or select the needed items manually.

What happens when a required dependency cannot be found?

HighLevel skips the missing dependency and continues processing the remaining assets. You should check the source asset’s references and fix the missing link before relying on the automation.

How do I capture new dependencies in an existing Snapshot?

Refresh the Snapshot with the relevant Workflows or Email Templates selected. The refresh rechecks their dependencies, after which you can load the updated Snapshot.

Does including dependencies remove the need for conflict checking?

No. Dependency inclusion only selects supporting assets. Conflict checking still reviews whether a Snapshot asset should replace or be skipped in the destination subaccount.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.