GoHighLevel Custom Date Reminder Trigger: Setup Guide (2026)
By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 28 October 2026 · 10 min read
Some links below are affiliate links — if you sign up through them, HL Growth Partner may earn a commission at no extra cost to you. It never changes what we recommend.
The GoHighLevel custom date reminder trigger starts a workflow a set number of days before, on, or after a date you have stored against a record. If your business runs on renewals, expiries, service intervals or anniversaries, it is the trigger that stops those dates living in a spreadsheet nobody checks.
This week's workflow trigger setup guide covers how the trigger behaves, how to get clean dates into your fields, the before/after timing logic, and how to test it before a client's renewal list goes live.
Quick Facts
| Trigger name | Custom Date Reminder (Workflows → Add New Trigger) |
| What it reads | A date-type field on the record the workflow is built around |
| Timing options | Before, on, or after the stored date, by a number of days |
| Supported records | Contacts (including opportunity date fields in contact workflows), plus companies and custom objects in their own workflows, per HighLevel's changelog |
| Fields per trigger | One date field per trigger; build a separate trigger or workflow for each date you track |
| Closest relatives | Birthday Reminder trigger, Wait action (wait until a date) |
How the GoHighLevel custom date reminder trigger works
Most triggers react to an event. The Custom Date Reminder trigger instead watches the calendar and compares today's date with the value sitting in a date field, then enrols the record when the two line up with your timing rule.
According to HighLevel's help article on the Custom Date Reminder trigger, the date fields you can pick depend on the workflow type. A contact workflow shows contact date fields, while company and custom object workflows show the date fields that belong to those objects.
That object support is a relatively recent upgrade. HighLevel's changelog announced that the trigger can now evaluate opportunity date fields in contact-based workflows, and date fields on custom objects and companies in their own workflows. For agencies, that means a contract end date on an opportunity can now drive a renewal sequence directly, without copying it onto the contact first.
If you want to see where this trigger sits among all the other options, our complete reference to GoHighLevel workflow triggers maps every trigger by category.
Where a HighLevel date-based workflow trigger earns its keep
Any date that matters to your client's revenue or compliance is a candidate. The ones we build most often for Australian service businesses are:
- Renewals: insurance policies, memberships, retainers and service contracts.
- Expiries: trade licences, first aid or working-with-children certificates and registrations.
- Service due dates: air-con and vehicle servicing, pest inspections, dental check-ups.
- Anniversaries: client start dates, policy anniversaries, wedding anniversaries for photographers and florists.
- Warranty end dates: one of the easiest upsell moments there is.
- Course and event start dates: joining instructions sent on a countdown.
Step 1: set up the date custom field properly
The trigger can only read a field of type Date. A text field that happens to contain "12/03/2027" will not appear in the trigger's field list, and that is the single most common reason a build stalls.
Go to Settings → Custom Fields (or the Fields area for the relevant object), create a new field, choose the date picker type, and give it a plain name like "Policy Renewal Date" or "Licence Expiry Date".
If you are unsure whether a piece of information belongs in a field or a tag, our guide to GoHighLevel tags vs custom fields explains the rule we use: anything with a value that changes or has to be compared goes in a field, never a tag.
Getting dates in: imports, forms and integrations
There are three practical ways to populate the field, and most accounts use all of them:
- CSV import for the existing book of clients. Map the date column to your new date field during the import mapping step, and check the date format before you upload.
- Forms and surveys for new data. Add the date field to an intake or onboarding form so the client or your team fills it once.
- Workflow actions and integrations, such as an Update Contact Field action, a webhook from a policy system, or a Math Operation that adds 12 months to a start date.
Date formats are where Australian accounts get burnt. A month-first export read as day-first quietly turns 3 December into 12 March. Our walkthrough on GoHighLevel CSV import mapping covers how to spot-check a handful of records before trusting a bulk import.
Step 2: configure the trigger, filters and timing
Inside the workflow builder, click Add New Trigger and choose Custom Date Reminder. You then add filters that tell HighLevel which date field to watch and when to fire relative to it.
The core filter is the date field itself. Third-party HighLevel documentation notes that the trigger only enrols records where that field actually has a value, so empty dates simply never fire, which is useful but also means gaps in your data are silent.
From there you choose the timing. The help docs describe "before" and "after" options measured in days, alongside firing on the date itself. You can layer on further filters to narrow who is enrolled; our guide to GoHighLevel workflow trigger filters covers how stacked filters combine.
How the "before / on / after X days" logic plays out
| Timing setting | Example field value | Fires on | Typical use |
|---|---|---|---|
| Before, 30 days | Renewal date 30 November | 31 October | First renewal reminder |
| Before, 7 days | Licence expiry 15 January | 8 January | Urgent compliance nudge |
| On the date | Course start 2 February | 2 February | Day-one welcome and joining link |
| After, 3 days | Warranty end 10 March | 13 March | Extended warranty or service offer |
| After, 14 days | Service due 1 April | 15 April | "You're overdue" follow-up |
For a 30-day, 7-day and 1-day sequence, add three triggers to one workflow, or use one early trigger followed by Wait steps.
The help docs also describe an option to match on the year as well as the day and month. In practice, think of it this way: leave year-matching off for dates that recur every year (anniversaries, annual servicing), and switch it on for one-off dates such as a contract end or a single course start.
Time zones and send times
Date triggers are evaluated by calendar day, and the sub-account's time zone governs what "today" means. For Australian agencies running US or UK clients, set the time zone on each sub-account correctly before you build anything date-driven.
HighLevel does not document a configurable send time on this trigger that we could confirm, so do not rely on the trigger firing at a specific hour. Control the send time with a Wait action set to a time window (for example, business hours on weekdays) straight after the trigger, so nobody gets a renewal SMS at 2am.
Step 3: combine the trigger with Wait, If/Else and tags
- Wait: after a 30-days-before trigger, wait 23 days, then send the 7-day reminder, then wait again for the final notice.
- If/Else: before each message, check a field or tag such as "Renewed" and exit the contact if the job is already done.
- Tags: add a tag like "renewal-due-2026" when the workflow starts, so the team can build a smart list or pipeline view of everyone in the window.
- Goal events: set a goal such as a payment received or appointment booked, so contacts leave the sequence the moment they act.
Finally, write the next renewal date back to the field when the client renews, and allow re-entry in the workflow settings, so the same workflow picks them up again next cycle.
Not on HighLevel yet? Start with a free 30-day trial here — long enough to build everything in this guide before you pay a cent.
Custom Date Reminder vs Birthday Reminder vs wait-until-date
| Tool | Reads from | Starts the workflow? | Best for |
|---|---|---|---|
| Custom Date Reminder trigger | Any date-type field you choose on the workflow's object | Yes, from the calendar | Renewals, expiries, service dates, anniversaries |
| Birthday Reminder trigger | The standard contact Date of Birth field only | Yes, from the calendar | Birthday messages and offers |
| Wait action (until a date) | A date field or fixed date, inside a workflow | No; the contact must already be enrolled | Pausing an active sequence until a deadline |
The key distinction is enrolment. A Wait step only helps contacts already inside a workflow, while the Custom Date Reminder trigger enrols people straight from your database, which suits a large renewal book.
For birthdays specifically, the dedicated trigger is simpler. Our guide to GoHighLevel birthday and anniversary automations shows how to pair the two triggers for full retention coverage.
Step 4: test your date-based trigger before it goes live
- Create a test contact with your own email and mobile.
- Set its date field so the rule lands tomorrow (for a 7-days-before rule, set the date eight days out).
- Publish the workflow and check the enrolment history the next day.
- Confirm each If/Else branch by toggling the relevant tag or field on a second test contact.
Common mistakes to avoid
- Using a text field for dates. Only date-type fields appear in the trigger, so convert text fields before you build.
- Importing dates in the wrong format. Day-first versus month-first mix-ups silently shift every reminder; spot-check before bulk imports.
- Forgetting the time zone. A sub-account left on the wrong zone sends reminders a day early or late for some clients.
- No exit check. Without an If/Else or goal, clients who have already renewed still get "your policy is expiring" messages.
- Not rolling the date forward. If the field is never updated after renewal, the annual cycle breaks after year one.
- Re-entry left off on annual workflows. Contacts who completed last year's sequence may never be enrolled again.
If you want a renewal, expiry or service-reminder system built and tested across your client sub-accounts, book a strategy call with the HL Growth Partner team.
Or if you just need the software first: grab the 30-day HighLevel trial and book us when you're ready to scale it.
Frequently asked questions
What does the GoHighLevel Custom Date Reminder trigger do?
It starts a workflow a set number of days before, on, or after a date stored in a date-type field. It suits renewals, expiries, service due dates and anniversaries, because it enrols records straight from your database based on the calendar.
Which fields can the Custom Date Reminder trigger use?
Only fields of type Date on the object the workflow is built around. Contact workflows can use contact date fields and, per HighLevel's changelog, opportunity date fields, while company and custom object workflows use their own date fields.
Why is my custom date field not showing in the trigger?
The most common cause is that the field was created as a text or number field rather than a date picker. Create a new date-type field, migrate the values into it, and it will appear in the trigger's field list.
Can one workflow send reminders at 30, 7 and 1 day before a date?
Yes. You can add several Custom Date Reminder triggers with different timings to one workflow, or use a single early trigger followed by Wait steps. Add an If/Else check before each message so contacts who have already acted are not reminded again.
How is it different from the Birthday Reminder trigger?
The Birthday Reminder trigger only reads the standard contact Date of Birth field. The Custom Date Reminder trigger reads any date-type field you choose, so it covers every other date your business tracks.
Should I use the Custom Date Reminder trigger or a Wait until date step?
Use the trigger when you need to enrol contacts from your database based on a date. Use a Wait step when a contact is already in a workflow and you only need to pause until a deadline.
Will the trigger fire every year?
It can, but check two settings. Leave year-matching off for recurring dates, and allow re-entry in the workflow settings so contacts who completed the workflow last year can be enrolled again.
How do I test a date-based workflow without waiting weeks?
Create a test contact and set its date field so the timing rule lands tomorrow. Publish the workflow, then check the enrolment history and execution logs the next day to confirm each step ran.
Related Articles on HL Growth Partner
More workflow trigger setup guides
- Contact Changed trigger setup guide
- Task Completed trigger setup guide
- Stale Opportunities trigger setup guide
