> For the complete documentation index, see [llms.txt](https://docs.countercyclical.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.countercyclical.io/agents/orchestrations.md).

# Orchestrations

Create and inspect repeatable workflows that connect Agents, tools, routing, and reviewed outputs.

An orchestration is a saved workflow of connected nodes. It defines how work starts, what data and Agents are used, how results are routed, and what outputs may require review. Open **Orchestrations** from the workspace sidebar.

### Building an Orchestration

Start from a blank workflow, an available template, or the Agent-assisted creation flow. Open the Canvas to add or edit nodes and connections. Select a node to open its properties.

A workflow can start from a conversation prompt or an eligible stage action. Data source inputs and tool calls supply information to the workflow. Agent and control nodes determine what work runs before the outputs.

### Working in Canvas and Insights

| **Area**                                                                       | **What You Can Do**                                                                  |
| ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------ |
| [Canvas](https://docs.countercyclical.io/agents/orchestrations/canvas)         | Edit the workflow, connect nodes, and follow execution on its graph.                 |
| [Runs](https://docs.countercyclical.io/agents/orchestrations/runs)             | Choose supported test, live, or scheduled execution and review its state.            |
| [Insights](https://docs.countercyclical.io/agents/orchestrations/insights)     | Review run activity, metrics, and history.                                           |
| [Inspection](https://docs.countercyclical.io/agents/orchestrations/inspection) | Open a recorded run and inspect the steps, outcomes, and approvals available to you. |

### Access, Approvals, and Destinations

{% hint style="warning" %}
**Before Turning on a Trigger**

Live execution follows workspace agent, model, tool, data, and credit policies. Validate the graph before a live run. Confirm the output destination and review requirements before you enable scheduled or stage-triggered execution.
{% endhint %}

A run may pause for approval or produce a draft or packet requiring a separate review. Inspect the requested change before deciding. Test and live runs have different effects.

### Related Pages

{% content-ref url="/pages/cF8IpbCXsAxGxbWhfba4" %}
[What is a Hierarchical Multi-Agentic System (HMAS)?](https://docs.countercyclical.io/agents/orchestrations/what-is-a-hierarchical-multi-agentic-system-hmas.md)
{% endcontent-ref %}

{% content-ref url="/pages/GpBh1FTo213H5v0crxJe" %}
[Nodes](https://docs.countercyclical.io/agents/orchestrations/nodes.md)
{% endcontent-ref %}

{% content-ref url="/pages/9NEXbp8Di0WukRXH82g3" %}
[Using Agents to Build Orchestrations](https://docs.countercyclical.io/agents/orchestrations/using-agents-to-build-orchestrations.md)
{% endcontent-ref %}

{% content-ref url="/pages/Rl2WZFJmGl0gjAjkDEyA" %}
[Governance](https://docs.countercyclical.io/agents/governance.md)
{% endcontent-ref %}
