Outcome. Contacts identified as regular listeners or viewers of a branded podcast or video series get a nurture sequence that references the series directly and offers a next step, instead of that audience relationship living only on the podcast platform with no bridge into the marketing database.
Workflow map
Enrollment, branches and actions at a glance
lead-nurturing-048
flowchart TD
A[On podcast/video listener list] --> B[Send: thanks for tuning in]
B --> C[Delay 5 days]
C --> D[Send: related resource]
D --> E[Delay 5 days]
E --> F{Clicked either email?}
F -- Yes --> G[Send: want to talk to us]
F -- No --> H[Send: new episode alert]
G --> I[Set podcast_nurture_completed = true]
H --> I
When to use it, when not to
- UseUse when the podcast or video series host platform can identify individual subscribers by email (a newsletter signup tied to the show, a gated bonus episode, a listener survey) and that data can be synced into HubSpot.
- UseUse to convert passive listening into an active relationship, since podcast analytics alone (download counts) do not identify individuals without an email capture step somewhere.
- SkipDo not use this if the show has no email capture mechanism at all; there is no contact list to build this workflow against.
- SkipDo not assume podcast platform "subscriber" counts equal engaged listeners; many podcast subscriptions are passive and never actually get played.
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.8 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.
