- Home
- Resources
- Integrations
- Sticky Note
n8n Sticky Note nodeConfigure Sticky Note in n8n.
A workflow nobody can read gets rebuilt from scratch instead of reused. The n8n Sticky Note node drops a colored panel onto the canvas, with 4 parameters: content, height, width and color. It carries the explanation a node name cannot hold, for whoever opens the workflow next.
Verified Trustpilot reviews · AI, automation & growth agency
What does the n8n Sticky Note node change on a canvas?
Sticky Note is a core node shipped with n8n, and its job is written into the node description: make your workflow easier to understand. It sits on the canvas as a resizable colored panel holding free text. Four parameters drive it, and only one of them is about words: content, then height, width and color, which decide how much of the canvas the panel covers and how it reads at a glance.
Take a workflow that pushes form entries into a spreadsheet. The nodes say what happens, never why. A note stretched over the export section, sized with Height and Width so it sits behind the whole group, can state which team owns that Google Sheets tab and what to check before touching it. The person who opens the canvas in a hurry reads that first.
Second scenario: a branch that exists for one edge case. An If node splits the run, and the false path does something that looks wrong until you know the history. A note in a distinct Color, parked next to that path, holds the two sentences of context. Nothing about the execution changes, but the next reader stops guessing.
Third scenario: a call to an API with no dedicated node. An HTTP Request node covers any HTTP endpoint, and that is exactly the kind of block where the URL alone explains nothing. The note next to it can name the endpoint's purpose and the field the workflow reads back from the response.
Know when a note is the wrong fix. If the confusion comes from unnamed data, renaming fields in an Edit Fields (Set) node documents the flow better than a paragraph describing it, because the names travel with the items. If a branch needs a note just to be followed, splitting it explicitly is usually the real answer. Text is a last layer, not a patch over a confusing canvas.
The limits are worth stating plainly. The node holds 4 parameters at version 1, so there is nothing to tune beyond text, size and color. Content is the only parameter that is not required, which means a note can be empty, and an empty note is just a colored rectangle that the next person has to interpret. If you want the reasoning behind a whole family of workflows rather than one canvas, that belongs in your own documentation, and our n8n training covers how teams keep both in sync.
Which parameters does the Sticky Note node expose?
The Sticky Note node has 4 parameters. For each one: the node as you configure it in n8n, what the parameter changes, and our field notes.
Parameters index
Content
contentWhat you see in n8n
Notes & use cases
Content is the text the note shows on the canvas. It is the only parameter of the node that is not required, so a note with nothing typed in it still renders as a panel and still takes up the same space.
Key parameters
- Content: the text carried by the note, typed into the panel; leaving it empty is allowed and produces a note with no message.
Height
heightWhat you see in n8n
Notes & use cases
Height sets how far the note extends down the canvas. It is a required number, so it always carries a value, and it is what lets a note cover a whole vertical stack of nodes instead of floating beside them.
Key parameters
- Height: a required number; its value sets how tall the panel is drawn.
Width
widthWhat you see in n8n
Notes & use cases
Width does the same job across the canvas. Also a required number, it decides how far right the panel reaches, which in practice decides where your sentences wrap and whether a note reads as a title or as a paragraph.
Key parameters
- Width: a required number; a narrow value keeps a short caption tight, a wide one suits several lines of explanation.
Color
colorWhat you see in n8n
Notes & use cases
Color is stored as a required number, and it is the parameter that turns notes into a system rather than a pile of panels. Readers pick up on the color before the text, so a consistent scheme across a workspace does real work.
Key parameters
- Color: a required number selecting the panel color; keeping the same value for the same kind of message is what makes the canvas scannable.
Need help automating Sticky Note with n8n?
A person reads every message.
Sticky Note in n8n, the questions that come next
01Is the Sticky Note node free in n8n?
02What credentials does the n8n Sticky Note node need?
03What are the limits of the Sticky Note node?
04When should you use a note rather than restructure the workflow?
05n8n or Make for documenting a workflow?
Get our weekly integration tips.
No spam. Unsubscribe anytime.
