Schedules

Schedules let you run a workflow or an agent message automatically at a set time. Choose a recurrence such as every Monday morning or the 1st of each month, and it runs on our servers — no need to keep your browser open.

What is a schedule

A schedule reserves a recurring task to run automatically at a set time. Once registered, two things happen on their own:

• It runs automatically on the server at the recurrence and timezone you set (hourly, daily, weekly, monthly, and so on). You don’t need to keep your computer or browser open, and you don’t have to be logged in when it runs.
• Each run is recorded in a chat, so you can review the results the next time you visit.

What you can schedule

A schedule can target one of two things:

• A workflow: run a saved workflow at a set time. If the workflow requires inputs, you can supply the values to use when you set up the schedule.
• An agent message: schedule a natural-language message to the agent. At the set time, the message is sent to the agent and the task is carried out.

Creating a schedule

The easiest way to create a schedule is to ask the agent in plain language. In the chat, describe what to run and how often.

Ask the agent

Describe the workflow (or message) to run and the recurrence in natural language.

"Run the 'Weekly Sales Report' workflow every Monday at 9 AM"

"On the 1st of every month at 8 AM, send the agent the message
'Summarize last month's sales by sheet'"

The agent understands the request and registers the schedule with the right recurrence.

Recurrence and timezone

Schedules use a cron expression to define the recurrence. For example, 0 9 * * 1 means “every Monday at 9 AM.” When you ask in plain language, the agent converts it to the right expression for you, so you don’t need to memorize cron syntax.

The timezone defaults to Asia/Seoul (Korea time). To run on another region’s clock, mention it in your request, for example “in New York time.”

Everyday phrasing such as “hourly,” “every day at 8 AM,” “every Friday at 6 PM,” or “the last day of each month” works fine — the agent turns it into the right recurrence.

Confirm registration

Once the schedule is registered, its name and recurrence are shown. From then on, it runs automatically when the set time arrives.

Pausing and stopping

A schedule keeps repeating until you stop it, but you can also set conditions for it to stop on its own.

• End date: stops running after a specific date and time.
• Run limit: stops after a set number of runs, counting all attempts — both successes and failures.
• Pause: to stop a schedule temporarily, turn it off, then turn it back on when you need it to resume.

You can set these in plain language too.

"Only run this schedule until June 30"
"Run the weekly report schedule 10 times, then stop"
"Pause the weekly report schedule for now"

Once the end date passes or the run limit is reached, the schedule stops automatically. A stopped schedule can run again if you extend the end date or raise the run limit.

Reviewing results and history

When a schedule runs, the result is recorded in a chat. You can see exactly what the workflow or message did and how it turned out, right in the conversation.

Each schedule also keeps a run history:

• When it ran (run time)
• Whether it succeeded or failed (status)
• The error detail, if it failed
• The credits used for that run

You can also run a schedule once right now, without waiting for the scheduled time, to check that it works. This test run counts toward the run total and credits just like a normal run.

Credits and cautions

Running a schedule consumes credits, just like a regular agent or workflow run. Because it repeats automatically, setting the recurrence too frequently can use up credits quickly.

You can review your remaining credits and usage history on the Subscription & Credits page.

Related docs