- Integrations
- /
- Datadog
- /
- Actions
- /
- Create Datadog Monitor
ActionDatadogUpdated May 2026
How do I create a Datadog monitor?
Short answer: Drop the "Datadog → Create Datadog Monitor" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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.
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 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 Create Datadog Monitor support batch operations?
Yes. Run Create Datadog Monitor inside a Loop node to process arrays. Tiny Command handles Datadog's rate limits automatically so you don't have to throttle manually.
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.
ActionPost 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.
ActionQuery 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.
Send create datadog monitor from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.