The Find Object Record action allows workflows to search your account for a specific custom object record using values passed from an Inbound Webhook trigger. By mapping fields from the webhook payload to corresponding object fields, this action dynamically locates the matching record so you can perform the necessary actions on it.

Note: This action is also available in Company-based workflows as Find Company, enabling users to locate company records using webhook data. If the workflow begins with the same object as its trigger (e.g., “Car created” or “Company created”), this action is skipped automatically to prevent unnecessary lookups.

How It Works #

• Navigate to the desired company or object-based workflow in your account. Add an Inbound Webhook trigger, as the action reads its payload (body and headers) to map incoming values.
• Add the Find Object Record or Find Company action and update the name as desired.
• Filter On: Choose one of the following rules to resolve duplicates: Earliest Created Record or Latest Created Record.
• Filters: Add one or more filters to define how records are matched.

Tips:

• Prefer unique identifiers (Record ID, External ID, Domain) for accurate matching.
• Add extra filters (status, location, or type) to reduce ambiguity.

The Find Object Record action bridges incoming webhook data with CRM automation, ensuring your workflows respond intelligently to real-time events. By dynamically locating or creating records based on webhook payloads, it enhances data integrity, minimizes duplication, and supports cleaner, more efficient workflow automation.

Best Practices #

• Ensure webhook payloads contain clean, structured values (string, number, boolean).
• Normalize data (e.g., casing, whitespace) in the source system for consistent matching.
• Always test the action with sample payloads in a staging environment before deployment.

Examples #

Example 1: Find a Pet by Name (Webhook to Lookup) #

Goal: Locate a Pet record using the incoming petname value.

• Filter On: Earliest Created Record
• Filters: Pet Name = inbound webhook body petname
• Flow: Webhook triggers with a petname value, and the action finds the Pet where Pet Name matches.
• Record Found: Update the Pet status and notify the owner.
• Record Not Found: Create a new Pet record and tag it for review.

Example 2: Find a Subscription by External Reference #

Goal: Identify a Subscription record using the webhook’s subscription_ref value.

• Filter On: Latest Created Record
• Filters: External Reference = inbound webhook body subscription_ref, with Status = Active as an optional safety filter
• Flow: Webhook arrives with subscription_ref, and the action finds the latest active Subscription with that reference.
• Record Found: Update plan fields and enqueue the renewal.

Frequently Asked Questions #

What does the Find Object Record action do? #

It searches your account for a custom object record using values from an Inbound Webhook trigger, then lets the workflow act on the matched record.

Is there a version for companies? #

Yes. In Company-based workflows the same action appears as Find Company and locates company records using webhook data.

What trigger does it require? #

It relies on an Inbound Webhook trigger, since it reads the webhook payload body and headers to map values.

How are duplicate matches resolved? #

Use the Filter On setting to pick either the Earliest Created Record or the Latest Created Record.

When is this action skipped automatically? #

If the workflow begins with the same object as its trigger, the lookup is skipped to avoid unnecessary searches.

How can I improve match accuracy? #

Prefer unique identifiers like Record ID, External ID, or Domain, and add extra filters such as status or type to reduce ambiguity.