The Workflow Library

Library / Customer onboarding / customer-onboarding-015

Add new customer to onboarding reporting static list

Customer onboardingContactMarketing Hub ProfessionalSimple~15 min to buildFull spec

Outcome. Every contact that becomes a customer lands on one static list, giving marketing and CS ops a single, stable count and roster to build reports and dashboards from.

Workflow map Enrollment, branches and actions at a glance customer-onboarding-015
flowchart TD
    A[Lifecycle stage becomes Customer] --> B[Add to New Customers - Onboarding Reporting list]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it as the simplest possible reporting building block, when no dedicated onboarding tracking exists yet on the contact object.
  • UseUse it alongside the deal-based fiches in this category, a static list at the contact level often makes marketing reporting easier than pulling from deal records directly.
  • SkipDo not use it if the team already reports off Lifecycle stage = Customer directly in a saved report or list, a static list adds a second source of truth that has to be kept in sync with no extra benefit in that case.
  • SkipDo not use it if one contact can represent multiple deals or accounts over time, the list will count the person once, not once per deal, decide up front whether that matches what the report needs to answer.
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.1 numbered action
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 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.