Short answer: Drop the "Datadog → Create Datadog Monitor" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
{"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"}
{"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.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.