Skip to content
Nappai Documentation

Schedule Flow Run

Schedule Flow Run programs a flow of yours to run once, later, on the date and time you choose, with the values you want for its inputs. It can also change a pending run, cancel it or list the ones you have. It is the way for a flow, or an agent, to say “do this tomorrow at 9” without anyone opening the Scheduler.

It only creates one-time schedules, never recurring ones. For something that repeats every week or every day, create the schedule in the Scheduler page.

In this video, an agent with Schedule Flow Run as a tool schedules a reminder two minutes ahead; you see it pending in the Scheduler with the One-time filter, and then run with Success.

When to use it

  • Reminders and follow-ups: “remind me tomorrow at 9”, “call the customer back in two hours”.
  • Deferred sends: an email, a message or a report that should go out at a specific time.
  • An agent that plans work for later and can also cancel it or tell you what is pending.
  • One run per row of a list, for example one follow-up per customer, each on its own date.

Operations

OperationWhat it does
ScheduleCreates a one-time run of the chosen flow.
RescheduleChanges the date or the input values of a pending run.
CancelCancels a pending run.
ListLists the one-time runs of the chosen flow, pending or already done.

Reschedule, Cancel and List only work on the one-time schedules of the flow chosen in the node. A recurring schedule, or one from another flow, answers that there is no pending schedule with that id.

Configuration

FieldWhat it does
OperationSchedule, Reschedule, Cancel or List. The fields below change with it.
FlowThe flow to run, chosen among your deployed flows (the ones with a production version; that version is the one that runs). Press the refresh button to reload the list. The flow this node belongs to is not offered.
Inputs of the chosen flowOnce you choose the flow, each of its inputs appears as a field, like in Sub Project flow. Write a fixed value, connect another component or leave it for an agent to fill in tool mode. Shown in Schedule and Reschedule.
Run AtWhen to run it, in ISO 8601 format, for example 2026-10-23T09:00. Required in Schedule; in Reschedule, leave it empty to keep the stored time.
Time ZoneAdvanced. The zone used for a time written without an offset, for example America/New_York. By default, Europe/Madrid.
Schedule NameThe name shown in the Scheduler page. If empty, the flow’s name and the date are used. Only in Schedule.
Schedule IDThe id of the schedule to change or cancel, the one returned when it was scheduled or listed. In Reschedule and Cancel.
StatusIn List: Pending (the default) shows runs still to come or running now, Done the ones that already ran, All both.
From / ToIn List: only runs programmed within those dates, for example 2026-10-23. A date alone covers the whole day. Empty means no limit.
Max ResultsIn List: how many schedules to return, from 1 to 200. By default, 50.

When an input of the target flow is left empty in Schedule, the flow’s own default value applies. In Reschedule, an empty input keeps the value already stored.

Dates and time zones

  • Write the time as 2026-10-23T09:00, or with an offset such as 2026-10-23T09:00+02:00. Without an offset, the time is read in the node’s Time Zone.
  • A time that is in the past, or that is not a valid date, returns an error that includes the current time, so a person or an agent can correct it.
  • Results show the time twice: in UTC and in the node’s time zone.

Output

Data returns one item per schedule with its schedule_id, the flow, the name, the run time in UTC (run_at_utc) and in the local zone (run_at_local), its status and the inputs it will run with. Cancel returns the id with cancelled: true.

Keep the schedule_id if you will need to change or cancel the run later. In tool mode, an agent gets it in the answer and can use it in its next call; see Tool Mode.

Where the schedules appear

Every schedule you create shows up in the Scheduler page, under the One-time filter, marked as created by a flow. Once a run has happened, it stays in the list for 30 days.

The run belongs to you: it runs as your user, with one of your API keys that has no IP or domain restrictions. If you have no such key, the node returns an error, so create one first.

Example: one reminder per customer (batch)

A flow has a list of customers, each with an email, a date and a message. The “Send follow-up” flow is deployed and has the inputs Email and Message.

  1. Connect the list to the Batch Input of Schedule Flow Run and keep Batch Mode on.
  2. In Operation, choose Schedule; in Flow, “Send follow-up”.
  3. Connect the date of each row to Run At, and the email and message to the fields that appear.
  4. Run the flow: one schedule is created per row, each at its own date, and you can see them in the Scheduler page.

Example: an agent that plans and cancels

An assistant that organises your reminders, with Agent and three Schedule Flow Run nodes in tool mode, all pointing at the “Send reminder” flow: one with Schedule, one with Cancel and one with List. The Run At and the reminder text are filled in by the agent.

  • “Remind me tomorrow at 9 to call Marta” calls Schedule with Run At = tomorrow at 09:00 and gives you back the schedule id.
  • “Cancel it” calls Cancel with that id.
  • “What do I have scheduled?” calls List and the agent reads you the pending runs.

Tell the agent the current date in its prompt (for example with Current Date), so “tomorrow” turns into the right day.

Tips

  • Deploy the target flow first: only flows with a production version appear in Flow.
  • Give the schedules a recognisable Schedule Name if you will look for them in the Scheduler page.
  • To change many runs, use List first and then Reschedule with each id.