ActionDatadogUpdated September 2026

How do I create a Datadog monitor?

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

Create Datadog Monitor in Datadog — start free All 4 Datadog actions

Create Datadog Monitor 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
Monitor Name name	string	Required	Monitor Name. Example: High Error Rate
Type type	options	Required	Type. Options: Metric Alert, Service Check, Log Alert, Query Alert
Query query	string	Required	Datadog monitor query
Alert Message message	string	Optional	Message sent when monitor triggers. Supports @mentions.
Tags tags	string	Optional	Comma-separated tags

Sample request

{
  "name": "e.g. High Error Rate",
  "type": "{{trigger.type}}",
  "query": "e.g. avg(last_5m):avg:system.cpu.user{*} > 90",
  "message": "e.g. CPU usage is above 90%! @ops-team",
  "tags": "e.g. env:production, team:backend"
}

Returns

{
  "id": 123,
  "name": "High Error Rate",
  "type": "metric alert",
  "overall_state": "No Data"
}

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

Triggered by

Apps that pair well as the trigger for Create Datadog Monitor.

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 Create Datadog Monitor.

What does the Create Datadog Monitor action do in Datadog?

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

What inputs does Create Datadog Monitor require?

Required: Monitor Name, Type, Query. 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 Create Datadog Monitor support batch operations?

Run Create Datadog Monitor 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

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.

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.

Create Datadog Monitor in Datadog — start free