Outcome. Every time the onboarding owner on a deal changes, a timestamped note is logged on the deal showing who it moved from and to, so ownership history survives even after several handoffs.
Workflow map
Enrollment, branches and actions at a glance
customer-onboarding-046
flowchart TD
A[Onboarding Owner changes, Onboarding Start Date known] --> B[Custom code: read property history, compare last two values]
B --> C{Was this an initial assignment?}
C -->|Yes| D[Skip, no note logged]
C -->|No| E[Create audit note, increment reassignment count]
E --> F{Code error?}
F -->|Yes| G[Notify operations owner]
F -->|No| H[End]
When to use it, when not to
- UseUse it when onboarding ownership changes often enough (parental leave, role changes, workload rebalancing) that "who had this before" becomes a real question during a review or an escalation.
- UseUse it if you have Data Hub (or any hub tier that includes custom coded actions) available, this fiche needs the property history API to capture the previous value, which a native workflow action cannot read on its own.
- SkipDo not use it if reassignment is rare in your team, a manual note on the rare occasion it happens is simpler than building and maintaining this workflow.
- SkipDo not use this as a substitute for a proper permissions or activity log if you need it for compliance purposes, this is a lightweight CRM-native trail, not an exported audit record.
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.4 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 customer onboarding 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.
