Required field enforcement on company creation (domain, industry)
One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.
Professional
Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Sales Hub Professional.
Per-hub plans: also Marketing Hub Professional
On per-hub plans, one of its steps belongs to another subscription: add to static list needs Marketing Hub Professional. Both are required to build it as written. On seat pricing the edition covers both.
OutcomeNew companies missing a domain or an industry value are flagged and routed to a cleanup queue instead of sitting incomplete through their first reporting cycle.
Workflow mapdata-quality-009
When to use it, when not to
Use it
- Use it when reps create company records manually and skip fields that later reporting and segmentation rely on.
- Use it when import processes bypass form validation and create sparse company records.
Read more on when to use itShow less
Skip it
- Do not use it expecting it to block record creation. Workflows react after a record exists; they cannot prevent creation. For hard blocking, enforce required properties at the point of creation in your CRM's record-creation settings where supported (check in your portal: whether a company-create required-property enforcement exists outside forms in the current UI).
- Do not use it for revenue or employee count completeness. That is a broader completeness check, see data-quality-022 for a scored version across several fields at once.
Read more on when to skip itShow less
The rest of this spec
Not the workflow you needed?
More in Data quality
50 specs in this section
Read 12 complete specs before you pay.
One per category, same format as the paid ones. Email only, no card.
We email the link, then a short note when specs change. Nothing else.
Here it is. Download the pack now (.zip) The link is in your inbox too.
Read the free Data quality spec