Multi-language nurture branch by locale property
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.
OutcomeA contact gets the nurture sequence in their own language, based on a locale property, instead of every contact receiving the same English default regardless of where they signed up.
Workflow maplead-nurturing-030
When to use it, when not to
Use it
- Use once translated versions of the nurture emails exist for at least the top two or three locales by contact volume.
- Use it as a branching layer on top of an existing sequence (for example lead-nurturing-001), not as a brand-new content track; the goal is language parity, not different messaging per locale.
Read more on when to use itShow less
Skip it
- Do not use it if
contact_localeis mostly unset. Confirm the fill rate before building branch content nobody will see. - Do not build this as a custom property branch if the account already
uses HubSpot's native multi-language content and smart content tools to
serve translated versions automatically.
*(check in your portal: whether native multi-language content variants inside a single email, keyed off contact locale, already cover this use case without needing a custom If/then branch at the workflow level)*
Read more on when to skip itShow less
The rest of this spec
Not the workflow you needed?
More in Lead nurturing
50 specs in this section
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.
Here it is. Download the pack now (.zip) The link is in your inbox too.
Read the free Lead nurturing spec