Date-Based Automation
Run a rule a set number of days before or after a contract end, invoice due date, SSL expiry or other date.
What it does
Most rules react to something happening. A date rule runs on a day worked out from a date on the record instead — for example 30 days before a contract ends, or 7 days after an invoice was due.
Plan: Professional and above.
Dates you can use
| Record | Dates |
|---|---|
| Contract | End date, start date, next billing date |
| Invoice | Due date |
| Bill | Due date |
| SSL certificate | Expiry date |
| Ticket | Due date |
| Deal | Expected close date |
| Proposal | Valid-until date |
Building a date rule
- Create a rule and, under When this happens…, choose On a date.
- Pick the record and the date.
- Choose Days before, Days after or the day itself, and the number of days.
- Add conditions if you need them — for example, only invoices that are still unpaid.
- Add the actions and save.
The rule list describes it in plain words, such as "30 days before the Contract end date".
When it runs
Date rules are checked once a day, early in the morning. Each rule fires once per record per date: if the date on the record changes, the rule fires again for the new date.
The dry run shows the records the rule will fire for over the next 30 days.
Ready-made templates
The Templates tab includes:
- Contract Ends in 30 Days
- Contract Ends in 7 Days — Alert Admins
- Invoice Due Today
- Invoice 7 Days Overdue
- SSL Certificate Expires in 14 Days
- Proposal Expires in 3 Days
Where to go next
Was this article helpful?