I’d love to see a native workflow capability for record lookup + direct follow-up actions on the found record, without requiring custom code.
The workflow pattern that’s missing
A lot of workflow use cases need this sequence:
- Lookup / Find / Search Record
- Return the record ID (or, even better, the record itself as a workflow output)
- Use that result in the next action to update/edit that exact record
What would be ideal
1) A native “Find one record” / “Lookup record” action
This action should let users:
- choose the record type to search
- define filter criteria (ideally including association labels)
- support different ways of handling results:
- Option A: return a single best match
- Option B: trigger an error handler or fallback path in case of multiple matches
- Option C: return an array of found record IDs and allow a loop feature in the next step
If the action returns a single best match, it should let users resolve multiple matches deterministically using common HubSpot options such as:
- Most recently created
- Most recently updated
- First created
- or another explicit sort rule
2) A native “Edit record by previous step output” action
This action should let users:
- choose the record type
- use the record ID or record object returned by the previous lookup step
- update properties on that exact record
In other words:
- Lookup Record → output found record / ID
- Edit Record → target record from previous step
Why this matters
Today, this kind of workflow often requires custom code, even for very common CRM automation scenarios.
Examples:
- find a related custom object and update it
- search for a matching record based on properties, then branch on found/not found
- update an existing related record instead of creating duplicates
- run upgrade or sync workflows across connected CRM objects
- find associated records using conditions such as association label + property values
This pattern is standard in automation tools like Zapier, and it would make HubSpot workflows much more powerful if it were fully available natively.
Additional improvement: found / not found handling
It would also be very helpful if HubSpot supported a native branch pattern like:
- record found → continue with update path
- record not found → send notification / fallback path
That would remove the need for workaround logic and make lookup-based workflows much easier to build and maintain.
If HubSpot already has parts of this internally, I’d love to see it exposed more clearly and consistently in the workflow action picker/UI.