Apify and Datadog Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Keep Apify and Datadog matched by integrating their events and actions. When developer tools events happen in Apify, update the Datadog automatically - without any line of code in visual workflow builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Apify and Datadog

Detailed info you need to know about Apify and Datadog integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Apify

    • Developer Tools
    • 4 triggers
    • 55 searches
    • 60 actions

    Run Apify Actors and tasks, manage datasets and stores, and watch for Actor run completion events.[5]

  • Datadog

    • Developer Tools
    • 6 triggers
    • 63 searches
    • 70 actions

    Monitoring and security platform for cloud applications.[6]

How to connect Apify to Datadog

Set up your Apify and Datadog integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Apify and Datadog work in WEXTL?

WEXTL exposes actions and triggers for Apify and Datadog that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

Apify triggersDatadog actions

Apify modules

  • Abort a Build Aborts a build while it is still running and ends its work early.
  • Abort a Build (Cross-Actor) Ends a build directly through its Build, without first naming the Actor that owns it.
  • Abort a Run Cancels a run that has not finished yet and halts whatever the Actor was doing.
  • Abort a Run (Cross-Actor) Terminates a run directly through its Run, with no Actor needed.
  • Add a Request to a Queue Puts a single new request into a request queue, where it waits to be processed.
  • Batch Add Requests Adds up to 25 requests to a request queue in one call, each with a Unique key, URL, Method and Payload. Turn on Add to the front to place them at the head of the queue.
  • Build an Actor Kicks off a new build for an Actor, producing a build record with a Status and Data.
  • Charge Events in a Run Applies charges for events to an Actor run, identified by its Actor and Run.
  • Create a Dataset Sets up a dataset in Apify storage and returns its Created at time.
  • Create a Key-Value Store Opens a new key-value store, a place that keeps records under keys.
  • Create a Request Queue Opens a new request queue that holds requests waiting to be processed.
  • Create a Schedule Registers a schedule through Apify and returns its Name.
  • Create a Task Saves a task with Apify and returns its Updated at time.
  • Create a Version Attaches another version to an Actor, alongside the ones it already has.
  • Create an Actor Creates an Actor in Apify and returns its ID and Name.
  • Create an Environment Variable Defines a new environment variable on a particular Version of an Actor.
  • Decode and Verify Data Decodes an encoded value and verifies it, the reverse of Encode and Sign Data.
  • Delete a Dataset Removes a dataset from your Apify storage.
  • Delete a Key-Value Store Deletes a key-value store held in your Apify storage.
  • Delete a Record Removes the record kept under a given Recordkey in a key-value store.
  • Delete a Request Removes the request with a given Requestid from a request queue.
  • Delete a Request Queue Deletes a request queue from your Apify storage.
  • Delete a Schedule Removes a schedule that exists in your Apify account.
  • Delete a Task Deletes a stored task from your account.
  • Delete a Version Removes a version that was attached to an Actor.
  • Delete a Webhook Deletes a webhook configured on your Apify account.
  • Delete an Actor Deletes an Actor from your Apify account.
  • Delete an Environment Variable Removes an environment variable from the chosen Actor Version.
  • Download Records (Batch Export) Downloads every record kept in a key-value store as one batch export.
  • Encode and Sign Data Encodes and signs data, producing a value that Decode and Verify Data can check.
  • Get a Build Reads a build of an Actor and reports its Status and last update.
  • Get a Build (Cross-Actor) Reads a build straight from its Build, even when the owning Actor is not known.
  • Get a Build Log Returns the log text that was produced while a build ran.
  • Get a Build Log (Cross-Actor) Returns the log text of a build addressed by Build alone, whichever Actor it belongs to.
  • Get a Dataset Reads the details of a dataset, including its Name and creation time.
  • Get a Key-Value Store Reads the details of a key-value store such as its Name and timestamps.
  • Get a Record by Key Reads the record kept under a given Recordkey in a key-value store.
  • Get a Request Reads a single request from a request queue by its Requestid, including its Status and Data.
  • Get a Request Queue Returns a request queue with its Name and creation time.
  • Get a Run Fetches a single Actor run together with its Status and Updated at.
  • Get a Run (by ID, Cross-Actor) Reads a run straight from its Run, regardless of the Actor behind it.
  • Get a Schedule Returns a schedule with its Name, Status and Created at.
  • Get a Schedule Log Returns the log describing what a schedule has done so far.
  • Get a Task Reads the stored configuration of a task, along with its timestamps.
  • Get a Task Input Reads the input values that are stored with a task and used when it runs.
  • Get a Version Reads a version of an Actor together with its Name and timestamps.
  • Get a Webhook Returns a webhook configuration with its Name and timestamps.
  • Get a Webhook Dispatch Reads a single webhook dispatch by its Dispatchid, including its Status.
  • Get an Actor Looks up an Actor and returns its ID, Name, Status and Data.
  • Get an Environment Variable Reads a single environment variable defined for an Actor Version, with its Name.

Datadog modules

  • Acknowledge an On-Call Page Marks a Datadog On-Call page as acknowledged by the responder.
  • Add a Case Comment Adds a written Comment to a Datadog case. Output has an ID, Author and Created At for the new comment.
  • Add a Team Member Gives a user membership of a Datadog team. Set Role to Admin to let them manage it, or leave it blank for a regular member.
  • Add Dashboards to a List Puts one or more dashboards into a manual Dashboard List, each given by its Dashboard and Type.
  • Add Host Tags Attaches Tags to a host. Source of user marks tags added by hand, and a blank Source covers every source.
  • Aggregate Logs Works out a count, unique count, average or sum over matching log events. Use Group By to split the result by facet, Metric to pick the attribute to compute, and Indexes to search only some log indexes.
  • Archive a Case Archives a Datadog case, which sets its Archived At time. The updated case record is returned.
  • Assign a Case Gives a Datadog case to an Assignee, the user who owns the case.
  • Cancel a Downtime Cancels a downtime, which is a muting window for monitors in Datadog.
  • Cancel a Workflow Run Cancels a Datadog workflow run that is still running.
  • Create a Case Opens a case under a case project, giving it a Title and Type. Use Priority to rank it, Description to explain it and Assignee to give it an owner.
  • Create a Case Project Creates a case project named by Name, with a short Key code that case IDs start with.
  • Create a Dashboard Builds a dashboard from a Title, a Layout Type of Ordered or Free, and a list of Widgets. Add Template Variables so viewers can filter, and turn on Read Only to limit edits to the author and admins.
  • Create a Dashboard List Creates a manual list under a Name, ready to collect dashboards. Output includes the Dashboard Count and ID.
  • Create a Downtime Plans a muting window for a Scope, either one time or recurring through Schedule. Use Mute First Recovery to silence the first recovery notification of a monitor that was already alerting.
  • Create a Global Variable Stores a Synthetics global variable from a Name, Description and Value. Turn on Secure to hide the value once it is saved.
  • Create a Monitor Creates a monitor of a given Type that evaluates a Query. Use Critical Threshold, Warning Threshold and OK Threshold for alert levels, and Message with @handles to choose who is notified.
  • Create a Team Creates a team from a Name and a unique Handle used in @mentions. Add a Description, and use Members to add users to it.
  • Create a User Adds a user from an Email address. Use Name and Title to fill in the profile.
  • Create an API Test Sets up a Synthetics API test with a Name, a Subtype of HTTP, SSL, TCP or DNS, a Frequency and the Locations it runs from. Add Assertions to define what must pass, and a Message for failure notifications.
  • Create an Event Sends an event into the Datadog event stream under a Title and Category. Use Aggregation Key to group related events and Timestamp to set when it happened.
  • Create an Incident Declares an incident from a Title and a Customer Impacted answer. Use Severity to rank it, State to mark where it stands, and Commander to name the lead.
  • Create an Incident Impact Logs a customer impact for an incident, giving a Description and a Start time. Leave End blank while the impact is still going.
  • Create an Incident Todo Attaches a task to an incident, written as its Content. Use Assignees to name who owns it and Due Date to set a deadline.
  • Create an On-Call Page Raises an On-Call page with a Title and an Urgency of Low or High. Use Target Type to page by team, team handle or user, and Description to add detail for the person who is paged.
  • Create an SLO Creates a service level objective from a Name, a Type of Metric or Monitor, and Thresholds. A metric SLO compares two metric queries, and a monitor SLO is based on monitors.
  • Create an SLO Correction Excludes a period from an SLO calculation. Give a Category as the reason and use Time Zone to say which zone the period uses.
  • Delete a Dashboard Deletes the chosen dashboard from your Datadog account.
  • Delete a Dashboard List Removes a manual list of dashboards from Datadog.
  • Delete a Monitor Removes a monitor. Turn on Force Delete to remove it even when an SLO or composite monitor depends on it.
  • Delete a Notebook Deletes a single notebook document stored in Datadog.
  • Delete a Team Deletes a team from your Datadog organization.
  • Delete an Incident Deletes an incident record from Datadog.
  • Delete an SLO Removes a service level objective. Turn on Force Delete to remove it even when a dashboard or monitor refers to it.
  • Delete an SLO Correction Removes one correction that excluded a period from an SLO.
  • Delete Host Tags Clears the tags attached to a host. Use Source to clear only the tags that came from one source.
  • Delete Tests Deletes one or more Synthetics tests in a single call. Turn on Force Delete Dependencies to delete them even when other resources depend on them.
  • Disable a User Disables a user account in your Datadog organization. Turning Disabled off on that user enables the account again.
  • Escalate an On-Call Page Moves an On-Call page up to the next level of its escalation policy.
  • Get a Case Fetches one Datadog case with its Attributes, Description and Created At.
  • Get a Case Project Reads a case project with its Key, Name and Settings.
  • Get a Dashboard Loads a dashboard, including its Author Handle, Description and Default Timeframe.
  • Get a Dashboard List Looks up a manual dashboard list and shows its Name, Author and Dashboard Count.
  • Get a Downtime Pulls up a downtime with its Message, Display Timezone and Monitor Identifier.
  • Get a Global Variable Reads a Synthetics global variable and its Restricted Roles.
  • Get a Monitor Retrieves a monitor with its Creator, Draft Status and Matching Downtimes. Set Include Downtimes to Yes to add the active downtimes of the monitor.
  • Get a Notebook Gets a notebook along with its Author, Cells and Modified.
  • Get a Synthetics Test Looks up a Synthetics test and its Config, Locations and Monitor ID.
  • Get a Team Retrieves a team with its Handle, Description and Created At.
  • Get a User Loads a user together with their Email, Handle and Disabled.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Apify and Datadog integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Apify and Datadog on WEXTL®

Claim your 3-day trial to build Apify with Datadog integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Apify and Datadog.

How do I connect Apify and Datadog?

Connect your Apify and Datadog accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Apify and Datadog?

Example: when the "Watch Aborted Runs" trigger in Apify fires, WEXTL can "Acknowledge an On-Call Page" in Datadog. Apify has 4 triggers (including Watch Aborted Runs, Watch Failed Runs, and Watch Succeeded Runs). Datadog has 133 actions (including Acknowledge an On-Call Page, Add a Case Comment, and Add a Team Member). Add filters and transforms between steps when you need them.[1]

Can Apify trigger actions in Datadog, and Datadog in Apify?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Apify and Datadog?

No. Apify-to-Datadog automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Apify integrate with Datadog in real time?

Yes. Trigger-based automations start the moment Apify (or Datadog) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Apify + Datadog integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Apify with Datadog?

You can build your Apify + Datadog automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Apify and Datadog integration.

  1. Apify and Datadog integration source code, module specs and credentials implementation.
  2. Our Apify and Datadog integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Apify and Datadog, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Apify integration information
  6. Datadog integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Apify and Datadog integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Apify and Datadog, or get started