# Automations

> Create recurring workflows in plain-language chat and track schedules, reviews and results.

Canonical: https://www.vuti.io/docs/autopilot
Last verified: 2026-09-10
Open in Vuti: https://www.app.vuti.io/automations

# Automations

Automations are repeatable social-media workflows. Vuti prepares work on a schedule while
keeping outputs, activity, failures, and approval controls visible.

[Open Automations](https://www.app.vuti.io/automations)

## Available templates

- **Weekly content planner:** prepares a channel-aware content plan in the saved brand
  voice and sends drafts to Review.
- **Publishing health monitor:** checks scheduled posts, publishing failures, and account
  health, then surfaces safe retry or reconnect actions.
- **Competitor watch:** monitors saved names, profiles, or URLs and turns useful patterns
  into original, research-backed drafts with source rationale.

## Create an automation in chat

Open [Vuti](https://www.app.vuti.io/vuti) and describe what should repeat:

- “Every Monday morning, prepare next week's social posts.”
- “Check my publishing health every weekday at 9.”
- “Prepare a performance presentation on the first of each month.”
- “Watch these competitors every Tuesday and prepare three original drafts: [names or URLs].”

Vuti proposes a name, workflow, schedule, timezone, first run and output destination.
It uses your workspace settings and asks for missing details that affect the outcome.
Review the summary, then choose **Create automation** or reply “yes”. You can change
it first with a reply such as “Make that Friday at 3 pm”. A changed review replaces the
previous one; nothing starts until you confirm the current review.

Generated posts still go to Review. For the daily ad factory, the review shows the
number and length of videos, the automatic H3 Max rendering authorization and the
per-run frame/video credit limit. Planning and QA use additional AI credits.

Chat supports the existing templates and their schedules. It does not create arbitrary
scripts or event triggers. The weekly planner uses the saved brand voice and connected
channels; custom per-automation prompts, exact post counts and channel overrides are
not supported for that template.

## Manage automations

Ask “What automations do I have?”, “Pause my weekly planner”, “Move the competitor
check to Tuesdays” or “Run my publishing health monitor now”. Vuti shows a review
before a change, deletion or manual run. A queued run is still pending; check Activity
for its completed result.

[Automations](https://www.app.vuti.io/automations) keeps your schedules, next runs,
results and attention items visible. **Create with Vuti** opens conversational setup.
Use **Use a form** if you prefer the template and schedule controls.

Owners and admins can edit a schedule, pause or resume it, run it now, or delete it.
Deleting an automation stops future runs but keeps existing drafts and run history.

## Approval-first guardrails

Automations speed up operations; they do not remove review. Generated content goes to the
review queue, and publishing-health work exposes problems instead of making risky changes
silently.

The **Mine** view shows the next run and last result for each automation. Open an automation's
detail view to keep schedule controls, saved configuration, recent runs, operation-level status,
and output context together. **Activity** keeps recent scheduled and manual runs with their
status and output. Empty operation groups stay collapsed so the page leads with work that needs
attention. Publishing failures and draft approvals also appear in the attention views so the
automation never becomes an invisible background process.

## Memory and outcomes

Weekly Planner uses active Vuti memory when creating drafts. Workspace memories can guide
general rules, while channel memories can guide platform-specific behavior such as thread
length or preferred formats. Recent performance guidance and outcome memories can shape
topics, hooks, and timing, but they do not override current instructions or verified
workspace facts.

Automation run details record which memory ids were used for a plan. See
[Memory](https://www.vuti.io/docs/memory) for scope boundaries and how this differs from external-assistant
memory.

## Chat and the Automations page

Use [Vuti](https://www.app.vuti.io/vuti) to create and change recurring workflows in
plain language. Use Automations to inspect their schedules, outputs and run history.