Skip to content

Create a manual Automation

Create a manual Automation to reuse starting instructions without setting up an automatic Trigger.

  1. In your project’s navigation, open Automations, then select New automation.
  2. In Name, enter a name you can recognize in a run menu.
  3. In Instructions, write the first message the new Session should receive.
  4. Under Trigger, leave None selected.
  5. Under Runtime → Model, leave Project default selected to use the project’s Session defaults.
  6. In Scope, leave This project selected.
  7. Select Create.

In Instructions, enter / to choose a Command or Skill, or @ to reference a file. See Skills and commands.

To make the Automation available in every project on this Mac, choose All projects in Scope before creating it. You cannot change a saved Automation’s Scope. Scheduled Automations must belong to This project.

The menu beside New automation offers Morning review, Implement ticket, and Triage ticket examples. Each opens a draft for you to review; it does not save or run anything. Check the instructions, referenced Skills or Commands, and any schedule’s time zone before creating it.

Project default inherits the model override in Configure → Sessions → Chat → Model. Without an override, Volli uses Settings → All projects → Models → Ticket Sessions for a ticket Run or Board chats for a project Run.

If you enable Pick models automatically for the decision model, an Automation using Project default can choose among your configured default models based on its Instructions. If no automatic choice is available, the configured default stands. See Model defaults.

To pin a different choice, select a named tier under Defaults or an exact model in Runtime → Model. A tier resolves to its current model when each Run starts. If an exact model offers multiple reasoning levels, choose one under Reasoning effort. A named tier or exact model bypasses automatic model selection.

Run history records the model and reasoning that started the Session. Changing defaults later affects future Runs, not earlier Runs’ history.

Select a saved Automation, then choose Edit beside Trigger, Instructions, or Runtime. Select Save in that section to apply its changes, or Cancel to restore its saved values. Select the Automation’s name to rename it.

Unsaved edits survive navigation. Draft saved marks unsaved work; Draft restored marks a draft reopened later. Select Discard draft to return to the saved record. For an unfinished new Automation, use Resume draft to return to it.

In the saved Automation’s More actions menu, Duplicate creates a copy. Delete… removes the Automation but keeps its past Runs and Sessions.

Write an idea in Instructions, then select Draft in chat. Volli opens a Board Session with your draft, Trigger, Runtime, and available Skill names. The agent proposes a name and instructions for you to review; this action does not save, arm, or run the Automation.

Copy the proposed instructions back into the editor and save them. Your editor draft survives the trip to chat.

To test the saved Automation, see Run an Automation and read Runs. For automatic starts, use column Automations or scheduled Automations.