Skip to content

Partner or referral source nurture track

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.

Contact4 stepsUpdated for HubSpot seat pricing
OutcomeA contact who came in through a specific partner or referral source gets a nurture sequence that acknowledges that relationship, instead of the same generic messaging used for direct organic or paid traffic.
Workflow maplead-nurturing-027
Filter: partner source known, not customer leads to Send: thanks via partner, personalized. Send: thanks via partner, personalized leads to Delay 3 days. Delay 3 days leads to Send: getting started, partner-aware. Send: getting started, partner-aware leads to Set partner_nurture_completed = true. Filter: partner source known, not customer Send: thanks via partner, personalized Delay 3 days Send: getting started, partner-aware Set partner_nurture_completed = true
Filter: partner source known, not customer leads to Send: thanks via partner, personalized. Send: thanks via partner, personalized leads to Delay 3 days. Delay 3 days leads to Send: getting started, partner-aware. Send: getting started, partner-aware leads to Set partner_nurture_completed = true. Filter: partner source known, not customer Send: thanks via partner, personalized Delay 3 days Send: getting started, partner-aware Set partner_nurture_completed = true

When to use it, when not to

Use it

  • Use when partner-sourced volume is high enough, and the relationship valuable enough, that co-branded or partner-aware messaging is worth building and maintaining.
  • Use it to strengthen the referral relationship and shorten time to trust, not as a replacement for whatever nurture track the contact's actual funnel stage calls for.
Read more on when to use itShow less

Skip it

  • Do not use it if partner attribution data is unreliable. A branch fed by mostly-guessed source data undermines the whole point of a partner-aware message.
  • Do not build a separate track per partner if there are more than 3 or 4 active partners; a shared "referred by a partner" message that inserts the partner name as a token scales better than a fully separate branch each.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 3 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 · 4 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 · 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 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