ActionDatadogUpdated September 2026

How do I query Datadog metric time-series?

Short answer: You can query datadog metrics in Datadog by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Datadog Query Datadog Metrics action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Query Datadog Metrics in Datadog — start free All 4 Datadog actions

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.

Triggered by

Apps that pair well as the trigger for Query Datadog Metrics.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Datadog

2 Google Sheets triggers

HubSpot → Datadog

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Datadog returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Query Datadog Metrics support batch operations?

Run Query Datadog Metrics inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Datadog's rate limits.

More actions

Other Datadog actions.

Action

Create Datadog Monitor

Programmatically defines an alerting monitor with query, thresholds, and notification list. Useful for infrastructure-as-workflow patterns where new services auto-provision their monitoring.

Action

List Datadog Monitors

Returns every monitor in the org with status and filter tags. Useful for "what's firing right now" dashboards or "audit monitors that haven't alerted in 6 months for cleanup" maintenance workflows.

Action

Post Datadog Event

Pushes a discrete event into Datadog's timeline — vertical line annotations on dashboards. The standard "mark when this deploy went live" workflow that helps engineers correlate metric changes with deploy timestamps.

Query Datadog Metrics in Datadog — start free