Scheduled Triggers
Audience: Administrators, Solution Architects, and Developers
Purpose: Explains each scheduled trigger type in Kizen: what it does, when it fires, and the behavioral details that affect how Agentic Workflows respond to time-based conditions.
Overview
Scheduled triggers fire based on time rather than a user action or data change. Instead of responding to an event as it happens, scheduled triggers calculate when a future execution should occur and queue it accordingly.
Activity Past Due
Fires when a scheduled activity's due date and time passes without the activity being completed.
This trigger is useful for Agentic Workflows that need to escalate or follow up when an activity is not completed on time. For example, sending a reminder to the Record owner or reassigning the activity after a defined grace period.
On or Around Date
Fires based on a date field on a Record, running a set number of days before or after that date.
This is the most configurable scheduled trigger and has several behavioral characteristics that are important to understand before use:
Future scheduling only: When the Agentic Workflow is activated, Kizen evaluates existing Records and schedules future executions based on their current date field values. Records whose date field values are already in the past at activation time will not have executions scheduled. This trigger is not retroactive.
Recalculates on field change: If the date field value changes after an execution has been scheduled, the scheduled execution is recalculated to reflect the new date. Changing the field moves the scheduled run. It does not create an additional execution.
Business calendar interaction: When a calculated trigger date falls on a non-business day, the execution is adjusted to the nearest business day as defined by your business calendar configuration. The actual execution date may differ from the raw calculated date when non-business days are involved.
Single-instance scheduling: This trigger schedules only one future execution at a time. For recurring or annual patterns, the next occurrence is scheduled only after the current one fires. Multiple future occurrences are never queued simultaneously.
Daylight saving time nuance: Scheduled execution times may appear to shift when a DST transition occurs between when the execution is scheduled and when it runs.
Scheduled
Fires on a user-configured recurring schedule. Only available on Global Agentic Workflows.
Because Global Agentic Workflows do not run in the context of a specific Record, this trigger initiates executions on a time-based cadence. For example, every day or every week, independently of any Record event. It is the appropriate choice when an Agentic Workflow needs to run periodically without being tied to a specific Record change.
A common pattern for Global Agentic Workflows is to assign a Record variable at the start of the Agentic Workflow, giving subsequent steps a Record context to operate against even though the trigger itself is not Record-scoped.
What's Next?
Continue to Webhook Triggers to understand how Agentic Workflows can be initiated by inbound HTTP requests from external systems.
Last updated
Was this helpful?