The Workflow Library

Library / Data quality / data-quality-016

Primary company association enforcement on contact

Data qualityContactData Hub ProfessionalIntermediate~35 min to buildalso needs Marketing Hub ProfessionalFull spec

This spec is filed under Data 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. Contacts linked to more than one company always have a clear primary company on record, instead of leaving reports and account-based routing to guess which one counts.

Workflow map Enrollment, branches and actions at a glance data-quality-016
flowchart TD
    A[Contact has 2+ associated companies] --> B[Custom code: read labeled company associations]
    B --> C{Company count}
    C -->|1| D[Status: Single company - ok]
    C -->|2+, has primary| E[Status: Primary confirmed]
    C -->|2+, no primary| F[Status: Needs review]
    F --> G[Add to review list + create task]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when reps or integrations sometimes link a contact to a second company (a former employer, a partner organization) without ever confirming which one is primary.
  • UseUse it alongside data-quality-006 (auto-association from email domain) and data-quality-007 (missing company flag): this fiche assumes an association already exists and checks which one is marked primary.
  • SkipDo not use it on a portal where contacts are only ever linked to a single company. There is nothing to enforce.
  • SkipDo not use it expecting the workflow to pick a primary company on your behalf when the answer is not obvious, such as two current employers. That decision goes to a human.
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.4 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.7 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, and the custom coded action ships as a ready-to-paste .js file.PDF, Markdown, JSON, code
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.