Currents and Datadog Integration

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

Keep Currents and Datadog matched by integrating their events and actions. When developer tools events happen in Currents, 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 Currents and Datadog

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

  • Currents

    • Developer Tools
    • 1 trigger
    • 23 searches
    • 15 actions

    Track Cypress and Playwright test runs in Currents. Read runs, tests, errors and insights, manage actions and react to run events.[5]

  • Datadog

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

    Monitoring and security platform for cloud applications.[6]

How to connect Currents to Datadog

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

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

WEXTL exposes actions and triggers for Currents 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.

Currents triggersDatadog actions

Currents modules

  • Cancel a Run Cancels a Currents run before it finishes. Output returns the Run ID, Status and Completion State.
  • Cancel a Run by GitHub CI Cancels the Currents run behind a GitHub Actions workflow, located by Repository Owner, Repository and GitHub Workflow Run ID. The reply holds the Currents Run ID and Cancelled.
  • Create a Jira Issue Opens a Jira issue from a run test named by Test ID, using your Jira Installation ID, Jira Project ID and Jira Issue Type ID. Use Custom Fields to fill Jira fields. It reports the Jira Issue Key and Jira Issue URL.
  • Create an Action Adds a rule with a Name that can quarantine, skip or tag the tests selected by a Matcher, using Actions. Set Expires After to end it on a date. The response lists an Action ID plus its Status.
  • Delete a Project Term Deletes a tag from the filter terms of a project. Only the tag Term Type can be deleted, as other types are rejected. You get the term ID, Name and Count.
  • Delete a Run Removes one Currents run from a project and returns its Run ID.
  • Delete an Action Removes one action, a quarantine, skip or tag rule, in a project. Output shows the Action ID and Archived.
  • Disable an Action Switches an action off. Output includes the Action ID, Name, Description and Status.
  • Enable an Action Switches a disabled action back on, reporting its Action ID, Name and Status.
  • Find a Run Searches a project for one run, matching on CI Build ID, Tag, Branch or Author. Add Status as Passed or Failed to restrict it. You receive the Run ID, Status and Completion State.
  • Generate a Test Signature Works out the stable Signature of a test from its Spec File Path and Test Title in a project.
  • Get a Project Fetches one project and returns its Name, Created At and Default Branch.
  • Get a Run Fetches one test run and returns its Status, Completion State and Duration (ms).
  • Get a Test Failure Context Builds structured failure context for a run, and a narrower one when an Instance ID or Test ID is added. Set Detail to Default, Compact or Summary, and turn on Include Flaky for flaky context.
  • Get a Webhook Looks at one webhook in a project, returning its URL, Label and Events.
  • Get Affected Test Executions Pulls the executions of one test, identified by its Test Signature, within a chosen window. Each shows the Run ID, Title, Executed At and Is Flaky. Add Search to filter and Limit to cap the total.
  • Get an Action Fetches one rule of a project, with its Name, Description, Status and Created At.
  • Get an Instance Reads one spec-file instance by Instance ID, returning its Run ID, Spec and Group ID.
  • Get Project Insights Aggregates run and test results for a project over a date window. Choose a Resolution of 1 day or 1 week, and filter by Tag, Branch, Group or Author.
  • Get Test Results Reads the history of one test by Test Signature, with the Framework and Created At of each result. Apply Limit to hold the output to a count, and Tag, Branch, Author or Group to focus it.
  • Link a Jira Issue Links an existing Jira issue with the Jira Issue Key to the test with a Test ID. Add a Comment, or turn on Include Context In Comment to attach context automatically. Output returns the Currents Issue URL.
  • List Action Test Executions Finds the test executions where an action was applied, over a date range. Each row has a Run ID, Spec File, Title and State. Pass Search or Limit to trim the output.
  • List Actions Retrieves every action in a project, showing each Action ID, Name and Status. Filter by Status of Active, Disabled, Archived or Expired, or run a Search on the name.
  • List Affected Tests Shows tests touched by actions in a time window, with their Signature, Title, Spec File and Last Seen. Narrow with Action Type, Status or Search, and order with Sort Direction.
  • List Errors Collects errors of one project over a given period, each with its Error Message, Spec and Count. Use Group By to group by Message or Signature, and add Tag, Branch or Author to narrow it.
  • List Jira Issue Types Returns the issue types in a Jira Project ID of one Jira Installation ID, each with an ID, Name and Description. Add a Search to match by name, and a Limit to restrict the rows.
  • List Jira Projects Looks up Jira projects reachable through a Jira Installation ID, giving the Key, Name and Description of each. A Search matches a name or key.
  • List Project Runs Pulls runs of a project along with Run ID, Status and Created At. Narrow by Tag, Branch, Author or Environment, combine tags with Tag Operator, and refine through Search or Status.
  • List Project Terms Browses the recorded values of one Term Type for a project, such as tags or branches, each with a Name, Count and Updated At. Use Search for a prefix match and Sort Direction to order them.
  • List Projects Gathers the Currents projects, with a Project ID, Name and Default Branch for each. Set a Limit to stop the list at a set number.
  • List Pull Requests Fetches pull requests of a project that have run activity, flagging Has More Runs on each. Include recent runs through Runs Per Pull Request, or restrict by Tag, Branch, Author, Search or Status.
  • List Spec Files Reads spec files for a project, each with its Signature and Spec. Filter through Tag, Branch or Author, and put a ceiling on the total using Limit.
  • List Tests Searches the tests of a project, returning each Title, Signature and Spec. Narrow the output with Search, Tag, Branch or Author.
  • List Webhooks Shows the webhooks set up on a project, giving each Webhook ID, URL, Label and Events. Add a Limit to stop at a given count.
  • Make an API Call Calls the Currents REST API directly with a free-form request under your saved credential.
  • Reset a Run Resets the failed spec files of a run for another attempt. Add Machine IDs to reset only chosen machines. The Run ID and its Status are returned.
  • Update a Webhook Edits the delivery URL, Events, Label or Headers on a project webhook. Use Events to react to Run Start, Finish, Timeout or Cancel.
  • Update an Action Edits a rule of a project: its Name, Description, Actions, Matcher or Expires After. Results echo the Action ID along with Name and Status.
  • Watch Events Instant trigger that fires when a Currents run starts, ends, times out or is cancelled. Output includes the Event, Run ID, Project ID and Status.

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 Currents and Datadog integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Currents and Datadog on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Currents and Datadog.

How do I connect Currents and Datadog?

Connect your Currents 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 Currents and Datadog?

Example: when the "Watch Events" trigger in Currents fires, WEXTL can "Acknowledge an On-Call Page" in Datadog. Currents has 1 trigger (including Watch Events). 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 Currents trigger actions in Datadog, and Datadog in Currents?

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 Currents and Datadog?

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

Does Currents integrate with Datadog in real time?

Yes. Trigger-based automations start the moment Currents (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 Currents + 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 Currents with Datadog?

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

References

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

  1. Currents and Datadog integration source code, module specs and credentials implementation.
  2. Our Currents and Datadog integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Currents 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. Currents 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 Currents and Datadog integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Currents and Datadog, or get started