Outcome. A nurture sequence sends each email during business hours in the contact's own region instead of at whatever time zone the workflow happens to run in, using timezone-based branching combined with the workflow's own send-time controls.
Workflow map
Enrollment, branches and actions at a glance
lead-nurturing-046
flowchart TD
A[On audience, timezone known] --> B{Timezone group}
B -- Americas --> C1[Send during 8am-6pm Americas]
B -- Europe/Africa --> C2[Send during 8am-6pm Europe/Africa]
B -- Asia-Pacific --> C3[Send during 8am-6pm Asia-Pacific]
C1 --> D[Set send_time_nurture_completed = true]
C2 --> D
C3 --> D
When to use it, when not to
- UseUse for a global or multi-region audience where local business hours plausibly affect open and click behavior (B2B audiences checking email during their workday).
- UseUse alongside a workflow's native time-window controls (restricting an action to specific days and hours) rather than trying to calculate exact send times manually.
- SkipDo not use this for a single-region audience; the added branching is not worth it if everyone is already in a similar time zone.
- SkipDo not rely on this for time-sensitive, date-anchored content (an event starting at a fixed global time); that needs explicit date math, not just a business-hours window.
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.5 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.
