List Grafana Dashboards: Grafana action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Search Query query	string	Optional	Search Query. Example: API latency
Filter by Tag tag	string	Optional	Filter by Tag. Example: production
Limit limit	string	Optional	Limit. e.g. "100"

Sample request

{
  "query": "e.g. API latency",
  "tag": "e.g. production",
  "limit": "100"
}

Returns

[
  {
    "id": 1,
    "uid": "abc123",
    "url": "/d/abc123/api-latency",
    "tags": [
      "production"
    ],
    "title": "API Latency"
  }
]

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List Grafana Dashboards.

What does the List Grafana Dashboards action do in Grafana?

Returns paginated dashboards with optional folder, tag, search filters. Useful for resolving dashboard IDs at workflow setup and for dashboard inventory.

What inputs does List Grafana Dashboards require?

List Grafana Dashboards has no required inputs. Sensible defaults are applied if you leave fields blank.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Grafana returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Grafana Dashboards support batch operations?

Yes. Run List Grafana Dashboards inside a Loop node to process arrays. Tiny Command handles Grafana's rate limits automatically so you don't have to throttle manually.

More actions