Chain the steps once,run the whole routine

A workflow is up to five steps behind one shortcut: your agents, then the write that files the result. Press the key and the routine runs through to a ticket that exists.

Meeting notes to a filed ticketJ2 steps
Starts fromSelectionléa: retry fires twice on a declined cardtom: VAT line missing on EU invoicesdecision: release moves to Monday
AgentWrite the user storyAs a customer whose card is declined, I want the retry to fire once, so that I am never charged twice.Your prompt · 3 acceptance criteria
Ends withYour clipboardKH-184#checkout-squadSprint 24 notesPasted where your cursor was
One step · three tools at once
Write · JiraCheckout boardKH-184CreatedRetry fires twice on a declined card
Write · Slack#checkout-squadPosted14:09Release moves to Monday, retry fix scoped
Write · ConfluenceSprint 24 notesAppendedv12Under Decisions, nothing else touched

A step is an agent,
or a write to your tools

An agent is a prompt you saved once. A workflow carries one running text from the first step to the last: an agent shapes it, a write ships it, and what the write hands back is what the next step reads.

Your agents, in the order you put them

Up to five steps in series. Each one runs on what the step before it produced, so rough notes become decisions, then a story, then a ticket that exists. An agent you already use drops straight in as a step, with nothing to rewrite.

Or a write into the tool

The AI steps shape the text. A write step ships it, into the six tools you have connected.

A write hands back its receipt

The issue key and the link it returns become the running text, so a step placed after a write is writing about something that exists. That's how a workflow ends on a release note quoting its own ticket, or on a reply that gives the customer a number.

One step, several tools at once

A parallel step gives the same text to two, three or four destinations and writes them at the same time: the ticket in Jira, the heads-up in Slack, the note in Confluence. It counts as one step against the five, and the editor draws it as a split that rejoins, never as a nested list.

Four things a workflow can start from

One field in the editor decides what the first step runs on. Change it and the steps stay exactly as you wrote them.

Selection

The text you highlighted when you pressed the key. The default, and the one most workflows never leave.

Starts fromSelection · the text under your cursor

Capture

Launching it draws a box on screen, reads what's inside and runs the steps on that. For the things you can't select.

Starts fromCapture · a region on screen

Document

A file is the input: asked for on every run, or pinned once in the editor and used every time after that.

Starts fromDocument · ask me each run

Voice

The workflow's own shortcut becomes the microphone key. Speak, press again, and the steps run on what you said.

Starts fromVoice · ⌘⇧V

It writes only where
you sent it

A workflow is a list you wrote, run in the order you wrote it. Every destination is one you picked, and every run says what it did.

Security and privacy
Five steps at most, and no hidden sixth
The board or channel picker opens first
Cancel at the picker and nothing is spent
A write that landed is never rolled back
A failed branch never cancels the others
Every step logs into your Memory session
Sessions stay in local SQLite on your Mac
Parallel branches cost no extra credits

Three ways to build one

Draw it step by step, describe it in a sentence, or run it once from the palette and keep it if it was good.

Draw it in the editor

Pick what it starts from, drop the steps in, choose the key. The editor draws the rail as you build it.

Download for Mac
  • Drag a step to move it in the workflow
  • A fan-out is a visible split, not a nested list
  • Its own shortcut, or a row in the palette
  • macOS 13+ or Windows 10 22H2+

Or describe it once

Say the routine in plain language and Khint drafts the workflow, reusing the agents you already have.

See what an agent is
  • Reuses a matching agent instead of cloning it
  • Writes the new prompts it needs
  • Build notes list what it created and reused
  • A tool you haven't connected is flagged, not guessed

Or just type the idea

The palette's idea bar plans a one-off run from your agents and your connected tools, and shows the plan first.

See the idea bar
  • One sentence is enough
  • Planning costs no credits
  • The pickers open before anything runs
  • A good run saves as a real workflow

Common questions about AI workflows

What's a Khint workflow?

A workflow is up to 5 work steps run in series behind a single shortcut. Each step is either one of your agents (a prompt you saved once), a write to a connected tool, or a parallel step that writes to several tools at once, and each step picks up where the previous one left off: rough notes become decisions, then a formatted ticket, then a filed Jira issue. One shortcut in, one result out. Workflows have their own page in the app's sidebar, next to Agents.

Which tools can a workflow step write to?

A step can create a Jira issue or comment on one, create a Confluence page, comment on a page or append to one, create a Linear issue, create or append to a Notion page, post a Slack message, draft a Gmail email, or hand the running text to Claude. The AI steps shape the text; the write step ships it, and the issue key or page link it returns becomes the running text for the next step.

Do I have to build workflows by hand?

No. Open Generate with AI on the Workflows page and describe the routine in plain language, for example "turn my standup notes into Linear issues." Khint drafts the workflow: it reuses agents you already have when they match, authors new ones where needed, and shows build notes for what it created or reused. If a step needs an integration you haven't connected yet, it flags a Connect prompt instead of guessing. You review, tweak, and save.

What's the idea bar?

The palette opens with a "Your idea" input. Type what you want done ("summarize this and file it in Jira") and Khint plans it as a one-off workflow from your agents and connected integrations. You see the plan before anything runs: the steps, and the text it will run on. Confirm, it runs, and if the run was good Khint offers to save it as a real workflow you can run again.

What does running a workflow cost?

Only its AI steps. Each agent step bills like a single action, about one credit for a light one; the write steps cost nothing, and neither do the branches of a parallel step, because a write isn't a model call. Planning a run from the idea bar is free too. The free plan gives 300 credits a month, Lite 900, Pro 4,000 and Max 7,000, all drawn from one monthly wallet.

Where does the result land?

A workflow run from the palette pastes the final text back where your cursor was. A run planned from the idea bar or a capture lands on your clipboard instead, with the created issue key or page link when the last step is a write, ready to drop into the thread you were in. Either way, every step logs into your active Memory session, so later actions can draw on what the workflow did.

Try Khint today

Free with 300 credits a month. No credit card. macOS 13+ or Windows 10 22H2+.