Datadog Zapier integrationAutomate Datadog with Zapier.
The Datadog Zapier integration gives you 2 actions, 0 triggers and 0 searches. In plain terms: other apps can feed numbers into Datadog through Zapier, but nothing that happens inside Datadog can start an automation. Here is how to use that one-way door well.
Verified Trustpilot reviews · AI, automation & growth agency
What the Datadog Zapier integration actually does
Connecting Datadog to Zapier lets a business event from another tool land in Datadog as a data point on a metric you name. It runs in one direction only: Zapier writes to Datadog, it never listens to it. That makes it a feeder for your dashboards, not a way to react to alerts.
Three things people actually get out of it. A business counter next to your server graphs: every time a form is submitted or a deal closes elsewhere, New Metric Post adds a point to a metric, so ops and sales numbers sit on the same dashboard. A clean signal from a messy source: a filter step lets only the events that matter through before the point is written, so the metric stays readable. Anything the menu does not offer: API Request (Beta) calls Datadog with your stored login, for the odd job the ready-made action does not cover.
What Zapier does not do here matters just as much. There is no Datadog trigger on Zapier, so a monitor firing, an incident opening or a dashboard changing cannot start a Zap. There is no search step either: a Zap cannot look up a host, a metric or an event in Datadog and reuse the answer. If your plan was to route Datadog alerts into a chat tool or a ticket queue through Zapier, this integration will not get you there on its own.
If you need Datadog to start the flow, check what the Datadog Make integration offers on the Make side, and at our Make vs Zapier comparison to weigh the two by criteria rather than by habit.
Zapier vocabulary in one minute
Seven words come back on every Zapier screen. Each one is explained once here, then used as is on the rest of the page.
- Zap
- The automation you build on Zapier: one trigger, followed by one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. Datadog has none, so the trigger always comes from another app.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you. Datadog offers two.
- Task
- The unit Zapier bills. One action that completes successfully is one task, and your plan is a monthly count of those.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer set by your plan. An instant trigger is pushed by the app the moment the event happens.
- Filter
- A step that lets the Zap carry on only when the incoming data meets your condition, and stops it quietly otherwise.
- Multi-step Zap
- Any Zap with more than one trigger and one action. A second action or a filter makes it one, and it then needs a paid plan.
What a Datadog Zap really costs
The trigger never costs anything, and neither does Zapier checking for new data. You pay in tasks, one per successful action.
- Free plan100 tasks a month
- Free plan steps2 (one trigger, one action)
- Premium appNo
- Cost of the trigger0 tasks
Each metric point written to Datadog is one task. A failed write is not counted. Add a filter and the Zap becomes multi-step, so it leaves the free plan, whose Zaps stop at two steps. Datadog itself is not a premium app, so it works from the free plan. Since the trigger comes from another app, its polling interval follows the grid below if that trigger is a polling one.
In short: one point, one task.
Connect Datadog to Zapier in three steps
- 01
Open your connections
In Zapier, go to Apps, then click + Add connection. A connection is your Datadog account linked once, then reused by every Zap that touches Datadog.
- 02
Pick Datadog
Type Datadog in the search box of the dialog, select it, then confirm with Add connection. A new browser tab opens on the Datadog side to finish the link.
- 03
Sign in and grant access
Log in to Datadog in that tab and allow Zapier to act on the account. You need a Datadog account of your own, plus write access to anything you did not create and want the Zap to change.
Your first Datadog Zap
GoalAdd a point to a Datadog metric each time your form tool receives a response, but only for the kind of request you want to count.
- 01
Create the Zap and pick the trigger
Start a new Zap and choose your form tool as the app that starts it, with its new-response event. Datadog cannot start a Zap, so the starting point always lives elsewhere.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent responses of the connected account, so you set up the rest of the Zap on a real one rather than a guess.
- 03
Add the filter
Add a Filter step from the plus icon, then fill its three boxes: the field to watch, the rule, the value. A text rule for a text answer. This step makes the Zap multi-step.
- 04
Add the Datadog action
Pick Datadog, then New Metric Post. Type your metric name and set the data point to 1, so each response counts once on the graph.
- 05
Test, then publish
Test the Datadog step and check in Datadog that the point arrived on the right metric. When it does, click Publish to switch the Zap on.
The 2 Datadog actions on Zapier
Datadog gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
New Metric Post
ActionIn Zapier“This covers the data that you want to send to Datadog.”
Writes one number to a Datadog metric each time the Zap runs, so a business event from another app shows up as a point on a graph.
API Request (Beta)
ActionIn Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”
Sends a request of your own straight to Datadog, reusing the login stored in your connection, for whatever the ready-made action does not cover.
When a Datadog Zap breaks
Zapier attaches no help article to Datadog, so the failures below are the general ones, as they play out on this app.
Since Datadog only receives, the weak spots sit upstream, on the trigger app, and in the value you map into the data point. The Zapier troubleshooting guide covers the general method; here are the cases that hit this integration.
Old events never show up
A Zap only reacts to what happens after you publish it. Forms or deals that existed before are never sent to Datadog, so your metric only counts from that day on.A bulk import floods the trigger
When the trigger app suddenly returns a huge batch after a migration, Zapier's flood protection can hold it back, and those points do not reach Datadog while it is held.The same item is not counted twice
On a polling trigger, Zapier remembers what it has already seen, so the same item does not start the Zap twice or add a second point to your counter.A loop eats your tasks
A Zap that writes into the very place its own trigger watches restarts itself again and again. Datadog starts nothing, so the risk comes from a second action writing back into the source app.
Need help automating Datadog with Zapier?
A person reads every message.
