WorqHat
Triggers

Time Based Runs

Category
Trigger
Node Type
Time-Based

Overview

The Time-Based Runs (Time Trigger) node allows you to automatically start workflows at specific times or intervals without manual intervention. It is ideal for scheduling recurring tasks such as data updates, report generation, system cleanups, or automated notifications.

This node ensures workflows are triggered consistently according to your defined schedule, making it a reliable automation starter for time-driven operations.

Description

Trigger workflow on a schedule using CRON expressions, intervals, or natural language.

The Time-Based Runs node executes workflows automatically based on a schedule configuration. It supports three scheduling modes:

  1. Interval – Runs at regular time intervals (e.g., every 5 minutes).
  2. Natural Description – Uses simple human-readable time expressions (e.g., "every Monday at 9am").
  3. CRON Expression – Uses standard CRON format for precise control (e.g., "0 9 * * 1-5" for weekdays at 9am).

You can define only one scheduling mode at a time — the other two must be left empty (null). Once configured, the workflow will automatically start at the specified times without any manual intervention.

This makes it ideal for integrating workflows with scheduled tasks, periodic data processing, automated reports, or time-based automation.

Input Parameters

The Time-Based Runs node accepts one of three scheduling parameters.

intervalstringOptional
Defines how frequently the workflow should run using a CRON step pattern. Example: "*/5" runs the workflow every 5 minutes.
Example
"*/5"
natural_descriptionstringOptional
A human-readable scheduling format. Example: "every 3 hours" or "every weekday at 9am".
Example
"every day at 6pm"
cron_descriptionstringOptional
A full CRON expression for advanced scheduling. Example: "0 9 * * 1-5" to trigger at 9am Monday–Friday.
Example
"0 9 * * 1-5"
Instructions
  • You must provide only one of the above parameters per node.
  • All parameters are simple strings (no nested objects or arrays).
  • Unused scheduling parameters should be left blank (null).
  • Access parameter values in workflows using:
{{timeTrigger.input.interval}}
{{timeTrigger.input.natural_description}}
{{timeTrigger.input.cron_description}}

Example Usage

Example 1: Interval-Based Schedule

Configuration:

{  "interval": "*/10",  "natural_description": null,  "cron_description": null}

Expected Behavior: The workflow runs automatically every 10 minutes.

Example 2: Natural Language Schedule

Configuration:

{  "interval": null,  "natural_description": "every day at 6pm",  "cron_description": null}

Expected Behavior: The workflow triggers once daily at 6:00 PM local time.

Example 3: CRON Expression Schedule

Configuration:

{  "interval": null,  "natural_description": null,  "cron_description": "0 9 * * 1-5"}

Expected Behavior: The workflow runs automatically at 9:00 AM, Monday through Friday.

How to Use in a No-Code Workflow

1

Add the Time-Based Runs Node

Place the node at the start of your workflow. It acts as the entry point for scheduled executions.

2

Select a Scheduling Mode

Choose one of the three available scheduling methods — interval, natural language, or CRON expression.

3

Configure Schedule

  • Use interval for quick recurring runs (e.g., every 5 minutes).
  • Use natural_description for simple human-readable schedules (e.g., "every day at 9am").
  • Use cron_description for advanced timing needs with standard CRON format.
4

Leave Other Fields Empty

Make sure only one scheduling parameter is filled; the others must remain null.

5

Connect to Processing Nodes

Link this trigger node to other nodes (e.g., AI, Database, Email, Storage) to process, store, or react to scheduled events automatically.

6

Activate the Workflow

Once configured, activate the workflow. It will automatically execute according to your defined schedule.

Best Practices

  • Use interval for simple repeat tasks (e.g., every few minutes or hours).
  • Use natural_description for readability in business or team workflows.
  • Use cron_description for complex or system-level automation.
  • Ensure your workflow remains active; paused workflows will not run automatically.
  • Always test schedules with short intervals before deploying long-running jobs.
  • Use descriptive labels or comments to clarify what each scheduled trigger does.
  • Consider timezone implications when scheduling workflows.

Do / Don't

Do
  • ✔️ Use interval for simple recurring tasks.
  • ✔️ Use natural_description for human-readable schedules.
  • ✔️ Use cron_description for advanced scheduling needs.
  • ✔️ Validate your CRON expression before saving (if using cron_description).
  • ✔️ Test with short intervals before production deployment.
  • ✔️ Use descriptive workflow names to identify scheduled tasks.
  • ✔️ Consider timezone settings when scheduling.
Don't
  • ❌ Don't set multiple scheduling parameters — only use one at a time.
  • ❌ Don't use invalid CRON syntax — always validate expressions (if using cron_description).
  • ❌ Don't schedule workflows too frequently without considering system load.
  • ❌ Don't forget to activate the workflow after configuration.
  • ❌ Don't assume workflows run in a specific timezone — verify timezone settings.

Example Workflow Integration

Use Case: Automatically refresh AI-generated content every day.

  1. Trigger Node – Time-Based Runs (runs daily at 9am).
  2. AI Node – Text Generation (generates the day's content.)
  3. Utility Node – Send Email (sends the generated content to subscribers.)

Common Errors

Multiple schedule parameters setErrorOptional
More than one scheduling mode (interval/natural/cron) was filled. Only one scheduling parameter should be set; leave others as null.
Invalid CRON expressionErrorOptional
Incorrect CRON syntax (missing fields or invalid format). Verify CRON format using a CRON validator (e.g., crontab.guru). Ensure all five fields are present: minute, hour, day, month, day-of-week.
Empty scheduleErrorOptional
All scheduling fields were left empty. Provide at least one valid scheduling parameter (interval, natural_description, or cron_description).
Workflow did not startErrorOptional
The workflow is inactive or disabled. Ensure the workflow is active and properly connected. Scheduled workflows only run when the workflow is in an active state.