GoHighLevel Bulk Workflow Triggers: Companies and Objects

HighLevel shipped a new bulk action on 2026-08-26: select multiple Company or Custom Object records from their list view and fire one workflow across every selected record at once, instead of triggering them one at a time or waiting for the workflow’s own native trigger to catch each record naturally. For an agency sitting on Company records built up over months, or Custom Object records imported before the matching workflow existed, this closes a real gap — until now, getting an automation onto existing records meant opening each one individually or re-importing the whole list just to re-fire a trigger.

This is not the bulk-actions feature you may already know. GoHighLevel has had bulk enrollment and removal for Contacts for a while — consultevo’s own guide to it covers exactly that, and only that. The Company and Custom Object version is new, it is a different button in a different part of the product, and as of this writing no dedicated guide covers it. Here is what it does, the exact steps, and — just as important — what HighLevel’s own documentation does not yet confirm.

What the Feature Actually Does

You are no longer limited to letting a Company or Custom Object workflow fire only when its native trigger condition is met (a Company Created event, a Custom Object field update, and so on). You can now select any number of existing records from the list view and push all of them through one workflow in a single action, whether or not the trigger condition that would normally start that workflow ever occurred on those records.

HighLevel’s own changelog names the practical use cases directly:

• Running an onboarding or follow-up workflow across Companies that already exist in the account
• Triggering a renewal workflow for Policies or Subscriptions modeled as Custom Objects
• Processing a batch of Custom Object records that just came in through an import
• Running a one-time operational workflow across a set of records that will never repeat

The common thread: records that already sit in your account, where you want an automation to treat them as if they had just met their trigger condition today, without rebuilding the workflow’s trigger or touching every record by hand.

The Exact Steps

The path is the same whether you are working with Companies or a Custom Object:

1. Open the Companies list, or the list view for your Custom Object.
2. Select the records you want to run through the automation — individually, or with a select-all control for the records currently loaded on the page.
3. Open the bulk-actions menu and choose Trigger Automation.
4. Pick the workflow to run from the selection dialog. Only workflows built for that object type appear here — a Company-oriented workflow will not show up when you are working from a Custom Object list, and vice versa.
5. Confirm the action.

Two constraints worth knowing before you get to that dialog. First, the workflow you want to run has to already be published — a draft sitting unfinished in the builder will not be an option. Second, this bulk action is currently scoped to Companies and Custom Objects specifically; it is not a general-purpose run-any-workflow-on-any-list button, and it does not replace or extend the older Contact-level bulk enrollment.

Checking What Actually Happened

Once you confirm, the action does not just fire silently in the background with no way to check it. HighLevel logs the run under Bulk Actions, where you can review progress and see the outcome for each individual record the batch touched. Before you trust a bulk trigger against your full list, that screen is the place to look — pull it up immediately after running a batch and read the per-record results rather than assuming the confirmation dialog was the whole story.

What HighLevel’s Own Docs Do Not Confirm

This is the part every agency running this on real client data needs to sit with before using it past a test batch. Both the changelog entry and its linked support article describe what the button does, but neither one states what happens in a few specific, entirely plausible scenarios:

None of this is guesswork on HighLevel’s part being sloppy — it is simply not written down yet, which is common for a feature this new. The safe move is the one the site’s own prior coverage of Company automation has already argued for: do not run a bulk trigger against your full list on day one. Select a small batch — five or ten records, including at least one that is already active in the target workflow if you have one — run it, and read the Bulk Actions result screen line by line before deciding what the tool actually does in your account. Treat the changelog’s description as the intent, and your own test batch as the confirmation.

Where This Fits Against What Companies Already Do

If you are already running Company Object automation to auto-create Companies from Contact Business Names, this bulk trigger is the tool for the records that automation already created but that never separately triggered a workflow — every Company that existed before you built the workflow, or every Company created by a backfill run rather than a live event. Rather than waiting for a future edit to accidentally re-fire a Company-based trigger, or rebuilding the trigger to catch old records retroactively, you select the backlog and run it through directly.

Custom Objects: Renewals and Imported Batches

The Company side of this feature is useful, but Custom Objects are where the bigger win sits, because Custom Objects are what agencies use to model anything that is not a Contact and not an Opportunity — a Policy for an insurance client, a Subscription tier for a SaaS client, a Membership record for a gym or studio client. Any of those objects can carry its own renewal date, and until this feature shipped, the only way to run a renewal workflow against records that already existed in the account was to wait for a field update to trip the object’s native trigger, or open each record and act on it by hand.

That mattered most right after an import. A sub-account bringing in a spreadsheet of two hundred existing Policy records has two hundred renewal dates that already exist on day one — none of them are new field changes, so none of them would naturally fire a Policy-based workflow trigger built around a change event. Before this feature, closing that gap meant either rebuilding the trigger around the import itself, or working through the batch manually. Now the list view for that Custom Object is the tool: select the imported batch, choose Trigger Automation, pick the renewal workflow, and let it run once across the whole set.

The same shape applies to a Membership object carrying a tier and an expiry, or a Subscription object tracking a billing cycle — anything an agency modeled as a Custom Object specifically so it could be automated on later. This closes the gap between modeling the data and actually running automation against records that were already sitting there before the workflow existed.

Rolling This Out Without Breaking Anything

Given how much the changelog and its linked article leave unconfirmed, treat the first run on any given workflow as a test, not a production batch, in this order:

• Pick a workflow with no destructive or costly action in it yet — nothing that sends an SMS, makes a call, or spends a paid API credit — for the very first test run.
• Select five to ten records, including at least one that is already active in that workflow if any exist, so you can see what happens to a record mid-workflow rather than guessing.
• Confirm the bulk trigger, then go straight to Bulk Actions and read every per-record result before doing anything else.
• Only after that batch behaves the way you expected — records that should have been filtered out were filtered out, records already active did what you expect them to do — move to a workflow with a real send or spend action, and still start with a small batch there too.
• Keep a record of which workflows and object types you have verified this way. Behavior HighLevel ships today is not guaranteed to be documented before another agency runs into it the hard way.

Frequently Asked Questions

Does GoHighLevel's bulk workflow trigger work on Contacts?

No. As of this feature's release, bulk-triggering from the list view applies only to Companies and Custom Objects. Contacts have their own separate bulk enrollment and removal feature, which predates this one and works differently.

Is there a limit to how many records I can bulk-trigger at once?

HighLevel's changelog entry and its linked support article do not state a cap. Because the interaction with trigger filters and re-entry rules is also unconfirmed, test on a small batch first rather than assuming a large run behaves predictably.

Can I bulk-trigger a draft workflow?

No. Only published workflows appear in the selection dialog when you choose Trigger Automation, so the workflow has to be finished and live before you can run it against a batch of records.

Will a record already active in the target workflow get re-triggered or skipped?

HighLevel has not published that detail yet. Check your account directly by including an already-active record in a small test batch and reading the per-record result under Bulk Actions before running this against your full list.

We build your GoHighLevel account for you

CRM, pipelines, funnels, SMS and automation — configured for your business, not left for you to figure out.

• Setup (one-time)$850
• Ongoing (per month)$38.80

Get my free setup quote

No obligation quote · reply within 1 business day

This site is independently operated and is not officially affiliated with, endorsed by, or sponsored by HighLevel LLC. We do not receive referral commissions — this is our own flat-fee implementation service.