Automation FEATURE

Scheduled, Timezone-Aware Journeys

Schedule journeys around the calendar—not server time.

Build journeys that start, pause, and resume according to the right operating timezone. Configure calendar-aware timing for weekdays, monthly dates, durations, and specific dates while keeping each flow’s schedule predictable.

Create a flow

Key Capabilities

Flow timezone override

Set a timezone for a flow or inherit the account’s configured timezone.

Calendar-aware pauses

Continue on a weekday, an nth weekday, a day of the month, or a specific date and time.

Duration-based timing

Pause an enrollment for a configured amount of time before continuing.

Durable scheduled resume

Keep a pending resume action so the enrollment can continue when it becomes due.

Local-time evaluation

Resolve calendar boundaries in the effective timezone before converting them to a scheduled instant.

Early interaction resume

Continue early after selected interactions when the following Conditional branch matches.

How It Works

Set the flow timezone

Choose a flow timezone or leave it blank to inherit the account timezone.

Add a Pause block

Select a duration, weekday, nth weekday, day-of-month, or specific-date pause.

Configure the timing

Enter the required calendar or duration settings and review the displayed timezone.

Activate the flow

Enrollments that reach the Pause block receive a scheduled resume action.

Continue automatically

The enrollment advances when the scheduled time arrives.

Optionally resume early

Enable selected interaction events when the following Conditional block can handle them.

Use Cases

Resume lead follow-up during your team’s operating hours.
Hold a nurture journey until the next matching weekday and local time.
Schedule monthly reminders using a day-of-month boundary.
Coordinate separate regional flows with different timezone overrides.
Wait until a known event or campaign date before continuing.
Accelerate a paused journey when a contact interaction matches the next condition.

Build automations that follow the calendar your team operates in. A flow can use its own timezone or inherit the account timezone, giving time-based steps a predictable local reference instead of relying only on server time.

Add a Pause block to wait for a duration, the next matching weekday, an occurrence such as the second Tuesday, a day of the month, or a specific date and time. Drip Drop resolves calendar boundaries in the effective flow timezone and schedules the enrollment to continue at the resulting instant.

For interaction-driven journeys, a pause can also resume early when a selected event matches a following Conditional branch. This combines planned timing with responsive automation without claiming that every contact receives messages in their own timezone.

Why teams build on Drip Drop

Drip Drop is bring-your-own-account automation: you keep your own sending reputation, pricing, and data, and Drip Drop handles the flows, templates, contacts, and reporting on top — no marked-up credits, no lock-in.