Outcome. A 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 map
Enrollment, branches and actions at a glance
lead-nurturing-030
flowchart TD
A[Filter: locale known, not customer] --> B{Locale value?}
B -- fr-fr --> C1[Send: Welcome 1 French]
B -- nl-nl --> C2[Send: Welcome 1 Dutch]
B -- de-de --> C3[Send: Welcome 1 German]
B -- es-es --> C4[Send: Welcome 1 Spanish]
B -- Other/default --> C5[Send: Welcome 1 English]
C1 --> D[Delay 3 days]
C2 --> D
C3 --> D
C4 --> D
C5 --> D
D --> E{Same locale check}
E --> F[Send matching Welcome 2]
F --> G[Set locale_nurture_completed = true]
When to use it, when not to
- UseUse once translated versions of the nurture emails exist for at least the top two or three locales by contact volume.
- UseUse 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.
- SkipDo not use it if
contact_localeis mostly unset. Confirm the fill rate before building branch content nobody will see. - SkipDo 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)*
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.21 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 nurturing 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.
