Resources · Make integration

Datadog Make integrationAutomate Datadog with Make.

What if your sales or signups showed up on the same Datadog graphs as your servers? The Datadog Make integration gives you 2 action modules, no trigger. This page links your API keys, builds a first scenario that posts a metric, and shows where the limits sit.

Try the Datadog integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Datadog Make integration do for you?

The Datadog Make integration lets a Make scenario write data into your Datadog account. A scenario is the automation you build in Make: a chain of modules, each one a single brick such as a trigger or an action. Here the bricks push time-series points that Datadog can graph, or call any endpoint of the Datadog API.

Revenue beside uptime. Post Timeseries Points sends a value, like the amount of an order from your shop app, into Datadog. Your ops team then reads business activity and infrastructure load on one dashboard, without a separate reporting tool.

A pulse on the funnel. Each new form entry or support ticket in another app becomes one point. A sudden drop in that line tells you something broke upstream, even when every server looks healthy.

Everything the list skips. Make an API Call reaches any endpoint of the Datadog API with the connection you already set up, so you are not stuck with the two listed actions.

What this app does not do: it has no trigger, so nothing in Datadog starts a scenario by itself. Another app or a schedule has to kick things off. One payload to the metrics endpoint is capped at 3.2 megabytes. The same app may also exist on the n8n side, and the n8n vs Make comparison sets out the criteria. To see what each plan allows, read Make pricing, and for a guided start, the Make training.

Connect

How do you connect Datadog to Make?

  1. 01

    Copy your two keys

    A connection is your Datadog account linked to Make once, then reused by every Datadog module. In Datadog, open Organization Settings, copy the key from the API keys tab, then the one from the Application Keys tab.

  2. 02

    Open the connection window

    In your scenario, add any Datadog module and click Create a connection. The Connection name field is optional, but a clear label helps once you run several Datadog accounts or environments.

  3. 03

    Paste your keys

    Paste the API key and the Application key you copied, or follow the on-screen instructions, to create the connection. The new connection now shows in the module, and every Datadog module you add later can pick it.

First scenario

Your first scenario: turn app events into a Datadog metric

GoalWhen a new order lands in your shop app, Make posts its amount as a point in Datadog.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where the event happens, such as your shop or form tool, and its trigger.

  2. 02

    Add Post Timeseries Points

    Click the + on the right of that first module, search for Datadog and pick Post Timeseries Points. Select the connection you created, or click Create a connection now.

  3. 03

    Map the value

    Fill the fields the module asks for. Map the number from the previous module, since each bundle (one item passing between modules, here one order) carries its own value.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can check the value before it lands in Datadog.

  5. 05

    Schedule and switch on

    On the first module, set the schedule (every 15 minutes by default on a new scenario), then switch the scenario on. Each module run counts as one operation on your plan.

Modules

What the Datadog modules do

Datadog gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Datadog1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This module opens the whole Datadog API to your scenario, using the same connection as the other module. You pick the endpoint yourself and Make handles the authorization with your keys.

When to use it
the action you need is not Post Timeseries Points, for example reading data back or touching another part of your Datadog account.
Watch out
you work from the Datadog API documentation here, so check each request with Run once before switching the scenario on.
Datadog2

Post Timeseries Points

Action

In Make“The metrics end-point allows you to post time-series data that can be graphed on Datadog’s dashboards. The limit for payloads is 3.2 megabytes (3200000).”

This module takes a number from another app and adds it as a point on a Datadog metric. Point after point, you get a line on your dashboard that you can watch like any server graph.

When to use it
a business event such as a paid order or a new signup should appear next to your infrastructure metrics.
Watch out
one payload cannot exceed 3.2 megabytes, so avoid pushing huge batches in a single call.
Need help

Need help automating Datadog with Make?

A person reads every message.

FAQ

Datadog and Make: common questions

01Is the Datadog Make integration free?
Yes, on the Make side. Datadog is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and lift the cap on active scenarios. You still need an active Datadog account with valid keys, and its own pricing is set by Datadog, not by Make.
02What do you need to connect Datadog to Make?
An active Datadog account plus two credentials: an API key and an Application key. Both live under Organization Settings in Datadog, on the API keys tab and the Application Keys tab. In Make, add a Datadog module, click Create a connection, give it a name if you want, then paste the two keys. The connection is saved once and every Datadog module in your scenarios reuses it. If you manage several Datadog accounts, name each connection clearly.
03Can a Datadog event trigger a Make scenario in real time?
No, not with the listed modules. The Datadog app in Make has no trigger at all, only two actions. Your scenario therefore starts from somewhere else. The simplest option is a schedule on the first module, every 15 minutes by default on a new scenario, and down to 1 minute on paid plans. The other option is a trigger from another app, such as your shop or your form tool, which then hands its data to Post Timeseries Points.
04What if the Datadog module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Datadog API through the connection you already created, so nothing new to set up on the account side. You write the request from the Datadog API documentation, then test it with Run once. For metric data, remember the 3.2 megabyte cap on one payload. The Datadog page in the Make doc also warns that its content is AI-generated, so confirm key details with Datadog.
05Should you use Make or n8n for Datadog?
It depends on how your team likes to build. Make gives you a visual editor where each module is a brick, and Datadog there offers two actions plus a generic API call. Many apps also have an n8n node, so check whether Datadog has one and what it covers against the calls you actually need. Compare which operations each tool covers for Datadog, how you prefer to test, and how each counts usage, rather than picking a winner in the abstract.
Same platform

Other docs you might need on this stack.

Browse all integrations