Outcome. A deal reaching a late stage without the required custom object record attached, for example a Project or a License record your business tracks separately from the deal, gets flagged before it closes with a gap that blocks provisioning later.
Workflow map
Enrollment, branches and actions at a glance
deal-hygiene-040
flowchart TD
A[Deal reaches pre-close stage, no custom object association] --> B[Set Missing Custom Object Flag = true]
B --> C[Create task for owner]
C --> D[Notify owner]
D --> E[Delay 2 business days]
E --> F{Still no association?}
F -->|yes| G[Notify manager - escalation]
F -->|no| H[Reset flag to false, exit]
When to use it, when not to
- UseUse it when your portal tracks a business entity as a custom object (not a deal, contact, company, or ticket) and every deal past a certain stage is supposed to be linked to one.
- UseUse it as a late-funnel safety check, not the mechanism that creates the custom object record itself, that association should already exist from an earlier step in the process.
- SkipDo not use it if the "custom object" in question is really something that fits a native object better, for example line items or products, those are native, not custom, and do not need this pattern.
- UseCustom objects require an Enterprise subscription on Marketing, Sales, Service, Data, Content, Smart CRM or Revenue Hub (https://knowledge.hubspot.com/object-settings/create-custom-objects), so an account below Enterprise cannot run this fiche at all. (check in your portal: the per-tier cap on custom object types and records for this portal, since the published catalogue, not the knowledge base, carries those numbers)
The preview ends here. Six sections are in the library.
counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.3 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.5 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.5 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library,
149 EUR
or the deal hygiene pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.
