Time triggers are configured inside an existing workflow rule. These steps add a time-dependent action to a rule that already exists. For new automation, build a scheduled path in a record-triggered flow instead, but the field concepts below map directly.
- Open the workflow rule
In Setup, go to Workflow Rules and open the rule you want, or create one. Confirm its evaluation criteria is "created" or "created, and any time it's edited to subsequently meet criteria," because the third option blocks time triggers.
- Add a time trigger
In the Time-Dependent Workflow Actions section, choose to add a time trigger. Enter the offset number, pick days or hours, and choose before or after.
- Select the date field
Pick the standard or custom date or date/time field the offset measures from, such as Close Date or Created Date. This field anchors the schedule, so make sure it is reliably populated.
- Attach actions to the trigger
Add the field updates, tasks, email alerts, or outbound messages that should run when the trigger fires. A trigger with no actions still sits in the queue but does nothing useful.
- Activate and monitor
Save and activate the rule. Watch scheduled items in Setup under the Time-Based Workflow queue, where you can review or remove pending actions.
A whole number from 0 to 999 that sets how far from the date field the trigger fires.
The unit applied to the offset number. Hours give tighter timing; days suit deadline reminders.
Direction relative to the source field. Before is for advance warnings; after is for follow-ups.
The standard or custom field whose value the offset is calculated from. A blank value means no action is scheduled.
- You cannot add a time trigger to a rule set to "created, and every time it's edited." Salesforce blocks it.
- Time-based workflow runs on the org time zone, not the running user's, and actions fire in a batch within about one hour of the scheduled moment.
- If a later edit makes the record stop meeting the rule criteria, queued time-dependent actions are removed and never run.
- Removing all actions from a time trigger does not delete the trigger; it stays queued and counts against the hourly time-trigger limit.