Skip to main content
Workflows chain prompts, agents, and tools into one repeatable run. This tutorial builds one from start to finish: create it from the starter template, add a step by hand, let the workflow assistant add another, then run it and read every step’s output. The video is 2 minutes 24 seconds long. The written steps below follow the same order, with the matching timestamp for each step.

​
What you’ll build

The starter template already runs out of the box. Over the tutorial, it grows into a small content pipeline:

​
Steps

1

Create a workflow (0:07)

Open Settings → Workflows → Manage and select New workflow. You start from a working starter template, not a blank page, and the editor opens in Visual mode.
2

Read the graph (0:18)

Read the graph from the top. The Inputs node declares what a run needs; here it is a single topic. The first two steps sit side by side because they belong to separate jobs, so they run in parallel. Each result then flows down into the steps below it, which run in order.
3

Edit a step (0:28)

Select a step to open it in the inspector, where you can change its ID, title, and prompt. Double curly braces pull values into a step: {{ inputs.topic }} reads a run input, and {{ steps.idea.output }} reads an earlier step’s result. That is how steps talk to each other.
4

Add a step (0:37)

Select the + below the last step and pick a step type — Prompt, Agent, Shell, Tool, and more. Give the new Prompt step the ID tweet, the title “Write a tweet”, and this prompt:
After you rename a step ID, press Return before moving to the next field.
5

Or just ask the workflow assistant (0:57)

Instead of editing by hand, describe the change in the assistant box at the bottom of the editor:
The assistant edits the graph for you. In the video it adds a translate_ja step whose prompt reads {{ steps.tweet.output }}. Review the new step before you save — assistant edits stay unsaved until you select Save.
6

It's just YAML (1:16)

Select YAML in the toolbar to see the same workflow as source. There is one plain file per workflow, saved at ~/.enconvo/workflows/<id>.yaml, so it is easy to read, diff, and share. Select Visual to return to the graph. See the full YAML below.
7

Run it and check the output (1:28)

Select Inputs, set the run values — the video uses {"topic": "matcha"} — and choose Run. Running steps glow blue and finished steps turn green. The Agent step takes longer than the others.When the run finishes, select any step and open its Output tab to see exactly what it produced. The last step picked up the tweet and translated it, with no copy and paste.
8

Find past runs (2:05)

Every run is kept under Runs in the toolbar, so you can come back to any result later.
Running a workflow calls real models and tools. It can use provider credits, and Shell or Tool steps act with your Mac account’s permissions. Review a workflow’s steps before you run it.

​
The finished workflow

Here is the workflow built in the video, written out as YAML. The YAML view may format it slightly differently.
The ideate job waits for date and catalog through needs, so it can read their results with jobs.<job>.<step>.output. Within a job, later steps read earlier ones with steps.<id>.output.

​
Next steps

Workflows introduction

Jobs, steps, and every executor a step can use.

Creating workflows

The Visual editor, YAML, and the editing assistant in detail.

Advanced workflows

Conditions, loops, retries, output schemas, and subworkflows.

Scheduled jobs

Run an Agent instruction or script at a set time.