# Workflow Node Types

**URL:** <https://community.solace.com/t/workflow-node-types/4951>\
**Category:** Solace Agent Mesh\
**Created:** [November 11, 2026, 1:48pm UTC](https://community.solace.com/t/workflow-node-types/4951 "2026-11-11T13:48:20Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tamimi](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/tamimi/32/2190_2.png) [@Tamimi](https://community.solace.com/u/Tamimi)\
**Post date:** [November 11, 2026, 1:48pm UTC](https://community.solace.com/t/workflow-node-types/4951/1 "2026-11-11T13:48:20Z")

</div>

Agents are great at open-ended work. When a process has to run the same way every time, I reach for a workflow: a graph of typed nodes that Solace Agent Mesh runs in dependency order. There are several node types in workflows.

| Node | What it does |
| --- | --- |
| `agent` | Sends a structured request to an agent and captures the response |
| `tool` | Calls one tool directly, no LLM involved |
| `switch` | Picks one downstream node based on a condition |
| `map` | Fans a node out over a list of items |
| `loop` | Repeats a node until a condition is false |
| `workflow` | Runs another workflow as a step |
| `decision` | Asks a decision model typed questions and routes on the answer (Early Access) |

Parallelism comes from `depends_on`: nodes that don’t depend on each other run at the same time, and a node that depends on several waits for all of them.

Here is a shipment exception triage workflow. One agent classifies the exception, a `switch` routes it to one of four recovery agents, two other agents run in parallel, and everything joins back up for the report:

 ![Shipment Exception Triage with a switch node and parallel branches](https://canada1.discourse-cdn.com/solace/original/2X/0/09a23be376432a2a553928c737eee60a609fdde3.jpeg)

And here is a peak season plan using `map` (one planning step per warehouse) and `loop` (refine until coverage hits 95%, at most three times):

 ![Peak Season Capacity Plan with map and loop nodes](https://canada1.discourse-cdn.com/solace/original/2X/c/cbc2093372980aa479affa2779c3454877f5a954.jpeg)

The YAML for those two nodes is short:

```yaml
- id: plan_sites
  type: map
  depends_on: [forecast_volume]
  items: "{{forecast_volume.output.sites}}"
  node: plan_site

- id: refine_network_plan
  type: loop
  depends_on: [plan_sites, market_scan]
  node: review_plan
  condition: "{{review_plan.output.coverage_pct}} < 95"
  max_iterations: 3

```

Always set `max_iterations` on a loop. The default is 100, and that is a lot of LLM calls if your condition never flips.

When I forget a field, `sam config schema show workflow --type loop` (or any other type) prints exactly what that node accepts.

Docs:

- [What Are Workflows?](https://docs.solace.com/Agent-Mesh/Framework/concepts/what-are-workflows.htm)
- [Creating Workflows](https://docs.solace.com/Agent-Mesh/Framework/building/workflows/index.htm)

Workflows are Early Access, so this is a great time to shape them. [Download the Solace Agent Mesh desktop app](https://solace.com/products/agent-mesh/) and build one.

What process would you model as a workflow first? Share it below and I’ll suggest which node types fit.