The Workflow Library

Library / Lead nurturing / lead-nurturing-033

Trade show / conference badge scan nurture

Lead nurturingContactMarketing Hub ProfessionalIntermediate~35 min to buildFull spec

Outcome. Contacts imported from a trade show badge scan get a fast, event-specific follow-up sequence while the conversation is still fresh, with an automatic sales handoff for anyone who engages.

Workflow map Enrollment, branches and actions at a glance lead-nurturing-033
flowchart TD
    A[Import: Trade Show Leads list] --> B[Send: Great meeting you]
    B --> C[Delay 2 days]
    C --> D[Send: Related resource]
    D --> E[Delay 3 days]
    E --> F{Clicked either email?}
    F -- Yes --> G[Create task: engaged, follow up]
    F -- No --> H[Send: Last note]
    G --> I[Set badge_scan_nurture_completed = true]
    H --> I
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse right after an event when badge scan data lands in HubSpot as an imported list, since speed matters more here than for evergreen nurture tracks.
  • UseUse when the booth conversation was general interest rather than a scheduled meeting; scanned badges that already booked a meeting on-site should skip straight to sales, not this nurture.
  • SkipDo not use this for contacts who only stopped by for a giveaway with no real conversation, if the vendor's scan data can distinguish that. Filter those out at import if possible.
  • SkipDo not treat this as a substitute for a same-day thank-you handled manually by the booth team for VIP contacts.
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.