BugBug and Datadog Integration

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

Connect BugBug and Datadog to automate developer tools workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.

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

Learn about BugBug and Datadog

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

  • BugBug

    • Developer Tools
    • 3 triggers
    • 51 searches
    • 50 actions

    No-code browser test automation for web apps.[5]

  • Datadog

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

    Monitoring and security platform for cloud applications.[6]

How to connect BugBug to Datadog

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

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

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

BugBug triggersDatadog actions

BugBug modules

  • Check a Project Import Tests a project export File against BugBug before importing it. Reports whether it is Valid along with a Summary of its content.
  • Check a Test Import Looks over a test File and reports if it is Valid, with a Summary, without creating anything.
  • Create a Component Adds a reusable block of steps that tests can share. Give it a Name and switch Is Active to run it.
  • Create a Folder Makes a folder of a given Kind for organizing items. Set Parent ID to nest it inside another folder.
  • Create a Group Adds a group of steps to a test. Use At Index to place it, Is Component to make it a reusable component and Folder ID to file that component in a folder.
  • Create a Step Adds one action to a group, with a Type and optional Position or Name. Fill Step Fields (JSON) with the parameters of that action.
  • Create a Suite Creates a suite of tests that run together under a Run Profile ID. Set Run In Parallel to run its tests side by side, Auto Retry to retry failed tests and Auto Add New Tests to include every new test in it.
  • Create a Tag Creates a tag, using Color for its hex value and Project ID to place it in a specific project rather than the one tied to the token.
  • Create a Test Makes a browser test and keeps its Notes. Use Screen Size Type to run it on desktop, mobile or a custom screen, Folder ID to file it and Tag Names to tag it.
  • Create a Variable Defines a variable by Key and Type, with an optional Value. Turn on Is Secret to hide the value in BugBug.
  • Delete a Folder Removes a folder. Turn on Force to delete it even when it has content.
  • Delete a Group Deletes a group of steps from a test.
  • Delete a Project File Removes one uploaded file from a BugBug project.
  • Delete a Reference Screenshot Deletes a stored baseline image that visual comparison relies on.
  • Delete a Step Removes one action from a test.
  • Delete a Suite Deletes a suite of tests from your project.
  • Delete a Tag Removes a label from your project.
  • Delete a Test Removes a test from your BugBug project.
  • Delete Project Files in Bulk Deletes many project Files in one call and reports how many Steps Affected used them.
  • Detach a Component from a Test Turns a component used by a test into ordinary steps of that test, so edits no longer touch the shared block.
  • Download a Project Backup Downloads one saved Backup of a project as a file, with its File Name and Content Type.
  • Download a Project File Fetches the content of an uploaded project file as a File with its File Name and Content Type.
  • Download a Suite Run JUnit Report Gets the JUnit XML report of a finished suite run for use in CI tools.
  • Download a Test Run JUnit Report Gets the JUnit XML report of a single test run, which CI tools can read.
  • Download Test Run Logs Downloads the log file of one test run with its File Name and Content Type.
  • Export a Project as ZIP Packs the whole BugBug project into a ZIP file, which you can import elsewhere.
  • Export a Test as YAML Returns the full definition of a test, written as YAML text.
  • Export a Test as ZIP Packs a test with what it needs into a ZIP file for import elsewhere, with step passwords removed.
  • Get a Folder Reads one folder with its Name, Kind, Depth and Parent ID.
  • Get a Group Reads a step group with its Name, Is Component flag and Folder ID.
  • Get a Project File Pulls the record of an uploaded file with Extension, Size and URL, but not its bytes.
  • Get a Reference Screenshot Reads one baseline image record with its Screenshot URL and Browser Name.
  • Get a Run Profile Shows a run profile with its Name and whether it Is Default for new runs.
  • Get a Step Reads one step with its Type, Name and Group ID.
  • Get a Step Run Looks up how one step went in a test run, with its Status and Test Run ID.
  • Get a Suite Reads a suite, including Auto Retry, Before After All Enabled and Auto Add New Tests.
  • Get a Suite Run Loads a suite run with its Duration, Ended time and Error Code.
  • Get a Tag Returns one tag with its Color and Name. Pass a Project ID when the tag belongs to another project.
  • Get a Test Fetches a test with its Name, Tags and the Groups of steps.
  • Get a Test Run Pulls a test run with the Browser Name, Browser Version and Duration.
  • Get a Test Run Debug Artifact Retrieves one debugging file of a test run, by its Artifact Kind, with its File and Content Type.
  • Get a Variable Reads one variable by Variable Key, with its Value, Type and whether it Is Secret.
  • Get Component Usage Finds which tests use a component, returned as Usage and the Tests Ids.
  • Get Project File Usage Finds where an uploaded file is used and reports the Steps Count plus the Tests that reference it.
  • Get Project Settings Shows the defaults of your project, including Browser Width, Browser Height, Browser Language and the Initial Run Profile ID.
  • Get Suite Run Screenshots Pulls the screenshots taken during a suite run, grouped as Tests Runs.
  • Get Suite Run Status Checks how far a suite run has come, showing Status and Finished Tests.
  • Get Test Run Screenshots Pulls the screenshots taken during a test run, grouped as Steps Runs.
  • Get Test Run Status Checks how far a test run has come, showing Status and Finished Steps.
  • Get the API Status Checks that BugBug is reachable and says whether you are Authenticated.

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

Automate BugBug and Datadog on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting BugBug and Datadog.

How do I connect BugBug and Datadog?

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

Example: when the "Watch Events" trigger in BugBug fires, WEXTL can "Acknowledge an On-Call Page" in Datadog. BugBug has 3 triggers (including Watch Events, Watch Suite Runs, and Watch Test 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 BugBug trigger actions in Datadog, and Datadog in BugBug?

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

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

Does BugBug integrate with Datadog in real time?

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

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

References

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

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

Explore BugBug and Datadog, or get started