The Workflow Library

Library / Sales ops / sales-ops-021

Route a commission record to a manager for approval via a custom object workflow

Sales opsCustomSales Hub EnterpriseAdvanced~60 min to buildFull spec

Outcome. A newly calculated commission record reaches the right manager for a yes or no decision automatically, instead of sales ops chasing an approval over email or Slack.

Workflow map Enrollment, branches and actions at a glance sales-ops-021
flowchart TD
    A[Commission status becomes Calculated] --> B[Set approval status = Pending review]
    B --> C[Create approval task for manager]
    C --> D[Notify approver by email]
    D --> E[Wait until approval status changes, cap 5 business days]
    E --> F{Approved?}
    F -->|Yes| G[Set Commission status = Approved]
    F -->|No or timeout| H[Notify sales ops: overdue or rejected]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it directly on top of sales-ops-020: once a commission record exists with status Calculated, this workflow takes it from there.
  • UseUse it when every commission record needs the same manager to sign off, or when the approver can be derived from the deal owner's reporting line.
  • SkipDo not use it if approval needs multiple sign-offs (for example, both a sales manager and finance) in sequence; this base version only routes to one approver. See Variants for a two-step version.
  • SkipDo not use it if commission amounts vary so widely that a flat approval process misses obviously wrong records; pair with a threshold branch (see Variants) so unusually large amounts get extra scrutiny.
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.7 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 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.