Documentation

Learn how to set up and get the most out of Viktor.

Scheduled Tasks

Have Viktor run recurring work on a schedule, and create, edit, pause, run or delete those tasks from chat or the Tasks page.

Anything Viktor can do once, he can do on a schedule: a metrics brief every weekday morning, a pipeline report every Monday, an invoice reconciliation on the first of the month. You can set a task up by asking Viktor in chat or by filling in a form on the Tasks page in the web app.

For a one-time reminder or follow-up, use a reminder instead. For work that should start when something happens in another tool, use an event trigger.

How scheduled tasks work

  • A task has a title, instructions, a schedule and, for AI tasks, a model.
  • Most tasks run a full AI agent on each run, following the instructions you gave. Viktor can also set up a script task, which runs a Python script directly. The task page shows script tasks as Script with the note "Runs Python directly · zero credits".
  • A schedule can run at most once every 5 minutes. A faster schedule is rejected with "Schedule must run at most once every 5 minutes."
  • Viktor reads times in your own time zone unless you name another one, and confirms the schedule in your local time.

Set up a task in chat

  1. Message Viktor in Slack, Microsoft Teams or the Viktor web app chat, and describe the work and the timing. For example: "Every weekday at 9 AM, post yesterday's revenue summary in #finance."
  2. Say where the results should go. If you ask from a DM or a private chat, the output stays private to you unless you ask for a shared channel.
  3. Viktor usually test-runs a new task once before it goes live. During the test, chat messages are captured instead of posted and permanent writes to your integrations are blocked, so you see a sample without side effects.
  4. Confirm the schedule when Viktor plays it back.

A few options you can ask for:

  • Model. Viktor defaults to smart. You can ask for balanced for lower-cost routine work, or cheap for runs that write nothing people read.
  • Personal task. Ask Viktor to make an AI task personal. It then shows only to you, under My tasks.
  • Sender name (Slack only). In Slack a task can post under a custom sender name. In Microsoft Teams, messages always come from the Viktor bot.
  • Run only when needed. Viktor can add a condition script that runs before each scheduled run and skips the run when there is nothing to do, or a pre-run script that gathers data for the agent. Viktor warns you when an AI task would run more than about six times a day, because each run costs credits.

If you create a task from the web app chat and no Slack or Teams workspace is connected, the run does not reply in that chat. Each run's report is on the task's page under Runs, and anything the instructions say to send (email, documents, connected tools) is delivered there.

Set up a task in the web app

  1. Open Tasks and select New task.
  2. Pick a template (see automation templates), or select Create manually.
  3. Fill in Title, Description and Schedule. If your description mentions timing, the schedule may be filled in for you and marked Set from your description.
  4. Choose a Model, or leave it on Team default.
  5. Select Create task. You see a "Task created" confirmation.

Change a task

  • In chat: ask Viktor, for example "move the daily brief to 8 AM". Viktor re-creates the task at the same place, which replaces its old settings.
  • In the web app: open the task from Tasks, select Edit, and change the title, description, schedule or model. Script tasks have no model to change.

Only a workspace admin, or the person who created the task or the person it runs for, can edit a team task. A personal task can be edited only by the person it belongs to, not even by an admin. Others get an error when they save.

In Slack, when a teammate edits the description or schedule of your task in the web app, you get a DM: "Your scheduled task was updated" (with the old and new descriptions attached) or "Your scheduled task's schedule was updated" (with the old and new schedule).

Pause, resume, run now or delete

On the task's page:

  • Open the ⋯ menu and select Pause or Resume. A paused task shows "This task is paused and won't run on its schedule." It keeps its settings, and when you resume it, it continues from its next scheduled time. Pausing has no end date: a paused task stays paused until someone resumes it.
  • Select Run now to run the task ahead of schedule. You see "Run started." and the result is delivered when the run finishes. The button shows only on tasks stored under your own account, such as tasks you created in the web app. Tasks set up in Slack or Teams may be stored under the account that connected the workspace, so the button may not show for you. If you don't see it, ask Viktor in chat to run the task now.
  • Open the ⋯ menu and select Delete task, then confirm. Deleting removes the task and its schedule and cannot be undone.

You can also ask Viktor in chat to pause, resume, run or delete a task.

See your tasks and their runs

The Tasks page lists scheduled tasks under All tasks, My tasks and System tasks, with filters for status, model and author. Use Calendar to see tasks on a day, week or month view, and List to go back.

Each task's page shows whether it is Active or Paused, its schedule, its model (or Script), who created it, and whether it is Personal, Team or System. The Instructions tab shows what the task does. The Runs tab lists past runs; select one to read what happened. A run's transcript opens only for the task's creator.

Workspace admins can see how many credits each task used in Usage → Tasks. The table can be sorted by total credits, total runs and last activity, and filtered by user. Each row's menu has Open full details and Pause or Resume. Delete and edit tasks from the Tasks page, not from Usage.

Limits by plan and permission

  • Each AI run uses credits; script tasks use none.
  • Runs, including Run now, are blocked when the workspace is out of credits or the task creator's personal spend cap is reached. Run now then shows "Out of credits — can't run this task right now."
  • Personal tasks are visible only to the person they belong to, and only that person can edit, pause, resume or delete them. Workspace admins can't either.
  • Any member of the workspace can pause, resume or delete a team task.
  • Editing a team task needs a workspace admin or the task's creator or the person it runs for.
  • System tasks, which Viktor installs himself (such as his proactive check-ins), cannot be edited or deleted. They can be paused and resumed.
  • The Usage page is for workspace admins only.

Common problems

  • "Schedule must run at most once every 5 minutes." Pick a slower schedule. For reactions faster than that, use an event trigger.
  • A task can't be resumed. Resume is refused when an integration the task needs has to be reconnected. Reconnect the integration, then resume.
  • "Out of credits — can't run this task right now." Add credits or change plan: see running out of credits.
  • You can't find a task on the Tasks page. Check All tasks rather than My tasks. Someone else's personal task is not shown to you.
  • Edit fails with an error. You are not an admin and did not create the task. Ask its creator or an admin.
  • A run posted in the wrong place, or did the wrong thing. Tell Viktor in the task's thread or a DM what went wrong. He can trace the run and fix the instructions.

Related

Get Started for Free