The Workflow Library

Library / Data quality / data-quality-007

Missing company association flag on contact

Data qualityContactSales Hub ProfessionalSimple~20 min to buildFull spec

Outcome. Contacts with no linked company are flagged and queued for a rep to fix, instead of quietly skewing company-level reporting and account-based routing.

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

When to use it, when not to

  • UseUse it when reps create contacts manually without linking a company, or when an import process leaves the association blank.
  • UseUse it as a lightweight, native alternative to data-quality-006 when the portal does not have Operations Hub, or when a purely detect-and-queue approach is enough without automatic domain matching.
  • SkipDo not use it on portals where most contacts are genuinely personal, with no company to link (consumer-facing businesses). The flag will fire on nearly every record and the queue becomes noise.
  • SkipDo not use it expecting an automatic fix. This workflow only flags the record and creates a task; a human still has to search for and attach the right company. See data-quality-006 for the automated match, which needs Operations Hub Professional.
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.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.