Note adds visual documentation to your workflows without affecting data flow. Perfect for explaining workflow logic, providing instructions to team members, and creating professional workflow templates.

​
When to Use It

Use this node to:
  • Document complex workflow logic for team members
  • Add setup instructions for workflow templates
  • Explain business rules and decision criteria
  • Create workflow sections and organize canvas layout
  • Share context and reasoning behind workflow design

​
How It Works

Note nodes are pure documentation - they don’t connect to other nodes or process data. They exist solely to provide context and instructions on your workflow canvas.

​
Key Features

No Data Flow:
  • No input or output connections
  • Doesn’t affect workflow execution
  • Pure visual documentation
Markdown Support:
  • Format text with bold, italic, and lists
  • Create headers, links, and structured content
  • Rich text formatting for professional documentation
Locking Capability:
  • Lock notes to prevent accidental editing
  • Locked notes can’t be moved or edited
  • Perfect for finalized templates and shared workflows

​
Inputs

FieldTypeRequiredDescription
Note ContentText AreaNoYour documentation text with markdown support
Additional styling options (width, height, color, lock) are available in advanced settings

​
Markdown Formatting

You can style your notes using standard markdown: 
# Main Title
## Section Header

**Important:** This workflow runs daily at 9 AM

*Required setup:*
- Connect Google Ads account
- Set up reporting spreadsheet
- Configure email recipients

[Link to documentation](https://docs.company.com)

> **Note:** Always test before publishing

​
Locking Notes

When to Lock:
  • Finalized workflow templates
  • Critical instructions that shouldn’t change
  • Shared workflows with multiple editors
  • Production workflows to prevent accidents
Locked Note Behavior:
  • Cannot be moved on canvas
  • Text editor won’t open when clicked
  • Prevents accidental modifications
  • Maintains template integrity

​
Best Practices

Content Organization:
  • Use clear, descriptive titles
  • Break up long text with headers and lists
  • Include contact information for questions
  • Link to external documentation when helpful
Visual Organization:
  • Use consistent colors for different note types
  • Position notes near relevant workflow sections
  • Size notes appropriately for content length
  • Group related notes together
Team Collaboration:
  • Include setup requirements and prerequisites
  • Document any manual steps or dependencies
  • Explain complex business logic
  • Provide troubleshooting tips

​
FAQ