GoHighLevel Custom Object & Company Workflows
If you already manage projects in ClickUp and now want deeper CRM automation, GoHighLevel custom object and company-based workflow tools let you build highly targeted processes around more than just contacts and opportunities.
This guide walks you through how to use the new workflow trigger and action options for custom objects and companies so you can connect complex records, sync related data, and keep everything automated inside GoHighLevel.
Understanding Custom Objects in GoHighLevel
Custom objects in GoHighLevel allow you to store and automate data that does not fit into standard records like contacts, companies, or opportunities. Instead of forcing everything into a single object, you can create dedicated structures that match your business model.
Examples of data that can be modeled with custom objects include:
- Subscriptions and contracts
- Projects, tasks, or services sold
- Locations, assets, or equipment
- Memberships and licenses
Once a custom object is created, it can participate directly in workflows via specialized triggers and actions. This makes GoHighLevel much more flexible for advanced CRM automation.
GoHighLevel Workflow Triggers for Custom Objects
Workflow triggers define when a workflow should begin. With custom objects enabled, you get additional options designed specifically for those records.
Custom Object Record Created Trigger
The Custom Object Created trigger fires when a new custom object record is added to your account.
Use cases include:
- Automatically send a confirmation email when a new subscription record is created.
- Notify an internal team when a new project custom object is added.
- Start an onboarding sequence immediately after a custom object is generated from a form, API call, or other automation.
Key configuration points:
- Select the specific custom object you want to monitor.
- Optionally add filters to restrict which records start the workflow.
- Build actions that use data from the custom object throughout the automation.
Custom Object Record Updated Trigger
The Custom Object Updated trigger starts a workflow whenever a selected custom object is modified.
Examples of when to use this trigger:
- Run follow-up actions when a status field inside the custom object changes.
- Send alerts to a sales rep when an amount or date field is updated.
- Move related opportunities when specific custom object attributes are edited.
You can:
- Specify the custom object type.
- Filter on updated fields or conditions to avoid unnecessary runs.
- Use the updated data in later workflow steps.
Custom Object Record Deleted Trigger
The Custom Object Deleted trigger fires when a custom object record is removed.
This is useful for:
- Cleaning up related child records when the parent record is deleted.
- Stopping or adjusting ongoing workflows that depend on that custom object.
- Notifying an admin that critical data has been removed.
GoHighLevel Workflow Actions Using Custom Objects
In addition to triggers, GoHighLevel provides workflow actions specifically designed to work with custom objects. These actions allow you to look up or manipulate records in the middle of a workflow.
Custom Object: Get or Create Record
The Get or Create Record action checks whether a custom object record exists that matches your criteria and either loads or creates it.
Typical use cases:
- Ensure a subscription or membership record always exists for a contact.
- Prevent duplicate custom object records when starting new workflows.
- Create new custom entries only when they are missing.
How to configure:
- Select the custom object type.
- Define the matching conditions (such as unique ID or linked contact).
- Choose what should happen if no record is found (create a new one).
Custom Object: Find Related Records
The Find Related Records action allows you to retrieve records that have a relationship with another object in GoHighLevel, such as contacts, companies, or other custom objects.
Use this to:
- Locate all custom records attached to a single company.
- Gather multiple related items (for example, all projects linked to a client).
- Build workflows that branch depending on how many related items exist.
This action is helpful when you want to process or reference multiple records inside a single workflow run.
Company-Based Workflow Triggers in GoHighLevel
Beyond custom objects, GoHighLevel also supports workflow triggers tied directly to companies. This is ideal for B2B users who center their processes around organizations instead of individual contacts.
Company Created Trigger
The Company Created trigger runs whenever a new company record is added.
Ways to apply this trigger:
- Launch a full onboarding or welcome workflow for new organizations.
- Assign an account manager immediately after creation.
- Sync the company data with other platforms through integrations.
Company Updated Trigger
The Company Updated trigger detects changes to existing company records and starts a workflow accordingly.
Typical scenarios:
- React to lifecycle stage changes (for example: Prospect to Customer).
- Send renewal reminders based on updated contract dates.
- Alert the team when company size, revenue, or status fields change.
You can narrow down activity by adding conditions so only certain updates launch a workflow.
Company Deleted Trigger
The Company Deleted trigger fires when a company record is removed from GoHighLevel.
Possible uses:
- Clean related custom objects or opportunities tied to that company.
- Stop nurture campaigns for users connected to that organization.
- Log removal events for compliance or reporting.
Company-Based Workflow Actions in GoHighLevel
Company workflow actions let you look up or manage company data from inside any workflow, not just company-focused automations.
Company: Get or Create Company
The Get or Create Company action ensures a company record exists that matches the criteria you define.
Key benefits:
- Avoid duplicate companies when creating records from form submissions or imports.
- Link contacts to the correct company in an automated way.
- Standardize how new organizations enter your pipeline.
Basic configuration steps:
- Choose your matching fields (for example: company name or domain).
- Decide when a new company should be created.
- Use the resulting company record in subsequent steps.
Company: Find Related Records
The Find Related Records action for companies lets you pull in records connected to a specific organization.
Common examples include:
- Finding all contacts linked to one company.
- Listing opportunities or deals attached to an organization.
- Locating custom object records that belong to that company.
This action helps you build automations that understand the full organizational context, not just individual contacts.
Best Practices for GoHighLevel Custom Object & Company Workflows
To get the most from these features, follow a clear structure when designing your GoHighLevel workflows.
- Define relationships first: Map how contacts, companies, and custom objects connect before building flows.
- Keep naming consistent: Name custom objects and fields in a way that is easy for your team to understand.
- Use filters generously: Add conditions to triggers and actions so only the right records enter automation.
- Test with sample data: Run workflows with test records to confirm that relationships and actions behave as expected.
More Resources for Optimizing GoHighLevel
You can review the original documentation for these features in the official help center article here: Custom Object and Company-Based Workflow Actions & Triggers.
For implementation strategy, funnel architecture, and advanced CRM consulting around platforms like GoHighLevel, visit Consultevo for expert guidance.
By combining custom objects, company records, and the dedicated workflow triggers and actions detailed above, you can build highly tailored automations that mirror your real-world business processes inside GoHighLevel.
Need Help With ClickUp?
If you want expert help building, automating, or scaling your GHL , work with ConsultEvo — trusted GoHighLevel Partners.
“`