> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/workflows/drag-and-drop-canvas.md).
# Drag-and-drop canvas
You can create workflows using a visual drag-and-drop canvas, where you define the use cases with actions, triggers, remediation steps and paths. You also have a wide range of pre-established templates (playbooks), which can be customized to your organization's specific applications or use cases.
The workflow window contains following sections:
* **Actions** - The workflow actions are the building blocks for the workflow, and appear in the left pane.
* **Canvas** - The main section where you create the workflow.
* **Trigger** - The trigger event and conditions appear in the right pane.
* **Ribbon** - Displays the workflow settings above the canvas.
Drag actions from the left pane into the workflow canvas, and define them on the right
{% hint style="warning" %}
You need **Admin** permission to create workflows.
{% endhint %}
---
# 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.docontrol.io/docontrol-user-guide/workflows/drag-and-drop-canvas.md?ask=&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.
