Stacklink
Workflows

Workflows

Set up a process once. Stacklink runs it step by step and keeps its place.

A workflow is a set of steps that Stacklink runs for you, in order. It can use your apps, ask a Bot, wait for a person, and pick up where it stopped if something fails.

A support email comes in. AI sorts it. Bugs go to Linear, billing questions go to a Bot, and Priya approves the reply before it’s sent.
A support email comes in. AI sorts it. Bugs go to Linear, billing questions go to a Bot, and Priya approves the reply before it’s sent.

Start here

Bot or workflow?

You want…Use
Something that thinks for itself, like “review yesterday’s tickets”A Bot
The same steps every time, like “sort each email, then file it”A Workflow
Steps, plus some judgment in the middleA workflow with an Ask a Bot step

A workflow follows the steps and branching rules you define. An AI step inside it can still give a different answer each time.

It keeps its place

Stacklink saves after every step. Here, the email was already sorted when Create an issue failed, because Linear’s access had expired. You fix the cause and continue from that step. The sorting isn’t done again.

“Create an issue” failed. Finished steps stay done.
“Create an issue” failed. Finished steps stay done.

How retries and recovery work →

Embed the builder in your application

Building your own product? Your customers can build workflows inside your app with the same editor. See how →

Looking for a section from the previous guide?

Build, test and publish

Paths, parallel work and loops

Save Memory

Code and AI

Schedules and triggers

Limits and recovery

SDK guide

MCP guide

Issue embedded access

Mount the builder

Connections and sharing

Host reports and analytics

On this page