Flows & schedules

Build repeatable workflows on a canvas, then run them by hand or on a schedule.

Flows are visual workflows you build on a canvas: connected steps that call integrations, run AI, branch, loop, or call HTTP. Schedules run a flow, or send a prompt to an agent, on a repeating timetable.

Use these when the work should happen even if nobody is sitting in a chat thread.

Open Flows

  1. Click Flows in the left icon strip to see every flow in the workspace.
  2. Open a flow to enter the builder (full-width canvas).
  3. Add steps for the systems you already connected, plus AI steps where you need language or judgment.
  4. Save, then run it by hand to verify the path.

Each run has a history you can inspect: what ran, what failed, and what came out. That's the same “what happened, and why” idea as agent artifacts.

A flow can also start when another tool calls its webhook, with the request body as its input.

Build with care

  • Start from a real runbook you already do by hand. Name steps the way the team talks.
  • Prefer existing integrations over one-off HTTP when the connector exists.
  • Keep secrets in Settings, not hard-coded on a node.
  • If a step can change customer data, test on a non-production connection first.

Skills and flows complement each other: skills guide a live agent; flows encode a pipeline you can trigger without a conversation.

Schedules

Open Schedules in the icon strip (agent threads can also produce schedule artifacts).

A schedule is one of:

  • A prompt that starts or continues an agent on a cron-style cadence (“every weekday at 9:00, summarize new tickets”)
  • A flow run with the trigger inputs that flow expects

You can enable, disable, and inspect run history from the same page. Disabled schedules keep their definition so you can turn them back on.

When not to use a flow

If you need a back-and-forth with a person in the loop, start an agent or mention @kluff in a topic. Flows are for paths you could draw on a whiteboard and run again tomorrow.