The Workflow Library

Library / Lead routing / lead-routing-027

Book-a-meeting form auto-assigns owner from meeting link used

Lead routingContactSales Hub ProfessionalSimple~20 min to buildFull spec

Outcome. A visitor who books time on a specific rep's meeting link gets that rep as owner automatically, and this workflow only adds the follow-up layer on top: a routed-date stamp, a notification, and a meeting-prep task.

Workflow map Enrollment, branches and actions at a glance lead-routing-027
flowchart TD
    A[Meeting booked via personal link] --> B[Set routed date]
    B --> C{Owner matches booked rep?}
    C -->|Yes| D[Notify owner + create meeting-prep task]
    C -->|No| E[Notify original owner + sales ops of mismatch]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it for personal or team meeting links embedded on a pricing or demo page where the booked rep should become the contact owner.
  • UseUse it to catch the edge case where a contact who already has a different owner books with someone else, so nobody assumes ownership silently changed.
  • SkipDo not use it as your primary routing mechanism if the meeting link itself is a round-robin or collective link; HubSpot's own scheduling logic already distributes those, see Variants.
  • SkipDo not use it if reps use a shared, unbranded booking link with no way to tell which rep the visitor actually intended to reach.
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.5 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.