Ticket workflows: visual automations over your tickets

Ticket workflows are automations you build as a graph: a trigger, a few steps, and the actions Starko should take. They run on ticket events, on a schedule, when a Slack channel gets a message, or by hand. Open them under Settings → Ticket workflows.

ticket workflows

The list

Each workflow shows its trigger type, when it last ran and whether it succeeded, and a toggle to switch it on or off. Secrets stores API keys and tokens that workflow steps can use without putting them in the graph.

Triggers

Event: a ticket is created, changes status, gets a tag, is assigned, or a comment arrives. Filters limit which tickets qualify.

Schedule: every hour, every day at a time, or a cron expression.

Slack message: a message in a channel you choose starts the run, with the message as input.

Manual: run from the list or from a ticket, optionally with inputs you type.

Chat: Starko AI can run a workflow for you from ⌘L, Slack or an MCP tool when you ask.

Steps

Open a workflow to edit the graph. Drag steps from the palette and connect them:

ticket workflow editor

AI: summarise, classify, draft a reply, extract fields, or decide a branch with a prompt.

Ticket: create, update, comment, assign, tag, link, set the project or move status.

Customer: reply through the ticket's channel, or send an email.

HTTP: call any API with headers and a body; use a secret for the key.

Code: run a short script in a sandbox when you need logic the other steps do not cover.

Condition and loop: branch on a value or repeat over a list.

Wait: pause for a time or until a ticket changes.

Notify: post to Slack or notify a teammate.

Each step's output is available to the following steps, so an AI classification can decide the tag and the assignee in the next steps.

Testing and runs

Run now executes the workflow against a ticket you pick and shows each step's input and output. Past runs are listed per workflow with their status, so a failed HTTP call is easy to find.

Active window

A workflow can be set to run only until a date, for example "until tomorrow, then stop". Ask Starko in chat to switch a workflow on or off for a period and it sets this for you.

Examples that teams start with

New ticket tagged billing → AI summary as an internal comment → assign to the finance team.

Every two hours → fetch production errors from your host → open one ticket per new error.

New client in the CRM → create a sales lead ticket with the enrichment data.

Slack message in #bugs → create a ticket with the message and the poster as the reporter.

Did this answer your question?