Appearance
Scheduled Tasks with WeWeb AI
You can describe what should happen, and when, and let WeWeb AI build it. It works in the editor and in any assistant connected to your project through WeWeb MCP, like Claude.
The AI can create Scheduled Task workflows and their schedules, set up Scheduled Tasks, schedule a task, and read the execution history to explain what happened.
Create a recurring task
Say what the task does, when it runs, and whether it should start right away:
Create a Scheduled Task workflow that generates the sales report for a period. Add a schedule called "Monthly sales report" that runs on the last day of each month at 9 AM Paris time, with period set to last-month. Leave it off for now.
The workflow and its schedule appear in the editor. Open them to check the actions, the inputs and the Next runs dates before you turn the schedule on.
If you want the schedule to run, say so clearly:
Turn on the Monthly sales report schedule and show me its next three runs.
SCHEDULES RUN IN THE EDITOR
A schedule that's on runs in the editor too, and can send real emails or change real records. Your schedules only reach staging and production when you publish.
Schedule a task for one user
Add an API Endpoint that receives a customerId and a date, and schedules the Send renewal reminder task for that customer at that date. Return the task ID.
The AI uses the Schedule tasks action and binds its inputs for you. Learn more about scheduling from a workflow →
Check how your tasks ran
The AI can read the execution history without changing anything:
In production, show me the Send renewal reminder tasks that failed last week. Look at the latest failure and tell me why it failed. Don't retry anything.
Always name the environment (Editor, Staging or Production) when you ask about tasks, especially before scheduling, cancelling or deleting anything. If you don't, the AI uses the editor and tells you.
For dates like "tomorrow at 9 AM", give a timezone. If the AI can't tell which one you mean, it asks you.
Settings and cleanup
Set up Scheduled Tasks in the editor with WeWeb Tables, with 5 tasks running in parallel.
In the editor, delete the succeeded scheduled tasks that finished before September 1, 2026. Keep the failed and cancelled ones.
Deleting history, or switching storage provider, removes data for good. Only ask for it when you mean it.
To pause a schedule or all tasks, use the Pause and Pause all tasks buttons in the editor: the AI can't pause or resume them for you. Learn more about pausing →
See the Scheduled Tasks tools available through WeWeb MCP →
CONTINUE LEARNING
Scheduled Tasks often start from an API Endpoint. Learn how to build one and call it from your app.