> For the complete documentation index, see [llms.txt](https://docs.n8n.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.n8n.io/build/understand-workflows/create-and-run-workflows.md).

# Create and run workflows

A workflow[^1] is a collection of nodes connected together to automate a process. You build workflows on the [workflow canvas](#user-content-fn-2)[^2].

## Create a workflow <a href="#create-a-workflow" id="create-a-workflow"></a>

1. Select the <img src="/files/i7DUe1F1hB5HR3hmbdOG" alt="universal create resource icon" data-size="line"> **button** in the upper-left corner of the side menu. Select workflow.
2. If your n8n instance supports projects, you'll also need to choose whether to create the workflow inside your **personal space** or a specific **project** you have access to. If you're using the community version, you'll always create workflows inside your personal space.
3. Get started by adding a trigger node: select **Add first step...**

Or:

1. Select the <img src="/files/i7DUe1F1hB5HR3hmbdOG" alt="universal create resource icon" data-size="line"> **create** button in the upper-right corner from either the **Overview** page or a specific **project**. Select workflow.
2. If you're doing this from the **Overview** page, you'll create the workflow inside your personal space. If you're doing this from inside a project, you'll create the workflow inside that specific project.
3. Get started by adding a trigger node: select **Add first step...**

If it's your first time building a workflow, you may want to use the [quickstart guides](https://github.com/n8n-io/n8n-docs/blob/main/try-it-out/index.md) to quickly try out n8n features.

## Run workflows manually <a href="#run-workflows-manually" id="run-workflows-manually"></a>

You may need to run your workflow manually when building and testing, or if your workflow doesn't have a trigger node.

To run manually, select **Execute Workflow**.

## Run workflows automatically <a href="#run-workflows-automatically" id="run-workflows-automatically"></a>

All new workflows are unpublished by default. See [Publishing and saving workflows](/build/understand-workflows/save-and-publish-workflows.md).

You need to publish workflows that start with a trigger node or Webhook node so that they can run automatically. When a workflow is inactive, you must run it manually.

To publish your workflow, open your workflow and click **Publish**. The option to unpublish is in the workflow settings menu.

Published workflows run whenever its trigger conditions are met.

[^1]: An n8n workflow is a collection of nodes that automate a process. Workflows begin execution when a trigger condition occurs and execute sequentially to achieve complex tasks.

[^2]: The canvas is the main interface for building workflows in n8n's editor UI. You use the canvas to add and connect nodes to compose workflows.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.n8n.io/build/understand-workflows/create-and-run-workflows.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
