The Workflow Library

Library / Data quality / data-quality-018

Association hygiene: deal must have a company association

Data qualityDealSales Hub ProfessionalSimple~20 min to buildalso needs Marketing Hub ProfessionalFull spec

This spec is filed under Sales Hub Professional, and one of its steps belongs to another subscription: add to static list needs Marketing Hub Professional. Both are required to build it as written.

Outcome. Deals created without a linked company are flagged before they skew company-level pipeline reporting and account-based forecasting.

Workflow map Enrollment, branches and actions at a glance data-quality-018
flowchart TD
    A[Deal created] --> B{Company associated?}
    B -->|no| C[Flag: Missing company]
    C --> D[Add to review list + create task]
    B -->|yes| E[Flag: Has company]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when deals can be created without going through a company-first flow: quick-create shortcuts, imports, or integrations that post a deal without an associated company.
  • UseUse it alongside data-quality-007 (missing company on contact), since a deal's company gap often traces back to its primary contact never having one either.
  • SkipDo not use it on deal pipelines that are intentionally company-less, such as individual or consumer deals with no company entity, unless you filter by pipeline.
  • SkipDo not use it expecting an automatic company creation or association. It flags the gap only.
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.2 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.4 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 data quality 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.