This idea is intended for developers, technical admins, and operations teams who routinely troubleshoot workflows, manage enrollments, and work directly with HubSpot object records.
Problem:
When troubleshooting workflow enrollment or manually enrolling records, the search experience only supports searching by an object’s name. In many real-world implementations, names are not unique or are reused across records. For example, our organization names all Order Product records after the product itself, which means dozens (or hundreds) of records can share the exact same name.
In these scenarios, locating the correct record becomes slow and error-prone. Teams often rely on record IDs when working through APIs, logs, integrations, or support tickets — but those IDs cannot currently be used in the enrollment search experience.
Proposed Improvement:
Allow workflow enrollment and troubleshooting search to support Object ID in addition to object name.
This could be implemented as:
- A dual search field (name or ID), or
- Automatic detection when a numeric/record ID is entered, or
- A toggle allowing users to search by Name vs. ID.
Why This Matters:
- Enables precise targeting of records during troubleshooting
- Eliminates ambiguity when multiple objects share the same name
- Aligns workflow tooling with how developers and admins actually identify records (via IDs)
- Reduces time spent locating records during support, QA, and operational workflows
- Improves reliability when manually enrolling objects tied to integrations or external systems
For teams operating at scale — especially those using APIs, custom objects, and automated pipelines — Object ID is the primary identifier. Supporting ID-based search in workflow enrollment would significantly improve accuracy and efficiency with minimal UI complexity.
This small enhancement would meaningfully improve the troubleshooting experience and reduce friction for technical users working across workflows and integrations.