BugBug and Roe AI Integration
Automate the handoff between BugBug and Roe AI - your developer tools events flow into ai actions on a visual canvas your team can read. Set up the workflow once with 3 simple steps in the WEXTL® builder, let AI take smart decisions between apps, and never write a line of glue code again.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
How to connect BugBug to Roe AI
Set up your BugBug and Roe AI integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect BugBug and Roe AI
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 Roe AI 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 Roe AI. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between BugBug and Roe AI work in WEXTL?
WEXTL exposes actions and triggers for BugBug and Roe AI 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 triggersRoe AI 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.
Roe AI modules
- Get a Job Result Fetches the Response of an agent job. Pass the Agent Job ID of a job started with Run an Agent (Async).
- Get a Job Status Shows the Status and Timestamp of an agent job, identified by its Agent Job ID.
- Get a Query Result Fetches the Results for a worksheet query by Worksheet Query ID, with the Query Task ID that produced them.
- Get a Query Status Gets the Status of the query behind a Worksheet Query ID, plus its Query Task ID.
- Make an API Call Makes an authorized free-form request to the Roe AI REST API with your saved credential.
- Run a Query (Async) Starts the queries of Query without waiting for them to finish. Output includes a Job ID.
- Run a Query (Sync) Runs queries in Roe AI and waits for the Response. Use Query to send several at once by separating them with semicolons.
- Run an Agent (Async) Starts a Roe AI agent in the background and hands you a Job ID. Add the data for the agent to Input, then follow the job with Get a Job Status and Get a Job Result.
- Run an Agent (Sync) Runs a Roe AI agent and waits for it to finish, so the Response arrives in the same step. Use Input to pass the key names and data set in the agent settings of the Roe AI dashboard.
- Upload a File Stores a File in a Roe AI dataset and returns the saved item with its ID, Dataset, Name, Size, Creator and Created At. Set Organization ID to upload to an organization, or Metadata to attach JSON details.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with BugBug and Roe AI 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 Roe AI.
References
List of sources used to gather information about the BugBug and Roe AI integration.
- BugBug and Roe AI integration source code, module specs and credentials implementation.
- Our BugBug and Roe AI integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for BugBug and Roe AI, 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
- Roe AI integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted BugBug and Roe AI integration page documentation. Used sources, the role of AI, and how the team validates the result.

