Scheduled Tasks are available on paid plans. Each run uses the API usage budget of the workspace where the task is saved.
Create a Scheduled Task
1
Choose a workspace
Switch to Personal or the team workspace where the task should run. Tasks do not move between workspaces.
2
Open Scheduled
Choose Scheduled in the sidebar, then select New task or start from a template.
3
Write the prompt
Give the task a clear name and include everything Babbily should know when nobody is present to answer a follow-up question.
4
Choose the model and frequency
Select a supported model, schedule, time, and time zone.
5
Choose Plugin access
Select the connected Plugins the task may read from. Save the task when the summary matches what you expect.
Choose a schedule
Babbily stores the task’s time zone and shows its next run using that zone. Daylight-saving changes are handled from the selected local schedule.
Run, pause, and review a task
Choose Run now to start an extra run without waiting for the next scheduled time. Babbily prevents the same task from starting a second run while one is already active. Use the task switch to pause or resume future runs. Expand Recent runs to review queued, running, completed, skipped, failed, or canceled runs and open the chat created by a completed run. Scheduled run chats do not appear in the normal Library or recent-chat list. Open them from the task’s latest result or Recent runs. Deleting a task removes that run history from Scheduled, so open or save anything you need before deleting it. If a task’s selected model is retired, Babbily can use an available replacement and labels the run accordingly. Edit the task to choose a replacement yourself.Use Plugins safely
Scheduled runs are unattended. A selected Plugin can read authorized context, but it cannot perform a write action that would normally pause for your approval. Scheduled Tasks cannot run Deep Research or artifact actions. If the task needs to send a message, update a record, change a document, or perform another approval-required action, use an attended chat instead.Reconnect older Plugin selections
Tasks created with a retired Smithery connection cannot run until you make an explicit current selection.1
Reconnect the app
Open Settings > Plugins and connect the current Plugin through the Composio authorization flow.
2
Edit the task
Open the task showing Plugin reselection required.
3
Save current access
Choose the connected Plugins it may use now—even if the correct choice is none—and save the task.
Team Scheduled Tasks
Accepted team members can view, edit, run, pause, and delete tasks in their team workspace. Editing a task changes its Runs as identity to the editor, so future runs use that member’s connected Plugins. Everyone in the team can read a run’s result. Only the member shown in Runs as can continue that generated chat. If the team plan becomes inactive, members can still pause or delete retained tasks, but new runs do not proceed until plan access is restored.Usage and failed runs
Every run checks the workspace plan and available API usage budget before generating. A run can be skipped or fail when:- The paid plan is no longer active or cannot be verified.
- The workspace API usage budget is exhausted.
- The selected Plugin needs reconnection or reselection.
- The task is already running.
- The selected model is unavailable and no replacement can be used.
Plugins
Connect apps and choose the context a task may read.
Plugin troubleshooting
Fix authorization, reconnection, and Plugin reselection issues.
API usage budget
Understand how each run uses the selected workspace’s budget.
Teams
Understand workspace membership and team-plan access.