The Workflow Library

Library / Data quality / data-quality-033

Orphaned deal cleanup list (no owner, no contact, no company)

Data qualityDealData Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. Deals missing an owner, a contact, or a company land on one list ranked by amount, so cleanup effort starts with the deals that actually matter financially instead of a random crawl through the pipeline.

Workflow map Enrollment, branches and actions at a glance data-quality-033
flowchart TD
    A[Deal missing owner, contact, or company] --> B[Set Orphan flag: Missing owner or association]
    B --> C[Create task for sales ops owner]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it on pipelines where deals can be created without an owner or an association, from an integration, an import, or a form-to-deal automation, and these gaps quietly hurt forecast accuracy and reporting.
  • UseUse it as an ongoing filter-based flag, not a one-time cleanup. New orphaned deals keep appearing as long as the creation paths that allow it stay open.
  • SkipDo not use it to auto-assign an owner or auto-associate a record. Guessing the right owner or contact from partial data is a decision for a human, this fiche only surfaces the gap.
  • SkipDo not use it on pipelines where deals are deliberately created without a contact or company at an early stage, for example a pure inbound unqualified stage. Add a stage exclusion so early-stage deals are not flagged before an association is expected.
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.2 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.