Home/HighLevel/Features/Workflows/Find object record and find company actions in HighLevel

Workflows and Automation

Find object record and find company actions in HighLevel

In short

The Find Object Record and Find Company actions let a workflow search a custom object or a company record using values received from an inbound webhook. You define which fields to match, decide how to break ties, and then branch the flow based on whether a record is found.

AreaWorkflows · CRM Workflow Actions
Used forPet boarding service, Subscription billing platform, Lead generation agency
Setup steps7 steps in 1 task
Last updatedNovember 17, 2026

01Who this is for

  • Automation engineers who design webhook driven workflows, because they need deterministic record lookups.
  • Small business owners using custom objects to track assets, to update those assets automatically when external data arrives.
  • Companies that manage multiple client companies, to locate the correct company record from lead gen form data.

02Find object records, explained

These actions live inside a HighLevel workflow and only appear when the workflow already contains an Inbound Webhook trigger. The action reads values from the webhook payload and compares them to fields on a custom object or a company record.

You configure filters that use AND logic, choose a tie breaker (Earliest Created or Latest Created) for situations where several records match, and then decide what the workflow should do when a record is found or not found. If the workflow itself was started by the same object type, the action is automatically skipped.

The matched record becomes the current record for any following actions such as Update, Associate, or Clear, allowing the rest of the workflow to operate on that specific record.

03How businesses use find object records

  • Pet boarding service. When a webhook posts a pet name, the business maps the petname field to the Pet object’s "Pet Name" filter. The workflow then finds the earliest created pet record with that name and proceeds to update its status or creates a new pet record if none is found.
  • Subscription billing platform. A billing webhook sends a subscription reference. The platform adds a filter that maps the webhook field to the Subscription object's "External Reference" and optionally adds a status filter. The Find Object Record action selects the latest created active subscription and updates its details.
  • Lead generation agency. A lead gen form webhook includes a company domain. The agency configures a Find Company action with a filter that maps the domain field to the Company object's "Domain". The workflow locates the most recent matching company and enrolls it in an onboarding workflow, or creates a new company record if none exists.

04Before you start

  • An Inbound Webhook trigger must already be present in the workflow.

05How to set up and use find object records in HighLevel

Set up find object record action

  1. Open the workflow that contains the inbound webhook trigger.
  2. Add a new action immediately after the trigger.
  3. Select the "Find Object Record" or "Find Company" action, depending on the workflow type.
  4. Define filters by mapping webhook payload fields to object or company fields, using AND logic.
  5. Choose a tie breaker option: Earliest Created Record or Latest Created Record.
  6. If the workflow starts with the same object type as the trigger, note that this step will be skipped automatically.
  7. Save the action and test the workflow with a sample webhook payload.

06What it looks like in HighLevel

07Settings that matter

  • Filter On (tie breaker). Determines which single record to keep when multiple records satisfy the filters, by selecting either the earliest or the latest created record.
  • Filters. Sets the field to field comparisons that must all be true for a record to match; each filter pairs a custom object or company field with a value from the webhook payload or a fixed value.

08Things to know before you rely on it

  • The action appears only when the workflow includes an Inbound Webhook trigger; otherwise it is unavailable.
  • If the workflow starts with the same object type as the trigger (for example, a "Car created" workflow), the action is automatically skipped.
  • Using non unique identifiers can lead to ambiguous matches; unique fields such as Record ID, External ID, or Domain are recommended for reliable results.

09How it connects to the rest of HighLevel

Michael's take

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

The biggest trap with Find Object Record is assuming it will always return the right item.

If the webhook sends ambiguous or poorly formatted data, the filter may return an unexpected record.

Ensure the webhook sends clean, typed values and consider adding extra filters for deterministic results.

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

Common questions

Common questions about find object records.

When does the Find Object Record action run in a workflow?

It runs after an Inbound Webhook trigger and reads values from that webhook’s payload. If the workflow was started by the same object type, the action is automatically skipped.

What happens if multiple records meet the filter criteria?

The action uses the selected tie breaker setting, either the earliest created record or the latest created record, to choose a single record.

Can I use a fixed value instead of a webhook field in a filter?

Yes, the right side of a filter can be a fixed value or a value taken from the webhook payload’s body or headers.

What branches are available after the Find Object Record action?

Two branches appear: Record Found, where the matched record becomes the current record for downstream actions, and Record Not Found, which you can use to create a new record, alert a user, or stop the flow.

Do I need to add any special configuration to the webhook for this action to work?

The webhook should send clean, typed values (strings, numbers, booleans). Normalizing casing or whitespace in the source data helps when matching on non unique fields like names.

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.