Connect BugBug integrations
VerifiedNo-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
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.
- 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.
- Get the Folder Tree Reads folders of one Kind as a nested tree with Children. Set Parent Folder to start lower in the tree and Search to narrow it.
- Get the Step YAML Schema Fetches the JSON Schema that describes the YAML format of steps.
- List Components Shows shared step blocks. Search them with Query, keep one Folder ID or No Folder, and arrange rows with Ordering.
- List File Extensions Returns the file types present among the uploaded files of a project.
- List Folders Shows folders, optionally only one Kind or only those under a Parent ID. Add Query to match folder names.
- List Groups Gets step groups from your tests. Narrow by Folder ID or No Folder, search with Query, and sort by Ordering.
- List IP Addresses Returns the IP Address values that BugBug runs tests from.
- List Organizations Returns the organizations you belong to. Use Query to find one by name and Ordering to sort.
- List Profiles Returns run profiles, each with a Name and an Is Default flag.
- List Project Backups Shows the backup schedule of a project, with Frequency Days, Retention Days, Next Backup At and the saved Backups.
- List Project Files Browses files uploaded to a project. Filter by Extension, Folder ID or Query, switch on Recursive to include subfolders, and sort with Ordering.
- List Projects Reads the projects available to you with Name and Homepage URL. Use Query to narrow the list by text.
- List Reference Screenshots Retrieves baseline images saved for one Step ID, with Browser Name and Screenshot URL for each.
- List Suite Run Debug Artifacts Gets debugging files kept from a suite run, with Kind, File Extension and Content Type.
- List Suite Runs Finds suite executions. Narrow by Suite ID, Status, Tags, Started After or Started Before, and sort with Ordering.
- List Suites Collects suites with Auto Retry and other run options. Add Latest Run to see the newest result, or filter by Tags and Query.
- List Tags Browses labels with Color, Tests Count and Suites Count. Restrict them to one Project ID.
- List Test Run Debug Artifacts Gets debugging files kept from a test run, each with its Kind and File Extension.
- List Test Runs Pulls single-test executions. Select by Test ID, Status, Tags, Started After or Started Before, and order with Ordering.
- List Tests Reads tests. Filter by Folder ID, No Folder, Tags or Query, add Latest Run for the newest result, and sort with Ordering.
- List Variables Reads project variables with Key, Type and whether each Is Built In.
- 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.
- Import a Test Brings a test in from a File. Use Conflict Mode for a test with the same slug, Folder to import into a folder and On Missing Component for a missing component. Returns Status, Entity Ids and any Conflicts.
- Insert a Component into a Test Adds a shared component to a test. Set At Index to choose the slot it lands in.
- Make an API Call Sends a free-form request to the BugBug REST API, signed with your saved credential.
- Move a Group in a Test Repositions a step group inside a test, using At Index as its new place.
- Move a Step in a Test Moves a step in a test. Use Group ID to move it into another group and At Index to set its new position.
- Move Project Files in Bulk Moves several uploaded Files into another Folder at once and returns how many were Moved.
- Remove a Component from a Test Removes a shared component from a test and returns the test with its Groups.
- Replace Suite Run Tags Swaps the labels on a suite run for those from Tag Names or Tags. Turn on Remove All Tags to clear them.
- Replace Suite Tags Overwrites the labels of a suite using Tag Names or Tags. Turn on Remove All Tags to empty the list.
- Replace Test Run Tags Sets new labels on a test run from Tag Names or Tags, or clears them with Remove All Tags.
- Replace Test Tags Gives a test a new set of labels, from Tag Names or Tags. Turn on Remove All Tags to strip them.
- Resolve a Visual Regression Resolves a screenshot difference with a Resolution, where Set New Reference accepts the observed screenshot as the baseline. Use Test Run or Step Run ID to say which one to resolve.
- Run a Project Import Performs the import prepared by Validate a Project Import, using its Upload ID. The result gives the Project ID and Status.
- Run a Suite Starts a suite now. Choose a Run Profile, pass Variables or add Tag Names. Returns the run ID, Status and Finished Tests.
- Run a Test Launches one test right away. Choose a Run Profile, pass Variables or add Tag Names. Returns the run ID, Status and Finished Steps.
- Stop a Suite Run Aborts a suite run in progress and returns its Status and Duration.
- Stop a Test Run Aborts a test run in progress and returns its Status and Finished Steps.
- Update a Component Changes the Name, Is Active state or Folder ID of a shared component. Use Clear Fields to empty the Name or move it to the root.
- Update a Folder Renames a folder or moves it under another Parent ID.
- Update a Group Changes the Name, Is Active, Is Component or Folder ID of a step group.
- Update a Project File Renames an uploaded file or moves it to another Folder ID.
- Update a Step Edits an action: its Group, Position, Name, Active state or Step Fields (JSON).
- Update a Suite Edits a suite: Name, Notes, Run Profile ID, the Tests it contains and options such as Run In Parallel or Auto Retry.
- Update a Tag Changes the Name or Color of a label.
- Update a Test Edits a test: Name, Notes, Screen Size Type, Folder ID, Tag Names or Tags. Use Clear Fields to empty chosen values.
- Update a Variable Edits the Value, Type, Is Secret flag or Description of the variable with that Variable Key.
- Update Suite Run Notes Writes the Notes of a suite run. Use Clear Fields to remove them.
- Update Test Run Notes Replaces the Notes on a test run. Use Clear Fields to remove earlier notes.
- Upload a Project File Sends a File into a project. Use Name to rename it in BugBug and Folder to put it in a folder. Returns its Extension, Size and URL.
- Validate a Project Import Uploads a project File for checking and returns an Upload ID with a Summary. Follow with Run a Project Import.
How to integrate BugBug in automation workflow?
BugBug in three steps: start with "Watch Events", connect one credential, then add your next step.
STEP 1
Select BugBug in workflow
Add the "Watch Events" trigger from BugBug to the canvas[4].
STEP 2
Connect BugBug
Fill in the BugBug credential once. All 103 BugBug modules use it[3].
STEP 3
Build a workflow
Add "Download a Project Backup" or "Download a Project File" after it, then connect any app[5] or the HTTP node.
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 documentationThe following table illustrates what fields BugBug integration require during authorization flow inside our workflow builder[4].
Connect BugBug
API Token*Text
••••••••
| Field | Type | Help |
|---|---|---|
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
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].
References
List of sources used to gather information about the BugBug integration.
- BugBug integration source code, module specs and credentials implementation.
- Internal BugBug integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official BugBug vendor API documentation, 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.
- WEXTL® Apps Library
- WEXTL® BugBug App Documentation
- WEXTL® Workflow Scheduler
- 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.





















