Short answer: Drop the "Grafana → Create Grafana Annotation" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Annotation Text text | string | Required | Annotation Text. Example: Deployed v2.1.0 to production |
Tags tags | string | Optional | Comma-separated tags for filtering |
Dashboard UID dashboardUID | string | Optional | Limit annotation to a specific dashboard. Leave empty for global. |
Time (epoch ms) time | string | Optional | Annotation timestamp. Leave empty for current time. |
{"text": "e.g. Deployed v2.1.0 to production","tags": "e.g. deployment, production","dashboardUID": "e.g. abc123","time": "e.g. 1700000000000"}
{"id": 1,"message": "Annotation added"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.