Pull any custom object into an automation, from any trigger

Automate more with the new action "Find custom object," which searches for a custom object record in your CRM based on field criteria you define. When a match is found, the custom object is brought into scope so downstream steps can act on it.
Search-driven custom object lookups, from any trigger
Use this action in any automation to search the CRM for a project, ticket, asset, or any other custom object by field criteria. The step searches the CRM for a matching record and brings it into scope so the rest of the workflow can update its fields, branch on its data, or pass it to later actions.
The step exposes a "Found" output and a "Multiple Found" output, so an "if/else" step right after "Find custom object" can route matches, misses, and duplicates to their own branches and handle each scenario cleanly.
Works from any trigger:
 Start from a company update, webhook, contact event, or schedule and still find the right custom object to act on
Supports all custom object types:
 Search across any custom object type defined in your CRM
Branches on the result:
 Found, not found, and multiple found are all separate outputs, so automations handle every scenario cleanly
Accepts dynamic values:
 Pull search criteria from trigger data or previous steps, so the lookup adapts to each run
Example: A webhook fires from your project management tool → Find the matching Project custom object by external ID → On Found, update the status field; on Not found, add a note to the company so an admin can investigate.
Why this matters
Until now, getting a custom object into scope inside an automation meant one of three things: starting from a custom-object-scoped trigger (which limited what could kick the automation off), using "Get custom object from company" or "Get custom object from contact" (which only worked when the records were already linked), or doing the lookup manually outside the automation entirely.
Find custom object closes that gap. Any trigger - a company update, a webhook, a contact event, a schedule - can now reach the right custom object record by searching on any field defined on that type, including system fields like External ID. Search values can pull dynamic content from the trigger or any earlier step, so each lookup adapts to the run. 
Who it's for
Teams building automations that read or update custom object records — projects, tickets, assets, or any custom object type defined in the CRM
Teams looking to replace manual CRM lookups with a configurable, no-code step inside the automation
Teams using workflows that start from non-custom-object triggers (webhooks, schedules, contact events, company updates) but still need to act on a specific custom object
How to access
Go to Business App > Automations > [open an automation] > Add new step
Under "Custom objects," select "Find custom object"
Select the custom object type you want to search (e.g., Projects, Tickets, Assets)
Add search fields. For each, pick a field on the chosen custom object type, use the "is" operator, and enter a value. Select "Add dynamic content" to pull values from previous steps
If you add multiple search fields, choose whether all criteria must match ("And") or any single match is enough ("Or")
Add an "If/else" step after Find custom object to branch on the "Found" output. Configure custom-object-scoped steps on the matched branch and fallback actions on the unmatched branch.
FAQs
What happens if multiple records match my criteria?
The step uses the first match returned. The "Multiple Found" output is set to true
, so you can branch on it to flag duplicates or alert a team member.
What happens if no record matches?
The "Found" output is set to false
 and no custom object is brought into scope. Use an If/else step to handle this. For example, add a note to the company or notify someone.
Can I search by any field on the custom object type?
Yes. Any field defined on the selected custom object type, including system fields like External ID, can be used as a search criterion.
Can I use dynamic content in the search value?
Yes. Select "Add dynamic content" to insert data from your trigger or any previous step. The values are resolved at runtime.
How is this different from Get custom object from company?
"Get custom object from company" retrieves a custom object already linked to a company — it requires a company-scoped trigger and an existing association. "Find custom object" searches by field criteria and works from any trigger, even when no link exists between records.
Learn more
Find custom object
Automation steps reference