ActionDatadogUpdated September 2026

How do I list Datadog monitors?

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

List Datadog Monitors in Datadog — start free All 4 Datadog actions

List Datadog Monitors 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
Name Filter name	string	Optional	Name Filter. Example: API latency
Tags Filter tags	string	Optional	Tags Filter. Example: env:production

Sample request

{
  "name": "e.g. API latency",
  "tags": "e.g. env:production"
}

Returns

[
  {
    "id": 123,
    "name": "API Latency > 500ms",
    "tags": [
      "env:production"
    ],
    "type": "metric alert",
    "overall_state": "OK"
  }
]

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

Triggered by

Apps that pair well as the trigger for List Datadog Monitors.

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 List Datadog Monitors.

What does the List Datadog Monitors action do in Datadog?

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.

What inputs does List Datadog Monitors require?

List Datadog Monitors 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 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 List Datadog Monitors support batch operations?

Run List Datadog Monitors 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

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.

Action

Query Datadog Metrics

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.

List Datadog Monitors in Datadog — start free