Skip to main content
Workflows are Markdown files describing a series of steps for Sixth to follow, such as releasing a version, opening a PR or setting up a new service. Save one once, then run it any time with /filename.
These are slash-command workflows stored as files in your project. They’re different from Workflow integrations, which connect Sixth to apps like Gmail, Calendar and Slack.

​
Creating a workflow

  1. Click the scales icon in the message box toolbar and open the Workflows tab.
  2. Under Workspace Workflows (this project) or Global Workflows (every project), click New workflow file…, type a name and press Enter.
  3. The file opens in the editor. Write the steps Sixth should take.
Or create the files yourself: Files can be .md, .txt or have no extension.

​
Running a workflow

Type / and pick the workflow from the workflows section of the menu, or type its full file name, for example /release.md. Anything you type after the command is passed along with it:
Each workflow has an on/off switch in the Workflows tab; turned-off workflows don’t appear in the menu. If a workspace workflow and a global workflow have the same name, the workspace one is used.

​
Writing good workflows

A workflow can use anything Sixth can do:
  • its built-in tools (reading and searching files, editing, ask_followup_question, new_task, …),
  • command-line tools you have installed, like gh, docker or npm,
  • MCP servers and workflow integrations.
Number the steps, say what to check before moving on, and say when to stop and ask you.
release.md
For instructions Sixth should be able to pick up on its own, without you typing a command, write a skill instead.