The “Custom object schedule date and time” trigger lets you automatically start a flow based on a specific date or date/time property from a custom object. This makes it easy to automate actions that need to happen at precise moments linked to your records.
This is especially useful for:
- Sending booking or shipment reminders
- Triggering follow-up messages after a customer’s purchase
- Automating renewal notifications for subscriptions or memberships
Set up the "Custom object date and time is reached" trigger
- Click on the Custom object schedule date and time trigger node to open up its node form, which will appear on the right side of the screen
- The node form contains the following fields for you to set up the trigger:
-
Set up tab
- Custom object: Select a custom object. If no object is created, you can refer to this Help Center article to create a custom object
-
Object property: Select the date/time property within the chosen custom object. This property will be used to trigger the subsequent nodes in the flow. If the selected custom object does not have an existing date/time property, you will not be able to make a selection.
- Trigger date: Choose whether the trigger should activate on the exact property date or set it to trigger before or after that date
- Trigger time: Configure whether the trigger should execute at the time specified in the property, before or after the property time, or at a custom time
-
Repeat: Choose if the flow should run at repeated intervals. Options include:
- Daily: Flow runs once every day at the selected time
- Weekly: Select one or more weekdays (e.g. Mon, Wed, Fri)
- Monthly: Choose a specific day of the month (e.g. 15th). You can specify which day of the month you would like to trigger this workflow. If the selected day doesn’t exist in a future month (e.g. 29th, 30th, or 31st), the flow will not run that month.
- Yearly: Runs once a year on the specified date and time
-
Filter tab
- Enrollment conditions: When toggled on, you can set specific conditions at the “Filter” tab that the customer must meet in order to be enrolled into the flow
Notes on trigger logic
After a flow using this trigger is published, the system performs a daily check (every 24 hours) to identify custom object records that meet the defined criteria.
- The 24-hour cycle is anchored around the flow’s publish time.
- Once a record matches the trigger conditions, the flow automatically enrolls it and runs the subsequent actions.
If a custom object record is updated after the flow is published, the flow will still use the data from the last check during the current cycle. The update will only take effect at the next scheduled daily check. If the updated record meets the trigger conditions at that time, it will be enrolled into the flow.
Example:
If you publish a flow at 2:00 PM, the system will check every day at around 2:00 PM.
If a custom object record is updated at 5:00 PM, the change will be detected at the next day’s 2:00 PM check.