The Workflow Library

Library / Deal hygiene / deal-hygiene-026

Deal source and original attribution auto-populate

Deal hygieneDealSales Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. Every deal inherits a Deal Source and Deal Source Detail from its primary associated contact automatically, so deals created without manual data entry still carry attribution instead of showing blank.

Workflow map Enrollment, branches and actions at a glance deal-hygiene-026
flowchart TD
    A[Deal created, Deal Source unknown, contact associated] --> B[Copy contact Original Source into Deal Source]
    B --> C[Copy contact Original Source detail into Deal Source Detail]
    C --> D{Deal Source still unknown?}
    D -->|yes| E[Create manual attribution task]
    D -->|no| F[Exit]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when deals are commonly created from a contact record, a workflow-created deal, or a manual "create deal" from a contact, and marketing needs attribution on the deal object itself for reporting, since deals do not track original source the way contacts do.
  • UseUse it as a one-time-at-creation copy, not a live sync. Source data on the contact should not keep overwriting a deal's attribution after the fact.
  • SkipDo not use it for deals created via an integration or API call that never associates a contact at creation. The copy has nothing to read from until a contact is added later.
  • SkipDo not use it if your team already reports off the associated contact's source properties directly and does not need a duplicate on the deal. Skip this fiche.
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.