> 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/workflow-components/add-notes-and-documentation.md).
# Add notes and documentation
Sticky Notes allow you to annotate and comment on your workflows.
n8n recommends using Sticky Notes heavily, especially on [template workflows](/key-concept-glossary.md#template-n8n), to help other users understand your workflow.
## Create a Sticky Note
Sticky Notes are a core node. To add a new Sticky Note:
1. Open the nodes panel.
2. Search for `note`.
3. Click the **Sticky Note** node. n8n adds a new Sticky Note to the canvas.
## Edit a Sticky Note
1. Double click the Sticky Note you want to edit.
2. Write your note. [This guide](https://commonmark.org/help/) explains how to format your text with Markdown. n8n uses [markdown-it](https://github.com/markdown-it/markdown-it), which implements the CommonMark specification.
3. Click away from the note, or press `Esc`, to stop editing.
## Change the color
To change the Sticky Note color:
1. Hover over the Sticky Note
2. Select **Change color** 
3. Choose from seven preset colors, or click the rainbow gradient button to select a custom color
### Custom colors
In addition to the seven preset colors, you can select any custom color for your sticky notes:
1. Click the button with the rainbow gradient and plus icon
2. Use the color picker to select your desired color, or enter a hex color code (for example, `#FF5733`)
3. Click **Apply** to set the color
Your recently used custom colors (up to 8) are automatically saved and displayed in the color picker for quick access.
Custom colors feature theme-aware borders that automatically adjust for optimal visibility in both light and dark modes.
## Sticky Note positioning
You can:
* Drag a Sticky Note anywhere on the canvas.
* Drag Sticky Notes behind nodes. You can use this to visually group nodes.
* Resize Sticky Notes by hovering over the edge of the note and dragging to resize.
* Change the color: select **Options** 
to open the color selector.
## Writing in Markdown
Sticky Notes support Markdown formatting. This section describes some common options.
```
The text in double asterisks will be **bold**
The text in single asterisks will be *italic*
Use # to indicate headings:
# This is a top-level heading
## This is a sub-heading
### This is a smaller sub-heading
You can add links:
[Example](https://example.com/)
Create lists with asterisks:
* Item one
* Item two
Or created ordered lists with numbers:
1. Item one
2. Item two
```
For a more detailed guide, refer to [CommonMark's help](https://commonmark.org/help/). n8n uses [markdown-it](https://github.com/markdown-it/markdown-it), which implements the CommonMark specification.
## Make images full width
You can force images to be 100% width of the sticky note by appending `#full-width` to the filename:
```markdown
```
## Embed a YouTube video
To display a YouTube video in a note, use the `@[youtube]()` directive with the video's ID. For this to work, the video's creator must allow embedding.
For example:
```markdown
@[youtube](ZCuL2e4zC_4)
```
To embed your own video, copy the above syntax, replacing `ZCuL2e4zC_4` with your video ID. The YouTube video ID is the string that follows `v=` in the YouTube URL.
---
# 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/workflow-components/add-notes-and-documentation.md?ask=&goal=
```
`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.