Who This Is For / When to Use
Use this update if you want to trigger workflows based on date fields that exist outside of contact records.
This applies when:
You track important dates on Companies (e.g., contract renewal dates)
You manage Opportunities with key timeline dates (e.g., close date)
You use Custom Objects with date fields (e.g., expiration, milestones)
What Changed
Custom Date Reminder triggers are no longer limited to contact date fields.
You can now use:
Opportunity date fields in contact-based workflows
Company date fields in company-based workflows
Custom Object date fields in custom object–based workflows
This allows workflows to run based on the most relevant record type instead of being restricted to contacts.
Supported Date Fields by Workflow Type
Each workflow type determines which date fields are available.
Contact-Based Workflows
Can use Opportunity date fields
Still supports contact date fields
Company-Based Workflows
Can use Company date fields only
Trigger evaluates dates directly from the company record
Custom Object-Based Workflows
Can use Custom Object date fields
Trigger evaluates dates from the selected custom object
How Custom Date Reminder Works
The trigger evaluates a selected date field and starts the workflow based on timing conditions.
You can configure:
Before the date (e.g., 3 days before)
On the date
After the date (e.g., 2 days after)
Optional setting:
Match year with day and month to ensure the exact date is matched, including year
The workflow runs automatically when the defined timing condition is met.
How to Set Up a Custom Date Reminder
Go to Automations → Workflows
Create a new workflow or open an existing one
Select Custom Date Reminder as the trigger
Choose the appropriate date field based on your workflow type
Set the timing (before, on, or after the date)
Add actions to your workflow
Save and publish
Example Use Cases
Opportunity-Based Reminder (Contact Workflow)
Trigger a reminder before an opportunity closes.
Use Opportunity Close Date
Send reminder email or SMS to the contact before renewal
Company Renewal Reminder (Company Workflow)
Trigger internal notifications before a company contract renews.
Use Company renewal date field
Notify account owner or assign task
Custom Object Expiry Tracking
Trigger alerts when a custom object reaches a key date.
Use expiry date on the custom object
Send internal notification or update status
Why This Update Matters
Previously, Custom Date Reminder triggers only worked with contact date fields.
Now you can:
Automate workflows across multiple data types
Eliminate workarounds and duplicate fields
Build more accurate, context-driven automations
This improves flexibility and reduces dependency on contact-only data.
Common Issues and Fixes
Date Field Not Available
Cause: The selected workflow type does not support that object’s date fields
Fix: Ensure the workflow type matches the object (contact, company, or custom object)
Workflow Not Triggering
Cause: Date field is empty or incorrectly set
Fix: Verify the record has a valid date value
Incorrect Timing
Cause: Timing settings (before/after) misconfigured
Fix: Review trigger timing and ensure it aligns with expected execution
FAQ
Can I use Opportunity date fields in all workflows?
No. Opportunity date fields are only available in contact-based workflows.
Can I trigger workflows from Company date fields?
Yes. Use a company-based workflow to trigger from company date fields.
Can Custom Objects trigger date-based workflows?
Yes. Custom object–based workflows can use date fields from that object.
Do I need to create new fields to use this feature?
No. You can use any existing supported date field on the relevant record.
What happens if the date field is empty?
The workflow will not trigger. A valid date must exist on the record.
Can I trigger workflows before and after the same date?
Yes. You can configure timing relative to the date (before, on, or after).