How To Disable or Pause Nodes in HighLevel Advanced Workflow Builder

If you manage automations in HighLevel (GoHighLevel, GHL), learning how to pause or disable specific workflow nodes is a small trick that saves time and reduces risk. Instead of deleting actions or rebuilding branches when you want to test, iterate, or temporarily remove behavior, you can toggle nodes off and on without changing the structure of the workflow.

What pausing a node actually does

Pausing a node tells the workflow engine to skip that action for any contact that passes through the workflow while the node is disabled. Contacts continue to flow through the workflow and will still hit active nodes. When you re-enable the node, it behaves exactly like it did before—no rewriting required.

This is useful for testing, staging changes, or creating multiple variations of a workflow that share the same structure but differ in a few actions. You can temporarily turn off an email, an SMS, a webhook, or other actions and toggle them back when you are ready.

Step-by-step: How to pause or resume a node

1. Open the HighLevel Advanced Builder for the workflow you want to edit. This feature is only available in the Advanced Builder mode, not the Standard Builder.
2. Hover over the action node you want to pause. Action nodes display a small pause icon when hovered.
3. Click the pause icon to disable the action. The node will be skipped for any contacts that run through the flow while it is disabled.
4. To re-enable the node, hover over it again and click the play icon. The action returns to active status immediately.
5. Repeat for any additional nodes you want to toggle. Multiple nodes can be enabled or disabled at the same time.

The interface is intentionally simple: hover, click pause, or click play. That simplicity makes it fast to experiment without risking live traffic or deleting work.

Actions versus triggers: what can be paused and why

Not every item in a workflow can be paused. The HighLevel engine separates elements into two broad categories: triggers and actions.

• Triggers start the workflow. Because a workflow cannot run without a trigger, trigger nodes cannot be paused. If you were able to pause a trigger, the workflow would effectively be disabled entirely.
• Actions are the steps that run after a trigger fires—emails, SMS, webhooks, function calls, and so on. Most action nodes can be paused and resumed.

Common triggers that cannot be paused

• Form submissions
• Tag applied/removed
• Appointment scheduled
• Pipeline stage changed

If your goal is to stop contacts from entering a workflow temporarily, disable the trigger outside the builder or add a trigger-specific condition. But do not expect a pause icon on triggers inside the Advanced Builder.

Internal actions: which ones can and cannot be disabled

HighLevel includes a set of internal actions that manage the logic and orchestration of the workflow. Some of these internal actions are integral to how contacts move through the flow and cannot be paused. Others, which are more like "pure actions," can be disabled.

Internal actions you cannot disable

These elements control workflow routing, timers, goals, and logic. Disabling them would break how the workflow runs, so they are protected:

• Wait timers — timing control for when the next action should run.
• Go-to nodes — redirect contacts to another branch of the workflow.
• Conditions — if/else logic that splits paths based on contact attributes or behavior.
• Goal events — complete or trigger other automation behavior when a contact meets a defined goal.
• Drips — sequences that manage staged communication over time.

Internal actions you can disable

Not all internal items are locked. There are internal-style actions that act more like regular actions and can be toggled off:

• Array functions
• Number formatters
• Custom code actions
• Other processing steps that manipulate contact data without controlling routing

If you are unsure whether a node is pausable, hover over it in the Advanced Builder. If you see the pause icon, it can be disabled; if you do not, it cannot.

Real-world example: pausing an email in an email-sorting workflow

Imagine an email campaign workflow that sorts contacts based on engagement. The flow checks whether an email was opened, clicked, or had no action, then sends follow-up emails depending on the branch.

Suppose you want to temporarily stop sending the "opened" email because you are updating its content or scheduling it for a different time. Instead of deleting the action and rebuilding later, pause that specific email action. Contacts that match the "opened" condition will skip the paused email and continue to the rest of the workflow.

When the email content is ready, click play and the original node resumes operation immediately. This makes iterating on copy, timing, and segmentation much safer and faster.

Practical use cases for pausing nodes

Pausing workflow nodes is a flexible tool. Here are practical ways agencies and marketers commonly use it:

• Testing and troubleshooting: Pause suspected failing actions to isolate where an error occurs without tearing down the entire flow.
• Staged rollouts: Release a new email, webhook, or integration for a subset of contacts by toggling the node on and off in different environments or branches.
• Seasonal or temporary changes: Temporarily stop promos, surveys, or automation steps during holidays or maintenance windows.
• A/B or multivariate workflows: Use the pause feature to simulate different workflow variants without duplicating the whole workflow.
• Safe update of content or integrations: Pause an action that calls an external API while updating credentials or endpoint configuration.

Best practices for agencies and operations teams

Use these practices to keep HighLevel workflows predictable and easy to manage at scale.

• Name nodes clearly. Include purpose, channel, and a short date code if it is a temporary action. Clear labels make it easy to see what you are pausing at a glance.
• Keep a change log. Note when nodes are paused and why inside a shared operations document or the CRM record. This prevents accidental gaps in campaigns.
• Use a sandbox or staging workspace for major changes. Pause and test in a sandbox before toggling nodes in production.
• Limit who can edit workflows. Assign workflow edits to specific team roles to reduce accidental toggles.
• Combine pausing with tags or conditions. For temporary behavior changes, consider adding tags or conditions in addition to pausing for safer targeting.
• Monitor reporting and logs. When you pause nodes that affect revenue or conversions, keep an eye on reporting so you can quickly see the impact.

When pausing is not the right tool

Pausing is convenient, but it is not a substitute for deliberate workflow design. If you need to permanently change behavior, refactor the workflow or create a new branch. Use pausing for temporary experimentation or short-term maintenance.

Also, pausing cannot be applied to triggers or core orchestration elements like wait timers and conditions. If you need to stop contacts from entering a flow entirely, manage the trigger or add a blocking condition at the start of the workflow.

How pausing affects contacts already in the workflow

When you pause an action, contacts that reach that node while it is disabled will skip it and continue. Pausing is not retroactive in the sense of modifying past execution history, but it changes the behavior for any contact that reaches the paused node during the pause.

If a contact was waiting for a timed action that is locked (for example a wait timer), the pause will not change the wait itself because wait timers cannot be paused. Planning around which nodes to pause is important when working with scheduled or delayed steps.

Getting access and next steps

The pause/disable node feature is part of the Advanced Builder. If you are using the Standard Builder, switch to the Advanced Builder to access these controls. Advanced Builder unlocks more granular control over HighLevel workflows and automations, which is valuable for agency setups and scaling automation across multiple clients.

If you are new to HighLevel, consider starting a free trial to explore Advanced Builder features, or join the Nexus Hub community for templates, implementation support, and best practices from other agencies. Implementing disciplined workflow management is a core part of scaling CRM and marketing automation operations.

Quick troubleshooting checklist

• Hover the node to confirm the pause icon is present. If not, the node is not pausable.
• Check whether the node is an internal routing element (wait, go-to, condition) if you cannot pause it.
• Use the builder history or operations log to confirm when nodes were toggled.
• If an external integration is failing, pause the webhook or custom code action, fix the integration, then re-enable.
• For large-scale changes, test the pause in a staging environment first.

Summary

Pausing individual nodes in HighLevel Advanced Builder is a safe, efficient way to experiment, perform maintenance, and run variants of your automations without deleting or rebuilding workflow elements. Remember:

• Only action nodes can be paused; triggers cannot.
• Certain internal orchestration nodes like wait timers, conditions, go-tos, goal events, and drips cannot be paused.
• Other internal-style actions—array functions, number formatters, custom code—can be paused.
• The Advanced Builder is required for this feature.

Use clear naming, a change log, and staging to make pausing part of a repeatable workflow management process. For agencies focused on scaling CRM and marketing automation, this small control leads to better testing, fewer mistakes, and more flexible campaign management.

FAQ

Can I pause the trigger so the workflow stops running entirely?

Triggers cannot be paused inside the Advanced Builder. If you need to prevent new contacts from entering a workflow, disable the trigger in the trigger settings or add a blocking condition at the start of the workflow.

Which internal actions cannot be disabled?

Core orchestration elements are not pausable. These include wait timers, go-to nodes, conditions, goal events, and drips. These pieces control timing and routing and must remain active for the workflow to operate correctly.

Can I disable multiple nodes at once?

Yes. You can pause and resume multiple action nodes across a workflow. This lets you quickly switch between different workflow variations without rebuilding branches.

Will pausing a node affect reporting or past records?

Pausing changes behavior for contacts that reach the paused node while it is disabled. It does not retroactively modify past execution logs. Reporting for events that did not occur while paused will reflect the skipped actions.

Is this available in the Standard Builder?

No. The pause/disable node feature is only available in the Advanced Builder. Switch to Advanced Builder to access this functionality.

How should agencies use pausing as part of their operations?

Agencies should use pausing for testing, staged rollouts, and temporary changes. Combine it with clear node naming, a change log, role-based access, and sandbox testing to maintain reliability across client automations.

If a contact is waiting on a wait timer, does pausing an action after the timer affect them?

Wait timers cannot be paused. A contact waiting on a timer will continue along their schedule. Pausing subsequent actions will only affect contacts that reach those actions while they are paused.

Where can I find more documentation or help?

Refer to the HighLevel help documentation for Advanced Builder and pause/disable actions. If you need hands-on assistance, request support or schedule a walkthrough with the HighLevel success team. Joining the Nexus Hub community can also provide templates and implementation guidance.