Agno Workflow Builder

The Agno Workflow Builder is a second, newer workflow builder. It builds agent pipelines: a chain of steps, most of which are an LLM agent with a model, some instructions and a set of tools. Workflows are saved to the database, run from the panel, and can be put on a cron schedule.

It is unrelated to Jarvis. The two do not share workflows, storage, step types, or the saved-workflow list.

Which builder do I want?

	Agno Workflow Builder	Jarvis
Where	Panel, inside a space	Full page at /workflows
Built around	Agent steps with tools	Nodes that drive Mantis panels
Mantis access	Through the Mantis MCP tool source on an agent	Through dedicated Mantis Control nodes
External calls	HTTP Request step, Composio and custom MCP servers	Custom Python node
Scheduling	Per workflow, from the Workflows tab	Per workflow, from the Workflow menu
Triggers	Cron and manual run	Cron, manual run, and a webhook endpoint

Reach for Agno when the work is “run these agents in order, with these tools”. Reach for Jarvis when the work is “open this panel, make that bag, run this notebook”.

Where to find it

View > Agents > Agno Workflow Builder.

The panel has two tabs, builder and workflows.

The builder tab

Three columns under a toolbar:

• Steps on the left: the palette.
• The canvas in the middle. With nothing on it, it reads “No steps yet / Drag steps from the left panel”.
• Configure on the right, which fills in when a step is selected.

Toolbar

The workflow’s name is an editable field on the left. On the right:

• Open: a dropdown listing your saved workflows with their last-updated time, plus New workflow, a refresh button, and Load more when there are more pages.
• Save: saves the workflow, briefly showing “Saved”.
• A trash button, shown once the workflow has been saved.
• An Input… box, whose value is passed into the run. Press Enter to run.
• Run, which becomes Stop while a run is in progress.

While a workflow is running, a strip below the toolbar streams tokens live, then shows the final result or the error.

Running always saves first, so Run on a new workflow creates it.

Steps

Drag a step from the palette onto the canvas.

Step	What it does
Agent Step	Run a single AI agent
Parallel	Run steps concurrently
Loop	Repeat until a condition is met
Condition	Branch on a condition
Input Map	Route a field from any step into the next one
For Each	Run an agent once per item in a list
Sub-Workflow	Run another saved workflow
HTTP Request	Call an external HTTPS API

Parallel, Loop and Condition are containers; the rest are leaves.

Configuring a step

Select a step to fill the Configure column. Every step has a Name. Beyond that the fields depend on the kind.

Agent Step and For Each

• Agent Config: Agent Name, Model (defaults to gpt-4o-mini), and Instructions.
• Tools: three sources, each independently switchable, and each with a searchable checklist so you can include only the tools you want:
  • Composio: third-party integrations such as GitHub and Gmail.
  • Mantis MCP: access to your active Mantis space. This is how an Agno agent reads and drives Mantis.
  • Custom MCP Servers: add any number of HTTPS MCP endpoints by URL.

For Each additionally takes a Source Step, a List Field to iterate over (leave it empty if the step’s output is already a list), and an execution setting.

Loop, Condition, Sub-Workflow

Loop takes Max Iterations. Condition builds a rule list with an expression preview under it. Sub-Workflow gives you a searchable picker over your saved workflows.

Input Map

Source Step (empty means the previous step) and Field (empty passes the whole output through).

HTTP Request

Method, URL, an optional raw body, a timeout in seconds, and toggles including Follow redirects. The URL must be HTTPS and supports placeholders: {{input}}, {{previous_step_content}} and {{steps.name.content.field}}.

Pin Output

Leaf steps get a Pin Output control. Run the workflow once, then pin a step to reuse the output it produced instead of re-running it. The pinned value is shown in an amber block; unpin to let the step run normally again. This is for iterating on the back half of a workflow without paying for the front half every time.

Delete step sits at the bottom of the Configure column.

Building and running

1. Drag an Agent Step onto the canvas.
2. Configure it. Give the agent a name, a model, and instructions. Switch on Mantis MCP if it needs to see your space.
3. Add and connect further steps for the rest of the pipeline.
4. Type into the Input box if the first step expects something.
5. Click Run. The workflow saves, then output streams into the strip under the toolbar.

The workflows tab

A card grid of your saved Agno workflows. Each card shows the description, a schedule badge when one is set, and when it last ran. Card buttons:

• Run now.
• Schedule.
• Edit in Builder, which loads the workflow into the builder tab.
• Delete, which asks for confirmation first.

Scheduling

The schedule modal is titled Schedule Workflow:

• Enable schedule: “Automatically run this workflow on a cron schedule”.
• Cron expression: free text, with presets for every minute, every hour, daily at 9:00, every Monday, and the 1st of the month. The format hint reads minute hour day month weekday.
• Space state: which space state the run should use for its Mantis MCP tools. If no space states have loaded, the modal says so. Leave it as “— None —” for a workflow that does not touch Mantis.
• Default run input: optional text sent to the workflow on each scheduled run.

Limits

• No webhook trigger. Scheduled and manual runs only.
• No execution history panel; the Workflows tab shows only when a workflow last ran.
• Stopping a run closes the panel’s connection to it and returns the UI to idle. It does not confirm that the backend stopped.
• Pins are saved with the workflow, so a pinned step stays pinned the next time you load it. Unpin before a real run.

Read nextJarvis workflow builderThe node-graph builder that drives Mantis panels directly.