# Workflows. Tasks that run by themselves. ## You describe a task once and set its trigger: a time or an event. When it fires, the AI agent does the work by itself – with the same skills and connectors as in the chat. When An invoice arrives in the inbox Outlook or: Mondays, 8:00 Then The agent checks it against the purchase order and delivery note Skill: invoice check Result Approval draft with discrepancies flagged Teams · #accounting ## What someone starts by hand today will then run by itself. ### The agent already handles these tasks on request today. As scheduled tasks they start by themselves as soon as their trigger fires. Mondays, 8:00 #### Pipeline for the sales meeting Deals by stage, last week’s wins and losses, the biggest open opportunities. When an invoice comes in #### Check against purchase order and delivery note Amounts, quantities and line items checked, discrepancies flagged before anyone approves. On the first of the month #### Cost centres against budget Plan and actual per cost centre, variances flagged, before the monthly review. When a contract lands in SharePoint #### Term and notice period in view When the contract expires and until when it can still be cancelled – reported in good time before the deadline. What these tasks look like in the chat today, with real results: What the HUB can do. ## What workflows can do. ### A request in the chat becomes a task with a trigger. ### At a set time Daily, weekly, monthly or once: weekdays at 7:30 or on 31 October at 9:00. ### When something happens A new email, a new document in a SharePoint folder, a new entry in the CRM: the event starts the task. ### Run now Any task can also be started by hand, for example to test it before its first real run. ### All in one place All tasks in one list: edit, pause, resume or delete. ### History for every run Every run with trigger, time, status and result, so it stays clear what happened when. ### Runs in the HUB The task runs on the platform, not on your computer. When it’s done, you get notified. ## Running by itself doesn’t mean running without control. Scheduled tasks follow the same rules as everything else in the HUB. - A task sees only what the person who created it is allowed to see - You decide which skills and connectors it may use - Every run is logged ## What keeps getting left undone? Tell us which task should run by itself. We’ll show you how the agent already handles it today with a skill on request.