> ## Documentation Index > Fetch the complete documentation index at: https://docs.spinnable.ai/llms.txt > Use this file to discover all available pages before exploring further. # Scheduling Tasks > Set up one-time and recurring tasks for your AI workers Your AI workers don't sleep, and they don't need you to remember everything. Schedule tasks once, and they'll execute automatically—whether that's a daily standup, a weekly report, or a one-time reminder. *** ## How Scheduling Works Just tell your worker what you want done and when. They'll handle the rest. **1. Describe the task** Be specific: "Pull last week's sales data and email me a summary." **2. Specify when** "Every Monday at 9am" or "On January 15th at 3pm." **3. Confirm** Your worker sets it up and confirms the schedule. > [!NOTE] > > **Scheduled task limits apply.** The number of active scheduled tasks you can have depends on your plan. See [Plans & Pricing](/account/plans-and-pricing.md) for details. > [!TIP] > > **Check the task's time zone.** Confirm the intended time zone when you set or change a schedule so it runs when you expect. ## Who Can Schedule Tasks Workspace members who can chat with a worker can ask it to create a scheduled task or a webhook; outside contacts can't. In chat, you can list the worker's tasks and change, pause, resume, or cancel the ones you created. The worker's manager can manage any of its tasks, and the manager and co-managers can also use **Settings → Tasks**. A webhook can't be given more access than the person who created it. *** ## One-Time Tasks Schedule a task to run once at a specific future date and time. **Examples:** * "On Friday at 10am, remind me to submit the proposal" * "In 3 days, email the client to check on their decision" * "On December 1st at 2pm, send the holiday schedule to the team" ```text Good Example theme={null} You: On January 20th at 2pm, email the product roadmap to taylor.mitchell@getspinnable.ai Worker: Scheduled! On January 20th at 2:00 PM, I'll send the product roadmap to Taylor Mitchell. ``` *** ## Recurring Tasks Schedule tasks that repeat on a regular schedule—daily, weekly, monthly, or custom intervals. **Examples:** * "Every Monday at 9am, summarize last week's GitHub PRs and email me" * "Every day at 8am, check my calendar and send me a WhatsApp with my first meeting" * "On the 1st of every month, pull expense data and email a summary" ```text Good Example theme={null} You: Every Monday at 9am, summarize last week's GitHub PRs and email me. Worker: Got it! Every Monday at 9:00 AM, I'll review the previous week's GitHub pull requests and email you a summary. ``` ### Custom Frequencies You can schedule tasks on custom intervals: * "Every weekday at 5pm" * "Every other Friday at noon" * "Every 1st and 15th of the month" > [!NOTE] > > **Maximum frequency limits apply.** There's a minimum interval between task executions to prevent system overload. If you need very frequent checks, consider using external triggers instead (see Pro Tips below). *** ## Managing Scheduled Tasks ### View and edit your tasks Open your worker's **Settings → Tasks** to see scheduled tasks. Select a task to change its name, instructions, or schedule, then save your changes. The schedule is shown in that task's time zone. You can also ask your worker what tasks are scheduled or request a change in chat. ### Pause, resume, or delete a task Open the task from **Settings → Tasks** and use the **Active** switch to pause or resume it. To remove it, select **Delete** and confirm. You can also ask your worker to delete a task in chat. > [!WARNING] > > **Deleting is permanent.** If you want to stop runs without losing the task, pause it instead. *** ## What Happens When Tasks Run When a scheduled task executes: 1. Your worker performs the task 2. Sends you the output via the channel you specified 3. Logs the execution for your review All runs of a recurring task share one conversation, so your worker can see what earlier runs did. If you archive that conversation, the next run starts a new one. If a task cannot start because a tool account or other dependency is missing, it shows **Failed** rather than remaining pending. Check the task status and the notification for the reason, then reconnect the tool and retry. Scheduled skills with a missing or disconnected integration also send an email alert to the worker's manager; see [Managing Skills](/concepts/skills.md#managing-skills). *** ## Pro Tips > [!TIP] > > **Test complex tasks before scheduling.** For tasks that involve multiple steps or tools, follow this workflow: > > 1. **Describe what you want:** "I want you to check my sales inbox, pull emails from last week, categorize them by priority, and send me a summary" > 2. **Ask the worker to do it once:** "Try that now and send me the result" > 3. **Review the output:** Make sure it's exactly what you want > 4. **Then schedule it:** "Perfect! Schedule that to run every Monday at 9am" > > This prevents wasting scheduled task executions on tasks that need refinement. > [!TIP] > > **Use external triggers instead of frequent checks.** Don't schedule a worker to "check Gmail every hour for new messages." Instead, set up an email notification that forwards to your worker—this triggers action immediately and saves Work Credits. Scheduled tasks should be for time-based work, not monitoring. > > Examples: > > * ❌ Bad: "Check the CRM every 2 hours for new leads" > * ✅ Good: Set up a CRM notification that emails your worker when a new lead arrives > [!TIP] > > **Scope each run, not just the schedule.** Recurring tasks are a major source of > Work Credit usage for many workspaces, and how much work a task does on each run matters more than > how often it runs. Name the specific sources, set a boundary, say what to skip, and give an > explicit stop condition — including what to do when there is nothing to do. > > See [Getting More From Your Work Credits](/guides/getting-more-from-your-work-credits.md) for how to > audit your recurring tasks and cut what they use. *** ## Best Practices > **Specify the delivery channel** > > "Email me the report" vs. "Send via WhatsApp"—workers need to know where to deliver the output. > **Grant tool access upfront** > > If a task pulls data from Gmail, Notion, or GitHub, ensure the worker has access to those tools before scheduling. > **Start with one-time tasks to test** > > Before creating a recurring task, test it once: "Send me the report tomorrow at 9am" → review → "Make this recurring every Monday." *** ## Next Steps > **[Training & Feedback](/guides/training-feedback.md)** > > Refine scheduled task outputs with feedback > **[Connecting Tools](/guides/connecting-tools.md)** > > Ensure workers have the tools they need *** **Questions?** Reach out to [support@getspinnable.ai](mailto:support@getspinnable.ai) — we're here to help! This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.