Outcome. A known contact who reads a blog post with a related gated asset, but does not download it, gets one nudge email pointing at that specific upgrade, instead of the download offer being left purely to on-page prompts.
Workflow map
Enrollment, branches and actions at a glance
lead-nurturing-025
flowchart TD
A[Blog page view, known contact] --> B[Set topic_viewed]
B --> C{Wait until gated form submitted, max 4 days}
C -- Submitted in time --> D[No action, already converted]
C -- Timed out --> E[Send: content upgrade nudge]
E --> F[Set content_upgrade_email_sent = true]
When to use it, when not to
- UseUse when a blog post has a clearly matched content upgrade (a checklist, template, or extended guide) and the post gets enough known-contact traffic to justify the automation.
- UseUse it only for known, already-identified contacts. This fiche cannot reach an anonymous first-time visitor; that visitor needs to convert on something first.
- SkipDo not use it on every blog post. Build this for the handful of posts with a real, high-relevance upgrade offer, not the full blog archive.
- SkipDo not stack multiple content-upgrade nudges on the same contact in a short window; one nudge at a time keeps it from feeling like the blog is gating everything behind a form.
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 lead nurturing 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.
