Outcome. A contact who hits a meaningful usage milestone in a free trial or freemium product gets promoted to Marketing Qualified Lead automatically, so product-driven signals reach sales as fast as score-driven ones.
Workflow map
Enrollment, branches and actions at a glance
marketing-ops-026
flowchart TD
A[PQL signal = true] --> B{Lifecycle stage already MQL or later?}
B -->|Yes| Z[No action]
B -->|No| C[Set lifecycle stage: Marketing Qualified Lead]
C --> D[Set PQL date]
D --> E[Notify sales]
E --> F[Add to Active MQLs list]
When to use it, when not to
- UseUse when your product can push a usage signal into HubSpot, whether through a native integration, a webhook, or a scheduled sync job, and that signal reliably means "this account is engaged enough to be sales-ready."
- UseUse alongside, not instead of, marketing-ops-001's score-driven promotion; a contact can qualify through either path.
- SkipDo not use if product usage data lives only in a separate analytics tool with no connection into HubSpot. This fiche assumes the signal already lands on the contact record; building that connection is a separate integration project.
- SkipDo not assume this fiche relies on HubSpot's native custom behavioral events feature, which is an Enterprise-tier capability. As written, this fiche expects the product signal to arrive as a plain contact property update (via API, native integration, or a Zapier/Make style connector), which keeps it usable on Professional. (check in your portal: if your integration instead uses native custom behavioral events as the signal source, confirm your Marketing Hub tier covers that feature before relying on this fiche's tier as written)
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.3 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.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 marketing 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.
