The Workflow Library

Library / Lead routing / lead-routing-038

Route webinar attendees by session/topic to matching rep

Lead routingContactMarketing Hub ProfessionalIntermediate~35 min to buildFull spec

Outcome. A webinar attendee is followed up by the rep who actually knows that session's topic, instead of a generic post-event blast from whoever is next in a flat rotation.

Workflow map Enrollment, branches and actions at a glance lead-routing-038
flowchart TD
    A[Webinar attendance confirmed with session topic] --> B{Session topic?}
    B -->|Product A demo| C[Rotate to Product A specialists]
    B -->|Industry trends| D[Rotate to industry specialists]
    B -->|Customer stories| E[Rotate to generalist/customer marketing pool]
    B -->|unmapped| F[Rotate to generalist pool + notify sales ops]
    C --> G[Set routed date, notify owner, create call task]
    D --> G
    E --> G
    F --> G
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when the team runs multiple webinar sessions on different topics or products, each with a clear owner or specialist pool best suited to follow up.
  • UseUse it once webinar registration and attendance data reaches HubSpot as a contact property or list membership, whichever your webinar tool integration provides.
  • SkipDo not use it for a single-topic webinar series with one generic follow-up owner; a plain form-submission workflow is simpler.
  • SkipDo not use it to replace a nurture sequence for non-attendees; this fiche is for people who actually attended, route registrants who did not attend through a separate re-engagement nurture instead.
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.15 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 routing 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.