BetterClaw
Workflows

Run and schedule

Run a workflow now, save its inputs, schedule it in a timezone, publish it, and read what each run did.

Run and schedule

You can run a workflow by hand at any time. To run it on a schedule, set a schedule and Publish it.

Run it now

Click Run now in the top bar. The run carries out the workflow for real, so anything it says it sends is sent. Manual runs use the latest saved version of the document, even if you haven't published it yet.

If the workflow has inputs, the Inputs form opens first so you can check the values.

Inputs

Inputs are settings the workflow uses on every run, such as a recipient address or a threshold. When a workflow has inputs, an input count appears at the top of the document. Click it to open Inputs.

  • Save stores the values with the workflow. Every later run uses them, including scheduled runs.
  • Run Now saves the values, then starts a run.

To apply saved inputs to scheduled runs, publish the workflow.

Set a schedule

Click the schedule control at the top of the document. It reads Only when you run it until you set a schedule. This opens When does it run?.

  1. Pick a cadence:
    • Only when you run it
    • Every few hours
    • Every day
    • Every weekday
    • Once a week
    • Once a month
    • A cron expression
  2. Set the time, day, or interval the cadence needs.
  3. Choose the timezone. The schedule fires at that time in this zone.
  4. Check the summary ("We read that as …") and The next three runs would be preview.

To see the raw cron expression, open Show the cron expression.

If a workflow has a schedule but no timezone, publishing gives it the agent's timezone. If the agent has no timezone, the schedule runs in UTC. A timezone you choose yourself is never replaced. See Agent settings.

Scheduled runs never overlap. If a run is still going when the next one is due, the new one is skipped.

Publish

Scheduled runs use the published version of the document. Click Publish in the top bar to make your current draft the version the schedule runs. Publishing also turns the workflow on. The Publish button appears whenever the draft has changed since the last publish.

If something must be fixed before the workflow can run, such as a connector that isn't connected, Publish is disabled. The list at the top of the document shows what to fix.

Turn a workflow on or off

Once a workflow is published and scheduled, an On / Off switch appears next to its title in the top bar. It also appears on its row in the Workflows list.

  • Off stops scheduled runs. A banner says the workflow is turned off. You can still read it, edit it, and run it by hand. Click Turn it back on to resume.
  • Paused automatically. After three failed runs in a row, the schedule pauses itself. The list shows paused by us and explains why. Fix what broke, then turn the workflow back on or publish it again.
Turn on a workflow is a step in the Getting Started checklist. You complete it by publishing a workflow and leaving it switched on. Drafts and freshly installed directory workflows start off, so they don't count until you publish them.

Read a run

Switch the top bar to Run to see the same document with a run's data filled in. Use the run picker to choose a run. Each run is labeled with its number and when it started. The header shows the run's status, whether it ran on schedule or you started it, and how long it took.

Each section shows how far the run got. Expand a section to see the values it wrote and the calls it made. If a value is too big to show inline, click See the whole value to open it in a side panel. Failed sections open automatically.

To open a workflow's run history from the list, click Logs on its row. Run history is kept for 90 days.

Debug one section

These options help you fix a single step without paying for the whole run again:

  • Run this section (Template view): runs only this section. Values from the sections above it are reused from the last run, at no cost.
  • Replay from here (Run view): returns the values this section produced last time, without calling anything.
  • Re-run from here (Run view): runs this section and every section after it, for real.
  • Freeze this value (Run view): debug runs reuse this section's value instead of working it out again. Scheduled runs ignore frozen values. Click Unfreeze to stop.

Debug runs are labeled This was a debug run and aren't part of the workflow's history.

Approvals

When a run reaches a section marked asks you first, it stops and waits. Nothing is sent until someone decides. You can answer:

  • on the workflow's row in the Workflows list (Approve and carry on / Don't do it), or choose See everything first to open the full approval request, or
  • in Run view, on the waiting section (Go ahead / Don't send it).

Approving continues the run from that section. Declining stops the run there. An approval that nobody answers expires after 24 hours.