Outcome. A quote that gets marked ready for approval snaps back to draft with a clear note if the deal behind it is missing required fields, instead of going out incomplete.
Workflow map
Enrollment, branches and actions at a glance
sales-ops-034
flowchart TD
A[Quote status changes to Pending approval] --> B{All required deal fields known?}
B -->|Yes| C[End, quote proceeds normally]
B -->|No| D[Set quote status back to Draft]
D --> E[Notify quote owner of missing fields]
When to use it, when not to
- UseUse it when reps regularly send quotes before deal qualification fields are filled in, and finance or sales ops wants a consistent minimum bar before a quote leaves draft.
- UseUse it as a soft gate. HubSpot workflows react to a status change after it happens; they do not prevent the click itself. This fiche catches the incomplete quote a moment later and reverts it, it does not stop the rep from clicking "Request approval" in the first place.
- SkipDo not use it expecting a hard, in-app block. If your team needs a true hard stop before a quote can be sent, look at HubSpot's native quote approval requirements first: (check in your portal: whether requiring approval before sending, configured natively in quote template or approval settings, can already enforce required fields without a workflow, and at what tier this is available).
- SkipDo not use it if the required fields genuinely vary quote to quote; this fiche checks a fixed list of deal properties. Highly variable requirements need a more flexible review process than a workflow can express.
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, 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
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.
