Input

Schedule

Fired by an Event (cron)

Schedule starts a job on a repeating timer, so a workflow can run every hour, day, or week with nobody pressing a button. It is the alarm clock for work that has to happen on a regular beat.

How it works

Set the rhythm once and dojobase runs the workflow on its own from then on. Every morning at eight, the first of each month, once an hour: the job fires on that cadence whether or not anyone is at their desk.

This is the trigger for recurring housekeeping and reports. Pull yesterday's rows and email a summary, refresh a dataset overnight, send a weekly digest: anything that should just happen on time, without a reminder to a human.

Under the hood it uses a cron timer, which is simply a standard way to describe "run at these times." You pick the schedule in plain terms and it keeps to it, run after run.

Common use cases

Real situations where this node earns its place in a flow.

Run a nightly batch

Kick off a workflow on a schedule to process the day's accumulated documents or send a recurring digest.

Send a recurring nudge

Fire a flow every morning to remind customers of an unpaid invoice or a missing document.

Poll a source on a timer

Run a fetch-and-compare flow on a schedule to watch a page or feed for changes.

Schedule in a workflow

A simple example of where this node sits in a flow.

Schedule Fired by an Event (cron) Dojobase read Read records from a Dojobase Analyze Underwriting pass Email outbound Send report link

What you set up

  • Choose how often the job should run and at what time.
  • Pick the time zone so "8am" means what you expect.
  • Decide what the job should gather or produce on each run.

Common questions

How often can it run?

As often as every few minutes or as rarely as monthly. You set the pattern that suits the task.

What happens if a scheduled run has nothing to do?

It still starts, then the workflow can simply finish quietly if there is no new work that period.