The Workflow Library

Library / Sales ops / sales-ops-049

Notify the deal owner and stamp the deal when a HubSpot payment is received (payment links and invoices)

Sales opsDealSales Hub ProfessionalIntermediate~35 min to buildFull spec

Outcome. When money lands through a payment link, a quote with payment, or an invoice, the deal owner gets an internal notification within minutes, and the deal itself carries a payment date and a payment status that anyone can filter, report and forecast on.

Workflow map Enrollment, branches and actions at a glance sales-ops-049
flowchart TD
    A[Deal has an associated payment with status Succeeded, Payment received date unknown] --> B[Set Payment received date = today]
    B --> C[Notify the deal owner by internal email]
    C --> D{Associated invoice balance due greater than 0?}
    D -->|Yes| E[Set Deal payment status = Partially paid]
    E --> F[Create To-do for the owner: chase the balance, due in 2 days]
    D -->|No| G[Set Deal payment status = Paid in full]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when you collect payment inside HubSpot (Commerce Hub) and the only signal today is a processor receipt landing in a shared finance inbox, so reps find out late.
  • UseUse it when deals stay open past the signature until the money clears, and your pipeline reports need a paid versus unpaid split that does not depend on someone remembering to update the deal.
  • SkipDo not use it when payment is handled entirely in an external billing system with nothing synced back into the CRM. No payment or invoice record means nothing to enroll on.
  • SkipDo not use it as is for recurring subscription charges. Without the first-payment filter in Enrollment, the deal owner gets a notification on every monthly charge. See Known pitfalls.
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.6 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.6 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.4 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.