Workflows

Schedules

Run a FlowHunt workflow on a timetable with the Scheduled Task trigger, and learn what happens when credits run out.

Open in ChatGPT Open in Claude

A schedule runs a workflow by itself at times you choose, for example a report every Monday at 9:00 or a data check every hour. You set it up with the Scheduled Task step. This page is about scheduling workflows. Re-crawling websites on a timetable is a different feature that lives in Knowledge, see Website crawling.

Add a schedule#

  1. Open the workflow and click Components.
  2. Add the Scheduled Task step from the Triggers category and connect it to the first step you want to run.
  3. Click the step. Under Schedule, click the button that shows the current timetable.
  4. In the CRON Interval dialog, choose a Frequency and, for daily, weekly and monthly schedules, a time. Click Save.
  5. Publish the workflow. See Publishing and versions.

A new Scheduled Task step starts with a daily run at 9:00. Open the dialog to check the time zone it uses.

The frequencies you can pick are each 5 minutes, 15 minutes, 30 minutes, hour, 4 hours and 12 hours, plus daily, weekly and monthly. Weekly schedules let you tick the days of the week, and monthly schedules the days of the month. Five minutes is the shortest interval the picker offers.

Time zone#

For daily, weekly and monthly schedules the dialog shows Time zone: … under the time. The schedule follows that zone’s clock, including daylight saving changes. Interval schedules, such as each hour, do not depend on a time zone.

Pass a message and variables#

Two optional settings sit under Advanced in the step:

  • Input Message is the text the workflow receives when the schedule fires.
  • Variables are named values the workflow can use.

Check the next run#

After you save, the step shows Next run with the date and time. Before the first save it says Save to see next run. To try the workflow without waiting, select the Scheduled Task step and click Run in the toolbar above it. This opens the Run tab and tests the draft.

What to expect#

  • The live version runs. A schedule runs the published workflow. Edits you have not published do not affect it.
  • One schedule per step. Each Scheduled Task step in a workflow creates its own schedule. Deleting the step deletes the schedule.
  • Runs cost credits. Each run spends credits like any other run, for the Scheduled Task step and every step after it.
  • Nobody is watching. Check History in the sidebar to see how a scheduled run went. See Testing and run logs.

Schedules stop when credits run out

If the workspace has too few credits when a run is due, FlowHunt deactivates that schedule instead of retrying it. A deactivated schedule does not start again by itself after you add credits. An AI assistant connected through MCP can resume it, see Connect your AI. See also Out of credits.

If the workspace itself is inactive, the run is skipped and the schedule stays on, so it resumes once the workspace is active again.

Older workflows#

Workflows created on the previous engine do not use the Scheduled Task step. They have a CRON jobs button in the top bar, where you add a schedule with Add new CRON and run one right away with Execute CRON.