How to query datadog metrics in Datadog

Query Datadog Metrics in Datadog — start free

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
Metric Query query	string	Required	Metric Query. e.g. "avg:system.cpu.user{*}"
From (epoch) from	number	Required	From (epoch)
To (epoch) to	number	Required	To (epoch)

Sample request

{
  "query": "avg:system.cpu.user{*}",
  "from": "{{trigger.from}}",
  "to": "{{trigger.to}}"
}

Returns

{
  "series": [
    {
      "metric": "system.cpu.user",
      "pointlist": [
        [
          1712835600000,
          45.2
        ],
        [
          1712835660000,
          42.1
        ]
      ]
    }
  ]
}

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

FAQ

Questions about Query Datadog Metrics.

What does the Query Datadog Metrics action do in Datadog?

Runs a Datadog query (aggregator:metric{tags}) over a time range and returns the time-series. Useful for "send the daily KPI metric to Slack" or "alert when error rate doubles" custom workflows.

What inputs does Query Datadog Metrics require?

Required: Metric Query, From (epoch), To (epoch). Every input accepts a static value or a variable from any upstream node in your workflow.

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 Datadog 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 Query Datadog Metrics support batch operations?

Yes. Run Query Datadog Metrics inside a Loop node to process arrays. TinyCommand handles Datadog's rate limits automatically so you don't have to throttle manually.

More actions