Skip to content

Attach a discovery-call playbook link as a task when a deal is created

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: Sales Hub Professional.

Deal1 stepUpdated for HubSpot seat pricing
OutcomeA new deal automatically gets a task pointing the owner to the standard discovery-call playbook, so reps stop asking sales ops which questions to cover on the first call.
Workflow mapsales-ops-018
Deal is created leads to Create discovery playbook task for deal owner. Deal is created Create discovery playbook task for deal owner
Deal is created leads to Create discovery playbook task for deal owner. Deal is created Create discovery playbook task for deal owner

When to use it, when not to

Use it

  • Use it when your team has a single, current discovery playbook (in Sales Hub's Playbooks tool or elsewhere) and wants it surfaced without a rep hunting for it.
  • Use it as a light-touch nudge, not a hard gate; this workflow does not block anything from happening if the task is ignored.
Read more on when to use itShow less

Skip it

  • Do not use it if you run multiple discovery playbooks by product line or deal type; branch first (see Variants) or reps will get the wrong playbook linked.
  • Do not use it for deals created by a data import or migration; add a filter excluding bulk-created deals if your process distinguishes them (for example, a source property), otherwise every backfilled deal spawns a stale task.
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 · 1 numbered action

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 · 2 cases, 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 Sales ops 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