BugBug and Flowise AI Integration
Demonstration of how apps are integrated in WEXTL workflow builder[4]
Wire the developer tools events of BugBug straight into the ai actions of Flowise AI on the WEXTL® visual canvas. Handoffs between your developer tools and ai tools stay automatic - drag the nodes, map the fields once, and let AI carry the rest. 3-step setup, no code, no engineering ticket.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about BugBug and Flowise AI
Detailed info you need to know about BugBug and Flowise AI integrations in WEXTL. Explore which modules apps support and how you connect them.
BugBug

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

Low-code builder for AI agents and chatbots.[6]
How to connect BugBug to Flowise AI
Set up your BugBug and Flowise AI integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect BugBug and Flowise 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 Flowise 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 Flowise AI. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between BugBug and Flowise AI work in WEXTL?
WEXTL exposes actions and triggers for BugBug and Flowise 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 triggersFlowise 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.
Flowise AI modules
- Check Server Pings the Flowise server and returns its Pong answer. Confirms that the base URL and credential respond.
- Create a Chatflow Creates a chatflow from a Name, optionally with Flow Data, Chatbot Config and a Category. Set Type to Chatflow or Multi Agent, and turn on Deployed or Public to mark it as deployed or public.
- Create a Document Store Creates an empty document store called by your Name. Use Description to note what the store holds.
- Create a Lead Captures contact details from a conversation in a Chatflow, storing Name, Email and Phone for a visitor next to the Chat ID.
- Create a Tool Defines a tool for chatflows to call, from a Name with an optional Schema and Function. Use Color and Icon URL to give it a look.
- Create a Variable Stores a named Variable in Flowise from a Name and Value. Use Type to say how the value is treated.
- Create an Assistant Registers an assistant in Flowise from its Details. Add a Credential ID to link a credential and an Icon URL for its avatar.
- Create Chat Feedback Records a Thumbs Up or Thumbs Down Rating on one Message ID of a Chat ID in a Chatflow, with optional Content text explaining it.
- Delete a Chatflow Removes a chatflow from your instance and reports a Success flag.
- Delete a Document Chunk Removes a single chunk of text from one loader of a Document Store.
- Delete a Document Loader Deletes one loader from a Document Store by Loader ID.
- Delete a Document Store Deletes a whole document store and confirms with Success.
- Delete a Tool Deletes one custom tool from your Flowise account.
- Delete a Variable Removes a stored variable from Flowise.
- Delete an Assistant Deletes an assistant from Flowise. Turn on Also Delete on OpenAI to remove the OpenAI copy too.
- Delete Chat Messages Deletes messages of a chatflow, narrowed by Chat ID, Session ID, Start Date and End Date. Turn on Hard Delete to also clear the session memory and Delete Everything to remove every message when no Chat ID, Session ID or date is given.
- Delete Upsert History Removes upsert history entries from a chatflow, for the Record IDs listed.
- Delete Vector Store Data Clears the vectors held by the store connected to a document store, which works for data upserted with a Record Manager.
- Get a Chatflow Reads a chatflow with its Flow Data, Deployed flag and Chatbot Config.
- Get a Chatflow by API Key Finds the one chatflow that belongs to a Flow API Key, returning its Flow Data and Chatbot Config.
- Get a Document Store Reads a document store together with its Loaders, Where Used and Status.
- Get a Tool Fetches a tool, with its Schema, Color and Description.
- Get an Assistant Fetches one assistant with its Details, Credential, icon source and created and updated dates.
- List Assistants Shows the assistants in Flowise with their Details and Credential, capped by Limit.
- List Chat Feedback Shows feedback left on the messages of a Chatflow. Filter with Chat ID, Start Date and End Date, sort with Order, and bound the result with Limit.
- List Chat Messages Shows messages of one chatflow. Narrow them by Session ID, Chat Type, Start Date and End Date, or by Feedback Type, and use Order for newest or oldest first.
- List Chatflows Returns your Flowise chatflows, flagging which are Deployed and which Is Public, capped by Limit.
- List Document Chunks Pages through the chunks of a loader in a Document Store, each with Page Content and Metadata. Give the Loader ID, then move through the pages with Page and Limit.
- List Document Stores Retrieves document stores along with their Status and Where Used, capped by Limit.
- List Leads Shows the leads captured through a chatflow with their Name, Email and Phone, capped by Limit.
- List Tools Gets custom tools with their Description and Schema, capped by Limit.
- List Upsert History Gets the upsert runs of a Chatflow with each Result and Date. Narrow by Start Date and End Date, reorder with Order, and set the Limit.
- List Variables Gets the variables stored in Flowise, capped by Limit. Turn on Include Values to read their values as well.
- Make an API Call Makes an authorized free-form request to the Flowise AI REST API with your saved credential.
- Query a Vector Store Runs a similarity search with your Query against the vector store behind a document store. You get the matching Docs plus Time Taken.
- Refresh a Document Store Re-runs the loaders of a document store to sync its data with the sources. Use Items to limit the refresh to chosen loaders and read Num Added, Num Updated, Num Deleted and Num Skipped.
- Send a Message to a Chatflow Sends a Message to a chatflow and returns its answer as Text, with the Chat ID and Session ID. Pass History to replay earlier turns, or Override Config for a one-off run.
- Update a Chatflow Renames a chatflow through Name, swaps its Flow Data or Chatbot Config, and flips Deployed and Public. Use Clear Fields to empty the API Key ID, Chatbot Config or API Config.
- Update a Document Chunk Rewrites the Content of one chunk in a loader of a Document Store, and optionally its Metadata.
- Update a Document Store Renames a Document Store with Name and rewrites its Description. Select Description under Clear Fields to empty it.
- Update a Tool Rewrites a tool by its Name, Description, Schema and Function. Use Clear Fields to blank the Description, Color or Icon URL.
- Update a Variable Replaces the Value stored for a variable, and optionally renames it with Name or switches its Type.
- Update an Assistant Edits an assistant by rewriting its Details, Credential ID or Icon URL. Use Clear Fields to remove the avatar.
- Update Chat Feedback Changes the Rating and Content of an existing feedback entry with this Feedback ID.
- Upload Chat Attachments Attaches a File to a chat of a chatflow, saved under a File Name with its extension. Turn on Return Base64 to get the content inline as base64 text, and set the Chat ID of the session.
- Upsert a Document Pushes a File through your chosen Loader, Splitter, Embedding and Vector Store of a document store. Turn on Replace Existing to overwrite earlier versions, or Create New Store to make a store in the same call.
- Upsert Vectors Upserts a File into the vector store of a chatflow. Set Stop Node ID to end the run at a chosen node, and Override Config to adjust settings for it.
- Watch New Chat Feedback Triggers once per new feedback entry on a chatflow, polled periodically. Use Limit to cap how many are read at each check.
- Watch New Chat Messages Runs the workflow for each new message in a chosen chatflow, checking on a schedule. Set Chat Type to Internal or External to filter, and Limit to cap each check.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with BugBug and Flowise 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 Flowise AI.
References
List of sources used to gather information about the BugBug and Flowise AI integration.
- BugBug and Flowise AI integration source code, module specs and credentials implementation.
- Our BugBug and Flowise AI integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for BugBug and Flowise 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
- Flowise AI integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted BugBug and Flowise AI integration page documentation. Used sources, the role of AI, and how the team validates the result.