How to Set 14 Days From Today in GHL Workflows: Timer Math, Date Triggers, and Wait Steps in 2026

Last updated: October 26, 2026

To set 14 days from today in a GHL workflow, use the “Wait” step set to 14 days, or use a “Wait Until” step with a calculated date field. For contact-specific date calculations (e.g. 14 days after a form submission date stored as a custom field), use GHL’s math operations in the workflow to calculate the target date. The settings that matter for each approach, and the most common timing errors, are covered below.

Your GHL workflow is firing at the wrong time. The 14-day follow-up is sending on day 9. Or day 17. Or immediately.

Timing errors in GHL workflows are common and often subtle. A “Wait 14 days” step sounds simple but behaves differently depending on whether you count calendar days, business days, or hours, and GHL uses calendar days by default, not business days.

This guide covers every GHL wait and timer configuration, the math operation approach for date-calculated workflows, and the Advance Window setting that stops follow-ups from going out at 2am.

GHL Workflow Wait Step Options: Which to Use When

GHL workflows offer several wait options, and picking the right one prevents most timing bugs. Use Set Period of Time for simple delays, such as a 14-day follow-up. Date-based waits use a specific date or a date field, and the appointment option times messages around a booking. The table shows the gotcha for each wait type.

Date-Based Wait Settings That Decide When a Step Fires

Most “the timer fired at the wrong time” problems come from a few settings inside the Wait action. HighLevel’s current Wait action has eight options. Three of them handle dates: Specific Date and Time, Upcoming Appointment/Booking, and Recurring Schedule. Each one is explained below.

Specific Date and Time

This option waits for a fixed date you pick or a dynamic date from a field. You can set it to continue on that date, a set amount of time before it, or a set amount of time after it.

The setting people miss is what happens when the date has already passed. You can continue, exit the workflow, go to another step, or skip outbound actions. If a contact enters with a date in the past and the setting is “continue”, the next step runs right away. That looks like the wait “did nothing”.

Upcoming Appointment/Booking

This option times the wait around an appointment, a service booking, or an invoice due date. You can fire at the start time, or a number of months, days, hours or minutes before or after it. It uses the same past-date handling, which matters when someone books a slot that starts sooner than your reminder offset.

Recurring Schedule

This option holds contacts until a weekly, monthly or yearly point. Monthly can be a set day or an “nth weekday” such as the second Tuesday. The builder previews the next five scheduled recurrences, so check that preview before you publish.

Advance Window: the business-hours control

There is no separate “business hours” wait step. Instead, Set Period of Time has an Advance Window toggle that limits when the wait may resume to selected days and an hour range. A delay that ends on Saturday night with a Mon–Fri 9–5 window holds until Monday at 9am.

The window controls when the step resumes, not how the time is counted. Weekends still count toward a 14-day delay.

How to Set a 14-Day Wait in a GHL Workflow

To set a 14-day wait in a GHL workflow, add a Wait step, choose Set Period of Time and enter 14 days. It counts full 24-hour days from the moment the contact reaches the step, including weekends. Turn on an advance window if the next message should only send during business hours.

Settings that matter for a 14-day delay

1. Use the Set Period of Time option on the Wait action with the value set to 14 days. It counts full 24-hour days from the moment the contact enters the step. So turn on the Advance Window if the next message should only go out on certain days and hours.

If a wait seems to fire immediately: check that the duration saved, and for date-based waits, check how the step handles dates that are already in the past.

When the 14 days depend on a stored date

When the 14 days count from a date stored on the record rather than from the moment the contact entered, three tools fit. The Specific Date and Time wait can use that date dynamically and run after it. The Custom Date Reminder trigger, covered below, can start the workflow a set number of days after the date. If you need the target date saved on the record, the Math Operation action can add days to a date field.

Date/Time Formatter vs. Math Operation: Which One Does the Date Math

People searching “highlevel date/time formatter” often expect it to add 14 days to a date. Per HighLevel’s own documentation, it does three other things: Format Date, Format Date-Time and Compare Dates. To add 14 days to a date, use the Math Operation action instead.

• Format Date / Format Date-Time converts a date from one structure to another, such as MM/DD/YYYY to YYYY-MM-DD. The result is stored in a variable you can drop into later messages or field updates.
• Compare Dates returns the difference in days between two dates. This helps with “how many days until renewal” logic in If/Else branches.

The From Format must match how the original date is stored. For system fields HighLevel detects it automatically. For custom values or webhook data you select it yourself, and a mismatch is the most common reason the action fails.

To push a date forward or back, use the Math Operation action instead. On Date fields, or on “Current Date” in the sub-account’s timezone, it adds or subtracts days, months or years. It does not handle hours or minutes, does not accept negative values on dates, and the source and destination fields must be the same field type.

One cost note: HighLevel lists the Date/Time Formatter as a premium workflow action. Premium executions are billed per run (one cent each without a Workflow Pro plan). So check your agency’s plan before using it in a high-volume workflow.

Critical Failure Points: Workflow Timing Mistakes

Failure Point 1, Not Setting an Advance Window on Timed Waits: A “Wait 14 Days” step followed immediately by a “Send SMS” action sends the SMS whenever the 14-day period expires. That can be 2am, 3am or a weekend. Turn on the Advance Window on the wait step so it can only resume on the days and hours you choose.

Failure Point 2, Confusing Calendar Days with Business Days: “Wait 14 days” in GHL is 14 calendar days, it counts weekends. If your client means “14 business days” (which equals about 20 calendar days), configure the wait as 20 days or use the Advance Window so the step only resumes on weekdays. The window controls when the step resumes; it does not stop weekends from counting.

GoHighLevel Countdown Timers: Fixed, Recurring and Dynamic

A “GHL date timer” can also mean the visible countdown on a page or in an email, not a workflow delay. HighLevel’s Countdown Timer lives under Marketing. You can place it in emails and in funnel or website pages with the Countdown Timers element in the page builder.

• Fixed counts down to one date and time for everyone, like a launch or a sale end. Set the timezone carefully, because the deadline is the same moment for every visitor.
• Recurring resets automatically after it hits zero, for repeating offers or weekly enrollment cutoffs.
• Dynamic is personal to each contact. It starts when an email is sent or first opened and runs for the duration you choose. You can optionally tie it to a set end time. Reopening the email does not restart it.

Each timer can carry an active link and an expired link. Clicks go to the offer while time remains and to a “this has ended” page afterward. You can sync the same timer between an email and a funnel page so the contact sees one consistent deadline.

The countdown is only visual. It does not stop a checkout or a workflow on its own. So the offer page and any follow-up timing still need to respect the same deadline.

Date Triggers vs. Long Wait Steps

For anything tied to a stored date, such as renewals, anniversaries, contract ends or follow-ups after a service date, a long wait inside a workflow is often the wrong tool. The Custom Date Reminder trigger starts a workflow on a date field, or a set number of days before or after it.

It works with contact date fields and supported opportunity date fields. Custom object and company workflows can use their own date fields.

The practical difference is that a trigger reads the date when the reminder is due. A contact parked in a 60-day wait keeps the timing it had when it entered, even if the date field changes later. When dates in your account get edited often, we lean on the date trigger and keep wait steps for short, relative gaps.

The Consensus Break: Fewer Wait Steps Produce Better Results Than More

The GHL community tends toward complex multi-touch sequences: day 1, day 3, day 7, day 14, day 21, day 30, day 45, day 60. More follow-ups = more opportunities to convert. In our experience, a short, well-timed sequence usually beats a long one.

In our experience, the extra steps rarely pull their weight. Each touch after the first couple of weeks adds maintenance and another chance to annoy the contact, and usually adds far less than the first few messages did.

The most important timing point in any follow-up sequence is day 1, the speed of first response. A reply that arrives within minutes of a form fill lands while the contact is still paying attention. The same message the next morning often does not. Optimize response speed before adding more workflow steps. See our optimized follow-up snapshots.

Related GoHighLevel Guides

• What Is GoHighLevel?
• GoHighLevel Login Guide
• GoHighLevel Training Programs
• GoHighLevel Snapshots Guide

Frequently Asked Questions

How do I add a time delay in GoHighLevel workflows?

Add a time delay in GHL workflows by inserting a “Wait” step. Click the + button to add a step, select Wait, set the duration (days, hours, or minutes), and save. The workflow pauses for the specified duration before executing the next step. To keep the next action inside business hours, turn on the Advance Window on that Wait step.

Can GoHighLevel workflows count business days instead of calendar days?

GHL’s Wait step counts calendar days, not business days, and there is no native option to wait a set number of business days. To approximate it, use a higher calendar-day count (14 business days is roughly 18 to 20 calendar days) and turn on the Advance Window so the step only resumes Monday to Friday during your set hours.

How do I prevent GHL workflows from sending messages outside business hours?

Turn on the Advance Window on the Wait step that comes before the message. It limits when the step may resume to the days and hours you choose, so the email, SMS, or call action waits for the next open window. This prevents messages from sending at 2am or on weekends regardless of when the workflow timer expires.

Does GoHighLevel have a countdown timer for funnels?

Yes. HighLevel’s Countdown Timer, found under Marketing, can be added to funnel and website pages through the Countdown Timers element. It can also go in emails. It offers Fixed, Recurring and Dynamic timers. You can style the units shown and set separate links for when the timer is active and after it expires.

Can the GHL Date/Time Formatter add days to a date?

Not according to HighLevel’s documentation. The Date/Time Formatter formats dates, formats date-times and compares two dates to return the difference in days. To add or subtract days, months or years from a date field or the current date, use the Math Operation action. It doesn’t support hours or minutes on dates.

What happens if a GHL “wait until date” is already in the past?

The Specific Date and Time wait, and the appointment-based wait, have a setting for dates that have already passed. You can continue to the next step, exit the workflow, jump to another step, or skip outbound actions. If it’s set to continue, the next step fires immediately, which is often mistaken for a broken wait.

How do I stop a GHL wait step from resuming at night or on weekends?

Turn on the Advance Window on the Set Period of Time wait. It limits resuming to the days and hours you pick, such as Monday to Friday, 9am to 5pm. A wait that ends outside that window holds until it next opens. It doesn’t convert calendar days into business days.