> ## Documentation Index > Fetch the complete documentation index at: https://docs.b-bot.space/llms.txt > Use this file to discover all available pages before exploring further. # Tasks > Schedule, trigger, inspect, and manage Agent automation # Tasks Tasks run instructions with the selected Agent on a schedule, from a webhook, or through polling. Select an Agent in the Hub header before creating or viewing its tasks. Task operations and Proactive mode in B-Bot Hub ## List and calendar views Use **List** to manage tasks and **Calendar** to inspect scheduled runs by date. The list shows each task's name, instructions, trigger, next run, and active or inactive status. A **Proactive** badge identifies the system task used by Proactive mode. Filter the list by: * all, active, or inactive status * all, scheduled, or webhook trigger Refresh reloads task data. The calendar uses the same filtered set. ## Create a task Select **New task**, then provide: 1. A name and clear instructions. 2. The assistant associated with the selected Agent. 3. A priority: low, medium, high, or urgent. 4. Optional comma-separated tags and a due date. 5. One trigger type. ### Schedule Choose once, hourly, daily, weekly, monthly, or a custom cron expression. The schedule builder exposes the relevant time, day, or minute fields and shows a summary. ### Webhook The Hub creates a webhook URL after the task is saved. An external system can call that URL to trigger the task. ### Polling Polling checks a source at a configured interval: * **HTTP** calls a URL with GET, POST, or PUT and includes a test action. * **MCP** selects a tool from a connected MCP app and passes JSON arguments. * **Composio** selects an action from a connected app and passes JSON arguments. Only connected apps available to the Agent are selectable. Testing a source confirms the request; it does not guarantee that every later run will succeed. ## Manage tasks From the list, you can: * open task details * open the task workspace * edit a user-created task * pause or resume it * delete it * use **Run now** for a webhook task Keep a new task inactive until you have reviewed its instructions and trigger. Activate it only when both are correct. Task details include the job ID, trigger, next and last run, run count, assistant, priority, tags, due date, readiness, related thread count, and webhook URL when applicable. ## Task workspace Each task has a workspace drawer with three tabs: * **To-dos** lets you add, complete, and remove planning items. * **Files** lets you add small text files, download them, or remove them. * **Generated files** shows files from the latest related run and links to its conversation. The manually managed to-dos and files are separate from the Agent's live task state in Chat. Generated files depend on a related run producing workspace files. ## Operations console and autonomy The operations console summarizes items needing attention, active tasks, total runs, and recent activity for the selected Agent. **Proactive mode** manages a system task on a six-hour heartbeat. When enabled, the console can show: * the next heartbeat * readiness score and missing context * a question you can answer to improve readiness * **Run now** * **Reset autonomy** * the autonomy timeline Resetting autonomy starts the next proactive run fresh. Proactive mode controls recurring Agent work; it does not promise successful completion or delivery to email, chat channels, databases, or other output systems. ## Where results appear Runs can create related conversation threads and workspace files. Inspect them through task details, **Generated files**, or **Open conversation**. Webhooks and polling are input triggers in this interface, not guaranteed output channels. For the Chat workspace panels, see [DeepAgents Workspace](/essentials/deepagents-workspace).