Post Datadog Event: Datadog action

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
Title title	string	Required	Title
Text text	string	Required	Text
Alert Type alert_type	options	Optional	Alert Type. Options: Info, Warning, Error, Success
Tags tags	string	Optional	Tags. e.g. "env:prod,service:web"

Sample request

{
  "title": "{{trigger.title}}",
  "text": "{{trigger.text}}",
  "alert_type": "{{trigger.alert_type}}",
  "tags": "env:prod,service:web"
}

Returns

{
  "event": {
    "id": 12345,
    "text": "Version 2.0 deployed",
    "title": "Deploy completed"
  }
}

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

FAQ

Questions about Post Datadog Event.

What does the Post Datadog Event action do in Datadog?

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.

What inputs does Post Datadog Event require?

Required: Title, Text. 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 Post Datadog Event support batch operations?

Yes. Run Post Datadog Event 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