Skip to content

Nurture pause and exit when a meeting is booked

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Marketing Hub Professional.

Contact2 stepsUpdated for HubSpot seat pricing
OutcomeThe moment a contact books a meeting, every nurture track they are in gets a single, shared signal to stop, so no one keeps getting drip emails while a real conversation is already scheduled.
Workflow maplead-nurturing-013
Meeting booked event leads to Set nurture_paused_reason = Meeting Booked. Set nurture_paused_reason = Meeting Booked leads to Add to list: Suppressed - meeting booked. Meeting booked event Set nurture_paused_reason = Meeting Booked Add to list: Suppressed - meeting booked
Meeting booked event leads to Set nurture_paused_reason = Meeting Booked. Set nurture_paused_reason = Meeting Booked leads to Add to list: Suppressed - meeting booked. Meeting booked event Set nurture_paused_reason = Meeting Booked Add to list: Suppressed - meeting booked

When to use it, when not to

Use it

  • Use as a small, shared utility workflow that every other nurture fiche in this category references, instead of building the same exit logic separately in each one.
  • Build this the same day a meetings tool or a "book a meeting" form goes live, before any nurture workflow does, so the suppression list and property already exist when nurture starts.
Read more on when to use itShow less

Skip it

  • Do not treat this as a substitute for lead-routing. Booking a meeting should also trigger assignment or notification logic; that lives in lead-routing, not here.
  • Do not skip wiring the unenrollment trigger into each individual nurture workflow. This workflow alone does not reach into other workflows and stop them, see Steps and Known pitfalls.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 2 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 2 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 1 case, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Lead nurturing spec

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library