Floyo Sticky-Node
Floyo Sticky Note is a documentation node that lets you add rich-text notes directly to your workflow canvas, to explain sections, document settings, and leave instructions for collaborators. It makes complex workflows self-explanatory.
Overview
Floyo Sticky Note lets you add rich-text notes directly onto your workflow canvas so you can explain sections, document important settings, and leave instructions for teammates.
Unlike processing nodes, a Sticky Note has no inputs or outputs and does not participate in workflow execution. Think of it as a comment block for your workflow purely for context, never for processing.
Sticky Notes support a range of content, making them useful for both personal workflows and team collaboration:
Supports | Use it to |
|---|---|
Rich-text formatting | Headings, lists, bold/italic, code blocks, dividers |
Themes | Visually separate different workflow sections |
Images & videos | Show examples or embed walkthroughs inline |
Links | Point to docs, models, or related workflows |
Directional pointers | Visually connect a note to the nodes it describes |
Why use Sticky Notes?
Sticky Notes make workflows more readable and easier to maintain. Use them to:
- Explain what a workflow section does
- Document important settings
- Leave instructions for teammates
- Organize large workflows into clearly labeled areas
They're especially valuable when sharing workflows, since they provide context directly on the canvas, without affecting execution.
Creating a Sticky Note
- Add the node: Drop the 📝 Floyo Sticky Note node onto your workflow canvas.
- Open the editor: Double-click anywhere inside the note body, or click the ✎ Edit icon in the bottom-right corner of the node to open the rich-text editor.
- Add your content: Enter what you want to display. The editor supports headings, text formatting, lists, links, images, videos, code blocks, and dividers. Pick a theme to help separate sections.
- Save: Click the green ✓ Save button, or click anywhere outside the note. Changes save automatically with the workflow.
Best practices
Practice | Why it matters |
|---|---|
Add context, don't repeat | Explain why, not what's already visible in node names. |
Keep it concise | Short, clear notes — especially for workflows meant for public use. |
Use themes consistently | Apply the same theme logic across sections so the canvas reads predictably. |
Maintain clear spacing | Keep notes from crowding nodes so the canvas stays readable. |