Skip to main content

Schedule

Schedules let you plan runs for a Builder so it can execute a specific task automatically, either once or on a recurring basis.

What a schedule does​

A schedule links:

  • A Builder
  • A task to execute
  • A timing mode

When the scheduled time is reached, Brixel starts the Builder and runs the configured task without requiring a manual chat action.

Schedule types​

Recurring​

A recurring schedule runs repeatedly based on a defined cadence, such as a cron expression or a fixed time pattern.

Typical use cases:

  • Generate a daily news summary
  • Send a weekly report
  • Refresh recurring operational workflows

One-shot​

A one-shot schedule runs only once at a planned date and time.

Typical use cases:

  • Send a reminder at a specific moment
  • Prepare a report before a meeting
  • Trigger a single follow-up workflow

After a one-shot schedule has run, it does not plan another execution unless it is created again or explicitly re-enabled.

Key schedule information​

The schedule view helps you track the operational state of each planned run, including:

  • Status: whether the schedule is active or inactive
  • Mode: recurring or one-shot
  • Next run: when the Builder is expected to run again
  • Last run: the latest execution already performed
  • Timezone: the timezone used to compute execution time
  • Runs: how many executions remain or are ready to run

Timezone and timing​

Schedules are evaluated using their configured timezone. This is important for recurring automations, because the same hour can mean different moments depending on the region.

For example:

  • A recurring morning report can run at 08:00 in Europe/Paris
  • Another schedule can run once at a specific time in UTC

Always verify the schedule timezone when a Builder must act at an exact local time.

Run now​

Schedules can also be launched manually with Run now. This is useful when you want to test the configuration or trigger the workflow immediately without waiting for the next planned execution.

Why schedules matter​

Schedules make Builders operational outside the chat flow. Instead of waiting for a user message, a Builder can execute important tasks proactively at the right moment, whether that means a single planned run or an ongoing recurring automation.