Connect BugBug integrations

Verified

No-code browser test automation for web apps, connected to WEXTL workflows and AI agents. Replace glue scripts around BugBug with visual workflows. Start from Watch Events, then run Download a Project Backup or Download a Project File.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region
  • BugBug
  • WEXTL
  • Merge.dev
  • 0CodeKit
  • Postman
  • Alchemy
  • Rollbar
  • tl;dv
  • QuickChart
  • Jenkins
  • Hostinger
  • Bunny.net
  • Vercel
  • Piloterr
  • Lansweeper
  • LogMeln
  • Clerk
  • Dropbox
  • Radar
  • Webflow
  • Turbot Pipes

Supported triggers and actions for BugBug integration

Triggers can detect changes in BugBug and run actions that can create, search or modify data inside BugBug automatically[3], exactly how you set them.

  • Watch Events Starts the workflow the moment BugBug sends an event, with its Event Type, Timestamp Ms and Organization.
  • Watch Suite Runs Checks on a schedule for new suite runs and emits each one. Use Suite to watch only that suite and Limit to set how many of the newest runs the first check reads.
  • Watch Test Runs Looks on a schedule for new test runs and emits each one. Use Test to watch only that test and Limit to set how many of the newest runs the first check reads.
  • 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.

How to integrate BugBug in automation workflow?

BugBug in three steps: start with "Watch Events", connect one credential, then add your next step.

How BugBug connects and integrates with WEXTL

Save and approve your credentials once. WEXTL® stores authorization information encrypted and reuses the authentication whenever BugBug app is called in workflows. That allows your developer tools automations to run without your attention, per defined schedule[7]. See the integration guide[6] for a detailed list of fields that BugBug supports.

Full BugBug API documentation

The following table illustrates what fields BugBug integration require during authorization flow inside our workflow builder[4].

Connect BugBug

  • API Token*Text

    ••••••••

Demonstration of BugBug connection step inside WEXTL Workflow Builder[4].
FieldTypeHelp
API TokenRequired
password

In BugBug open your project, go to Integrations, then API Token, and copy the token. The API needs a Business plan.

Connect BugBug to popular apps on WEXTL

Enter a name of the other app you want to sync with BugBug below. Click on selected app to explore integration options with BugBug. If the app you search for is not available in WEXTL yet, you can use HTTP node[10] instead to integrate it directly.

Example automation with BugBug integration

Select Watch Test Runs trigger from BugBug - this will be a starting point in your automation. Whenever event happens in BugBug, workflow will start[7] from Watch Test Runs node.

Search for Create a Test, connect it as the next step of integration sequence. You can use filters between Watch Test Runs and Create a Test, so only important data pass from Watch Test Runs to the next step. WEXTL gives you full control over the process of BugBug automation. All parts of workflow are visible on the canvas[4].

BugBug on WEXTL has 104 modules for creating developer tools automations. Explore BugBug documentation for more.

  • BugBugWatch Test Runs
  • Merge.devPerforms action

OR

  • Merge.devTriggers
  • BugBugCreate a Test
Demonstration of how visual BugBug automation[6] looks in WEXTL.

Frequently asked questions

Common questions about automating BugBug in your workflows.

What triggers does BugBug support?

BugBug has 3 triggers, including "Watch Events", "Watch Suite Runs", and "Watch Test Runs". Triggers are start points of the workflow, and automations may start from them.

What actions can I run in BugBug?

Integration has 101 actions, including "Download a Project Backup", "Download a Project File", and "Download a Suite Run JUnit Report", and more. Refer to our BugBug Documentation for detailed inputs and outputs.

Do I need to write code to build automations?

No. The 103 BugBug modules, like "Download a Project Backup", are forms on the canvas: pick a field, map data from an earlier step. Code is optional[4].

Is the integration secure?

Yes. You fill in the BugBug credential once. WEXTL encrypts it at rest, and only your team can use it.

How does WEXTL integrate with BugBug?

Through the official BugBug API: 103 modules, plus "Make an API Call" for any endpoint they don't cover[3].

Can I use webhooks with BugBug?

Yes. "Watch Events" is instant: BugBug pushes each event, so there is no polling delay.

Why use WEXTL platform for BugBug automation?

WEXTL is an AI-first visual canvas: describe the BugBug flow in plain words and AI wires the nodes[4].

Automate BugBug on WEXTL®

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

Cancel anytime.

References

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

  1. BugBug integration source code, module specs and credentials implementation.
  2. Internal BugBug integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official BugBug vendor API documentation, 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. WEXTL® Apps Library
  6. WEXTL® BugBug App Documentation
  7. WEXTL® Workflow Scheduler
  8. WEXTL® HTTP node documentation

How we write and maintain BugBug app documentation

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