Build your first workflow

You’ll build Ticket intake. It receives a ticket ID and gives it back: input {"ticketId":"ticket-42"}, result "ticket-42". It needs no apps, so you can finish it in a few minutes. Then you’ll grow it into support email triage.

You need permission to edit workflows in the project. Publishing needs publishing permission.

Open Workflows → New workflow

Describe with AIBuild manually

Paste this, then choose Draft workflow:

Create “Ticket intake”. Accept a required string input named ticketId.
Connect Start to Return a result, returning the ticketId input.
No apps, AI steps, code, schedule or other trigger.
Keep it as a draft for me to review.

Check the steps it proposes, then choose Keep in draft. If it’s not right, choose Discard and describe it again.

1. Choose Build manually, open the blank canvas, and name it Ticket intake.
2. Click Starts when. Under Input, add a field called ticketId with the type string.
3. Choose Add step → Return a result, and connect Starts when to it.
4. In Return, choose The workflow’s input › ticketId.

Building manually makes no AI request.

Check the two steps

Click each step to see its settings.

Test it

Open Test and leave Live test off. Enter this input, then choose Run simulation:

{ "ticketId": "ticket-42" }

You should see both steps marked Done. The workflow returns:

"ticket-42"

Publish

Choose Publish. The label changes to Live.

Publishing doesn’t start a run. Start it from your code, your AI app, or a trigger. Later edits go through Review changes → Publish changes.

Grow it into support email triage

Now describe a real process. This one uses Gmail, Linear, Slack, a published Bot and an approver, so connect those apps first.

When a support email arrives, sort it into bug, billing or other.
File bugs in Linear and post them in #support. Ask Billing assistant
to draft billing replies, and let Priya approve them before they are sent.
Post everything else in #support and label it General.

Then:

1. Review the draft and choose Keep in draft.
2. Finish each app step: App → Action → Account. Steps and data →
3. Test it. A simulation needs a sample answer for each step that would reach outside Stacklink (here, eight). Add them under Samples, or run a Live test once your apps are connected. Test and publish →