The Workflow Library

Library / Customer onboarding / customer-onboarding-044

Contract signature confirmation notice to legal and ops

Customer onboardingDealSales Hub ProfessionalSimple~20 min to buildFull spec

Outcome. The moment a signed contract is recorded on a deal, legal and operations get one notification with the key terms, instead of waiting to hear about it secondhand or digging through the deal record themselves.

Workflow map Enrollment, branches and actions at a glance customer-onboarding-044
flowchart TD
    A[Contract Signed Date known] --> B[Send notification to legal and ops]
    B --> C[Set Legal Ops Notified Date]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when legal or ops need to know about a signed contract promptly for their own recordkeeping, entitlement setup, or invoicing schedule, independent of the CS handoff in customer-onboarding-001.
  • UseUse it when contract signature is tracked as a property on the deal (set either manually or by an e-signature tool integration), not only inferred from the deal stage.
  • SkipDo not use it if Deal stage reaching Closed Won already reliably implies a signed contract and no separate legal review step exists, use customer-onboarding-001 or customer-onboarding-030 instead, adding this on top would be a duplicate notification.
  • SkipDo not use it as the trigger for provisioning or billing setup, those are customer-onboarding-022 and customer-onboarding-030, this fiche is a notice only.
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.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.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.