labb
Features / Studio workflows

From one paragraph to a checked workflow

Describe a job in plain words. labb draws the steps, you run them on a real example, and you can open every step to see exactly what went in and what came out.

The job in this walkthrough Ben has too many meetings. Each recording needs writing down, with the decisions and action items pulled out, and Ben wants to check the notes before they're saved.
Step 1 of 8

Describe it

Open Studio in the sidebar and press New workflow. Say what starts it, what it looks at and where the result goes, then press Draft it. Nothing is saved until you choose to create it.

The New workflow form with Ben's description of the meeting notes workflow typed in, a Draft it button, and templates to start from instead.
Step 2 of 8

Answer what wasn't clear

If the description leaves open something that changes the design, the model asks up to three questions, with answers to pick. Choose one, type your own, or press Skip and let it decide.

Two questions: how the recording reaches the workflow, and where the checked notes should go.
Step 3 of 8

Read the blueprint, then change it in words

The blueprint lists every step in plain words beside a preview. What it needs tells you if anything is missing or not set up.

Want something different? Ask for it. Ben types "List each action item with who does it and by when." That makes a new version with only the changed steps marked, and you can go back to v1 at any time.

When it looks right, press Create. The workflow opens as a draft and won't run on its own. Try it is also here if you'd like one run before saving.

The Meeting notes blueprint at version 2: nine steps listed, one marked Changed in v2, a preview of the flow, and a note that everything it needs is set up.
Step 4 of 8

See it on the canvas

The builder shows the same workflow as connected steps: the if/else splits into a path for meetings with action items and a path for those without, and they meet again at the result. You can drag in more steps, edit any of them, or keep changing it through Ask labb underneath.

The builder: Meeting notes on a canvas with its if/else branch, a settings panel on the right and an Ask labb box underneath.
Step 5 of 8

Test run on a real recording

Press Test run. The Start step's inputs become a form, so Ben pastes in a link to the recording of this week's launch check-in with Emma and Liam.

A test run uses the draft, and its steps really happen. The canvas lights up as it goes.

The Test the draft form with a link in the Link to the recording box.
The canvas mid-run: finished steps outlined in green, Write the notes running, the summary path marked skipped.
The run in progress. The meeting had action items, so the short summary step is skipped.
Step 6 of 8

Approve it, or don't

The run stops at the approval step and shows the notes. It keeps waiting until you answer, even if the server restarts in between.

Add a note if you like, then press Approve or Reject. Each answer can lead somewhere different. You can also answer from Waiting for you on Studio's page, or from the terminal.

The run panel, status Waiting, with the drafted notes and Approve and Reject buttons.
Step 7 of 8

Check every step

The finished run lists each step with its status and time. Click one to open what went in and what came out, so when an answer looks wrong you can see where it went wrong.

The Find decisions and actions step opened: its output has a title, the decisions, the action items and has_actions set to yes.
Output: the step answered in fields, and the if/else reads {{extract.has_actions}}.
The Write it down step opened: the link it received as input, and the transcript it produced as output.
Input and output: the link that went in and the transcript that came out, so you can check what was actually heard.
  • Run again from this step repeats a run from any step, reusing the results before it.
  • Fix it appears when a run fails. labb reads what failed and suggests a change for you to preview.
  • Runs keeps the workflow's history, which you can filter to the failed or waiting ones.
The canvas after a second run: the summary path in green, the notes path skipped.
A second test with a short status call has no action items, so it takes the other path. It needs no approval, and the run goes straight through to the result.
Step 8 of 8

Publish it

Press Publish when both paths behave. Workflows can then run on their own, or from a webhook your meeting tool calls. The draft becomes v1, and you can keep editing without touching it. Earlier versions are kept, and each run says which version it used.

The builder after publishing: a Published v1 message, a Run button, and two finished runs in the Runs tab.
By handPress Run and fill in the form.
On a scheduleSet the times on the Start step.
From a webhookA secret URL fills the inputs from JSON.
On an eventFor example, when a document is added.
From the terminallabb run runs it and prints the result.
More features

Try it on your own server

Get labb

Ben, Emma and Liam are made up, and the transcript and the model's text in these screenshots were scripted. The screens, the checks on the blueprint and the runs themselves come from labb.