BugBug and Pingdom Integration
Connect BugBug and Pingdom 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 Pingdom
Detailed info you need to know about BugBug and Pingdom integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect BugBug to Pingdom
Set up your BugBug and Pingdom integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect BugBug and Pingdom
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow[3]. No coding or API skills required.
STEP 2
Build a workflow
Paste selected BugBug and Pingdom nodes onto the canvas[4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between BugBug and Pingdom. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between BugBug and Pingdom work in WEXTL?
WEXTL exposes actions and triggers for BugBug and Pingdom 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 triggersPingdom 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.
Pingdom modules
- Create a Check Starts monitoring a Host with a chosen Check Type and Name. Add Check Interval (Minutes), Probe Regions or Response Time Threshold (ms) to tune the runs, and Contacts To Alert or Teams To Alert to notify people.
- Create a Maintenance Window Plans a quiet period with a Description, Start and End, during which chosen Uptime Checks or Transaction Checks are not alerted. Repeat, Repeat Every and Repeat Until make it recur.
- Create a Transaction Check Sets up a scripted browser check from a Name and the Steps to run. Add Region, Interval (Minutes) and Alert After Failed Tests to decide where, how often and when it alerts.
- Create an Alerting Contact Adds a person to notify about check problems. Add Email Targets and SMS Targets for where alerts reach them, or turn on Paused to hold notifications.
- Create an Alerting Team Groups people into a team under a Name, built from a list of Members.
- Delete a Check Deletes an uptime check along with all data collected for it. This cannot be undone.
- Delete a Maintenance Occurrence Removes one scheduled slot that belongs to a maintenance window.
- Delete a Maintenance Window Cancels planned downtime by deleting a maintenance window from the account.
- Delete a Transaction Check Deletes a scripted transaction check from the account.
- Delete an Alerting Contact Deletes a person who is notified about check problems.
- Delete an Alerting Team Removes a group of alert recipients from the account.
- Delete Multiple Checks Removes a batch of uptime checks with one request.
- Delete Multiple Maintenance Occurrences Deletes a batch of downtime slots with a single request.
- Delete Multiple Maintenance Windows Removes several maintenance windows at once.
- Get a Check Reads an uptime check with its Hostname, Status and Resolution. Turn on Include Teams to add the alerting teams.
- Get a Maintenance Occurrence Reads one occurrence of a maintenance window, showing its start (From) and end (To).
- Get a Maintenance Window Shows a maintenance window with its Description, Recurrencetype and Repeatevery.
- Get a Performance Summary Reads the response times of a check, one entry per interval of the chosen Resolution. Turn on Include Uptime to add uptime and downtime to each interval.
- Get a Root Cause Analysis Reads one root cause analysis of an outage for a check. Analysis IDs come from List Root Cause Analyses.
- Get a Transaction Check Fetches a transaction check with its Active flag, Interval and timestamps. Turn on Include Extended Tags for tag details.
- Get a Transaction Check Status Report Shows the States of a transaction check for the period from From to To, sorted by Order.
- Get a Transaction Performance Report Reads response Intervals of a transaction check over time. Use Resolution to pick the interval size and Include Uptime to add availability.
- Get an Alerting Contact Reads a notification contact with its Type, Owner and Notification Targets.
- Get an Alerting Team Reads a notification team and shows all of its Members.
- Get an Average Summary Averages the Responsetime and Status of a check over From to To. Use By Country or By Probe to group the result, and Include Uptime to add the uptime totals.
- Get an Hours Of Day Summary Shows the average response for each Hour of the day for a check. Turn on Use Local Time to group by the time zone of the account instead of UTC.
- Get an Outage Summary Lists the up and down periods (States) of a check from From to To. Use Order to start from the newest or the oldest.
- Get the Credits Shows the credit limits of the account, such as Checklimit, Availablechecks and Availablesms.
- Get the Reference Data Shows lookup lists of Regions, Timezones, Countries and Phonecodes.
- List Alerting Contacts Gives every notification contact with its Paused flag, Type and Notification Targets.
- List Alerting Teams Lists every notification team with their Members to see who belongs where.
- List Alerts Retrieves alerts that were sent, filtered by Check IDs, Contact IDs, Status or Sent Via, within From and To.
- List Check Results Pulls raw test results of a check, each with Probeid, Status and Responsetime. Filter by Probe IDs or response time bounds.
- List Checks Reads uptime checks with their Lasttesttime and Lastresponsetime. Use Tags to keep only checks with those tags.
- List Maintenance Occurrences Retrieves occurrences of maintenance windows from From to To, with Maintenance Window to focus on one.
- List Maintenance Windows Lists maintenance windows with their Description, Recurrencetype and Repeatevery. Use Order By to pick the sort field and Order to set the direction.
- List Probes Finds the testing locations with Country, City and Hostname. Turn on Only Active or Include Deleted to filter.
- List Probes Used By a Check Names the Probes that tested a check since From, up to To if given.
- List Root Cause Analyses Reads the root cause analyses for outages of a check between From and To, each with its Timefirsttest and Timeconfirmtest.
- List Transaction Checks Gets scripted checks with their Active flag and Interval, limited to some Tags or one Type.
- List Transaction Status Reports Shows status reports of transaction checks with their States. Turn on Omit Empty to drop checks without data.
- Make an API Call Sends a free-form request to the Pingdom REST API, signed with your saved credential.
- Run a Single Test Runs one immediate test of a Host with a Check Type, from a Probe or Probe Regions. Set Path, Port or HTTP Authentication to aim the request.
- Run a Traceroute Traces the network route to a Host, optionally from a given Probe.
- Update a Check Edits a monitor, from its Host and Check Interval (Minutes) to its Probe Regions and Contacts To Alert.
- Update a Maintenance Occurrence Moves one occurrence to a new Start and End.
- Update a Maintenance Window Edits the Description, Start, End or repeat settings of a maintenance window. Use Clear Fields to blank chosen values.
- Update a Transaction Check Edits a scripted check, covering its Steps, Region, Interval (Minutes) or Severity.
- Update an Alerting Contact Changes the Name of a notification contact, its Email Targets and SMS Targets, or sets Paused.
- Update an Alerting Team Renames a notification team or replaces its Members.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with BugBug and Pingdom integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting BugBug and Pingdom.
References
List of sources used to gather information about the BugBug and Pingdom integration.
- BugBug and Pingdom integration source code, module specs and credentials implementation.
- Our BugBug and Pingdom integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for BugBug and Pingdom, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- BugBug integration information
- Pingdom integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted BugBug and Pingdom integration page documentation. Used sources, the role of AI, and how the team validates the result.

