> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/guides-and-quickstarts/workflow-builder/canvas-organization.md).

# Canvas organization

Canvas controls help you navigate and explain a workflow. Node positions and notes make the processing path easier to read.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FZnIIhkVjLQJYChNZmAiB%2FG034.mp4?alt=media&token=c97ad9e6-10ce-4dd7-970f-045140ca9c19>" %}

## Fit and arrange the canvas

Choose Fit view to screen to see the workflow together.

![Fit view to screen control](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/mSxihQpR28RBa1y0ADJV/assets/g034-g034-01-fit.png)

Use this when the canvas position makes part of the execution path difficult to find.

Drag related nodes into a clear reading order and leave room for labels.

![Nodes arranged into a readable path](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/V9mAGq8JmvVEx7jYANvI/assets/g034-g034-02-arrange.png)

Check that their connections still show the intended execution path.

## Explain a workflow with notes

Right-click empty canvas space and select Add a note.

![Add a note canvas action](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/8wudnVXRIx4MgTxWW1Vo/assets/g034-g034-03-note.png)

Place a short explanation beside the relevant nodes. Notes describe the workflow but do not execute.

## Arrange nodes automatically

Select Auto arrange nodes and review the resulting layout.

![Automatically arranged workflow nodes](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/MG9wI2LWkspAKQpQi3Lk/assets/g034-g034-04-auto-arrange.png)

Check branching paths and labels before keeping the new arrangement.

## Navigate a large workflow

Use the minimap to move around a large workflow.

![Minimap navigation for a larger workflow](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/MczUG0pD75LiXtB8XWhZ/assets/g034-g034-05-minimap.png)

Combine it with Fit view when you need to return to the whole graph.

Review the canvas after arranging it.

![Canvas labels and connections after arrangement](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/HhZQzdjh0osAhOb0wL9x/assets/g034-g034-06-result.png)

Keep labels readable and leave enough space to follow the connections between nodes.

## Important behavior

Node positions and notes do not determine execution. Connections define how the workflow runs.

## Related steps

* [First input to output workflow](https://docs.stackai.com/guides-and-quickstarts/workflow-builder/first-input-to-output-workflow.md)
* [Conditional and AI routing](https://docs.stackai.com/guides-and-quickstarts/workflow-builder/conditional-and-ai-routing.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/guides-and-quickstarts/workflow-builder/canvas-organization.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
