> ## Documentation Index > Fetch the complete documentation index at: https://docs.vybe.build/llms.txt > Use this file to discover all available pages before exploring further. # Automations overview > How AI coworkers run on a schedule, react to events, and follow up without being messaged AI coworkers don't only answer when someone messages them. They can do recurring work on a schedule, react when something happens in a connected tool, and come back later to check on work they started. Use automations for daily briefings, weekly reports, inbox triage, and anything you'd otherwise have to remember to ask for. ## Three ways a coworker works on its own | | What starts it | How you set it up | Example | | - | - | - | - | | [Scheduled tasks](https://docs.vybe.build/automations/scheduled-tasks.md) | A repeating schedule, like every weekday at 9am | Ask the coworker in Slack or in its **Chats** | A Monday pipeline summary posted in #sales | | [Triggers](https://docs.vybe.build/automations/triggers.md) | An event in Slack, LinkedIn, WhatsApp, or another connected tool | **Add trigger** on the coworker's page, or ask the coworker | Triage every new message in #support | | Delayed runs | A one-off moment the coworker picks itself | The coworker schedules these on its own | Check back once a long export finishes | ## Where automations live Automations belong to a single coworker. Open the coworker and go to its **Automations** section. It has two tabs: * **Scheduled tasks**: the coworker's recurring tasks, with its **Delayed runs** listed underneath. * **Triggers**: the events the coworker listens for, with **Add trigger**. Each tab has a **View activity** button. It opens **Usage & Activity → Activity**, filtered to the runs from that tab. ## Scheduled tasks A scheduled task is a saved instruction that the coworker runs on a repeating schedule, in the timezone you choose. You create one by asking the coworker. For example: > Every weekday at 8:30am, DM me a briefing: my meetings today, emails that need a reply, and tickets assigned to me. For a new report, the coworker first shows you a preview built from real data, then schedules it once you agree. See [Scheduled tasks](https://docs.vybe.build/automations/scheduled-tasks.md). ## Triggers A trigger runs the coworker with a prompt whenever a specific event arrives. Examples are a new message in a Slack channel, a new LinkedIn or WhatsApp message, or a new email, form response, or payment in a connected app. You can add an **Only run when…** condition so the coworker acts only on the events that matter. See [Triggers](https://docs.vybe.build/automations/triggers.md). ## Delayed runs and follow-ups Coworkers also schedule one-off runs for themselves: * **Checks.** When a coworker starts something that finishes on its own, like a coding session or a large export, it can schedule a check to come back to it. In chat, this shows as **Scheduled a check**. A check can be set from 1 minute to 7 days ahead. * **Follow-ups.** After a conversation, Vybe may schedule a follow-up when something is still open. That could be an answer or decision you still owe, work the coworker promised, or an event coming up or just finished. A follow-up comes back to the same conversation and can be up to 12 weeks away. If you write in that conversation before then, the pending follow-up is cancelled. Pending runs appear under **Automations → Scheduled tasks → Delayed runs**, where you can **Run now** or **Cancel** them. In Slack, follow-up reminders have **Already done**, **Not relevant anymore**, and **Remind me in…** buttons. ## Credits and limits Every automated run uses credits, just like a message in chat. A task that runs every few minutes adds up quickly, so pick the least frequent schedule that's still useful. See [Plans and credits](https://docs.vybe.build/getting-started/plans-and-credits.md). Before each scheduled, trigger, or delayed run starts, Vybe checks three things. If any check fails, the run is **Skipped** and never starts: | Check | Reason shown on the skipped run | | - | - | | The coworker is active (not archived) | "Agent is not active" | | Your organization has credits left | "No credits left" | | The coworker hasn't reached its monthly usage limit | "This agent has reached its monthly usage limit. Raise the monthly limit or wait until the next reset before running it again." | The monthly usage limit is set per coworker under **Usage & Activity → Usage → Monthly usage limit**. It's a hard cap: once it's reached, chat, Slack, scheduled tasks, and trigger runs stop until next month or until you raise the limit. See [Usage and activity](https://docs.vybe.build/coworkers/usage-and-activity.md). Archiving a coworker also stops its scheduled tasks and pauses its integration triggers. ## See what ran Every automated run is recorded in the coworker's **Usage & Activity → Activity** tab. * Set the channel filter to **Scheduled** for scheduled tasks or **Trigger** for triggers. * Set the status filter to **Skipped** to find runs that were blocked, with their reason. * Open a run to see its **Input**, its **Response**, and every step the coworker took. Each task and trigger card also lists its own recent runs. ## Example automations Scheduled tasks: > Every Friday at 4pm, post a summary of this week's closed deals from HubSpot in #sales. > On the first of every month, compare last month's signups with the month before and email me the three biggest changes. Triggers: > When someone posts in #support, check whether it's a bug report. If it is, open a Linear issue and reply in the thread with the link. > When a new form response arrives, add the lead to our CRM and DM me a one-line summary. Delayed runs: > Kick off the CRM export and tell me when the file is ready. > [!TIP] > > Say where results should go: a Slack channel, your DMs, or an email address. To post in a Slack channel, the coworker needs **Read and write** access to it. See [Slack](https://docs.vybe.build/channels/slack.md). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.