> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryblend.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Annotation

> Add sticky notes, image boards, frames, and arrows to explain and organize a workflow without changing its execution.

Annotation nodes are visual canvas helpers. Use them to document decisions, group related nodes, show reference images, or draw attention to part of a workflow.

They have no input or output handles, do not execute, do not affect run counts, and do not add cost.

## Annotation types

Choose a type when you add the node, or switch types from the toolbar while it is selected.

<AccordionGroup>
  <Accordion title="Sticky" icon="note-sticky">
    Write a free-form note directly on the canvas. Drag the resize handle to change its size.

    When selected, a Sticky can use yellow, rose, blue, green, violet, blurred-glass, or transparent styling.
  </Accordion>

  <Accordion title="Image" icon="image">
    Select images from your library or upload new ones. The annotation lays them out in a responsive grid and can hold up to **20 images**.

    Use the image button to add more, remove images individually, and resize the annotation to change the grid's shape.
  </Accordion>

  <Accordion title="Frame" icon="object-group">
    Draw a labeled, resizable frame around a section of the workflow.

    Select the frame and choose **Grab all** to select the frame plus every workflow node touching its area. Move the selection together, then choose **Ungrab** to release the grouped selection. The frame is organizational only; it does not create execution scope.
  </Accordion>

  <Accordion title="Arrow" icon="arrow-right">
    Point from one part of the canvas to another. Select the arrow to reveal controls for its start, end, and bend.

    Drag either endpoint to point in any direction. Drag the midpoint to change the curve.
  </Accordion>
</AccordionGroup>

## Inputs and outputs

Annotation has no handles. It cannot receive workflow data or feed another node.

| Direction | Handles |
| --------- | ------- |
| Inputs    | None    |
| Outputs   | None    |

## Behavior in runs and publishing

* Annotation nodes are omitted from the execution plan.
* They never produce results, errors, run history, or credit usage.
* Their position, size, content, images, frame labels, and arrow geometry are saved with the workflow.
* They remain useful to workflow editors, but do not become Runner fields or API inputs/outputs.
* Annotation does not support a single-node run because there is nothing to execute.

<Note>
  A Frame helps move and organize touching nodes on the canvas. It does not make those nodes a sub-workflow and does not change dependency order.
</Note>

## Next steps

<CardGroup cols={2}>
  <Card title="Workflow overview" icon="diagram-project" href="/workflow/overview">
    See how annotations fit alongside executable workflow nodes.
  </Card>

  <Card title="Running the full workflow" icon="play" href="/concepts/full-run">
    Understand which canvas nodes participate in a run.
  </Card>
</CardGroup>