Skip to main content
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

​
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.

​
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.

​
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. Before each scheduled, trigger, or delayed run starts, Vybe checks three things. If any check fails, the run is Skipped and never starts: 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. 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.
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.