> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/build-and-improve/automate/build-a-workflow/canvas-reference.md).

# Canvas reference

Reference for the current Workflow editor itself.

The canvas has three useful layers to understand:

* **Workflow header** — Workflow/version selection plus Run, Feedback, Test and Publish;
* **execution canvas** — action cards and the connections between them;
* **canvas controls** — zoom, fit/navigation tools, minimap and Add Action.

Use the pages below when you need editor mechanics rather than conceptual Workflow design.

* **Canvas Controls** — move around and organise a larger Workflow.
* **Action Cards** — understand what the cards represent and how to work with them.
* **Action Connections** — understand the execution path between cards.
* **Keyboard Shortcuts** — faster editor navigation and manipulation where supported.

A clean-looking Workflow can still be configured incorrectly. Always verify configuration, bindings and test results rather than inferring behaviour from card layout alone.


---

# 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.lleverage.ai/build-and-improve/automate/build-a-workflow/canvas-reference.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.