The Workflow Library

Library / Sales ops / sales-ops-020

Create a commission calculation record on a custom object when a deal is closed won

Sales opsDealSales Hub EnterpriseAdvanced~90 min to buildFull spec

Outcome. Every closed-won deal produces exactly one commission record with the amount, rate, and calculated payout captured at close, instead of a spreadsheet someone rebuilds every payroll cycle.

Workflow map Enrollment, branches and actions at a glance sales-ops-020
flowchart TD
    A[Deal stage changes to closed won, rate known] --> B[Custom code: calculate and create commission record]
    B --> C{Calculation failed?}
    C -->|Yes| D[Notify sales ops of failure]
    C -->|No| E[Create commission review task]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when commission math is simple enough to express as one rate applied to one deal amount (flat percentage per deal). This is not a full commission engine; it does not handle tiered accelerators, clawbacks, or split deals on its own (see sales-ops-048 for splits).
  • UseUse it when finance or sales ops wants an auditable record per deal that will not change even if the deal's amount is edited later.
  • SkipDo not use it if your compensation plan varies commission rate by product mix within a single deal; that needs line-item-level logic this workflow does not attempt.
  • SkipDo not use it without Data Hub or Sales Hub Enterprise (or Service Hub Enterprise); custom objects, and workflows that create custom object records, require an Enterprise-tier subscription (https://knowledge.hubspot.com/object-settings/create-custom-objects).
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.7 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, 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 sales ops 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.