The Workflow Library

Library / Customer onboarding / customer-onboarding-022

Account provisioning request to internal delivery team

Customer onboardingDealSales Hub ProfessionalIntermediate~30 min to buildalso needs Marketing Hub ProfessionalFull spec

This spec is filed under Sales 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. A closed-won deal creates a provisioning task for the internal delivery team with the seat count and plan details already attached, so the new account gets set up without a manual email chain between sales and delivery.

Workflow map Enrollment, branches and actions at a glance customer-onboarding-022
flowchart TD
    A[Deal stage = Closed Won, Provisioning Complete unknown] --> B[Create provisioning task, rotate to Delivery team]
    B --> C[Send internal notification]
    C --> D[Add to Pending Account Provisioning list]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when setting up a new account (licenses, environment, admin access) is a manual step performed by a team other than sales or CS.
  • UseUse it when the deal record already carries the information provisioning needs (seat count, plan tier), so the task does not depend on someone re-typing it into another system.
  • SkipDo not use it if provisioning is fully automated already through a product-side API integration, this fiche is for teams still doing it by hand.
  • SkipDo not use it for renewals, a renewed deal does not need a new account provisioned, exclude Deal Type = Renewal.
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.4 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 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.