BugBug and Postman Integration
Build developer tools workflows between BugBug and Postman on a visual canvas. Set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about BugBug and Postman
Detailed info you need to know about BugBug and Postman integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect BugBug to Postman
Set up your BugBug and Postman integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect BugBug and Postman
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 Postman 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 Postman. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between BugBug and Postman work in WEXTL?
WEXTL exposes actions and triggers for BugBug and Postman 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 triggersPostman 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.
Postman modules
- Add a Collection to an API Attaches collection content to an API from an Operation Type and Data (JSON). It returns the stored Data and Operation Type.
- Create a Collection Starts a collection in a workspace. Prefill it with Items (JSON), Variables, Auth (JSON) and Events (JSON), or add a Description. It returns the Id, Name and Uid.
- Create a Collection Comment Leaves a Comment on a whole collection. Use Thread ID to reply in an existing thread, and Tagged Users to mention people by User ID or Username.
- Create a Collection Folder Makes a folder in a collection from a Name. Use Parent Folder ID to nest it inside another folder.
- Create a Collection Pull Request Opens a pull request that proposes merging a forked collection into a Destination. Assign Reviewers, give it a Title and add a Description to explain the change.
- Create a Collection Request Saves an API request in a collection with its Method, URL, Headers, Query Parameters and body. Use Folder ID to file it in a folder, or add Auth (JSON) and Events (JSON).
- Create a Collection Response Stores an example reply under the request with the Request ID. Add Status Text, Headers and a Body, and use Body Language for the syntax of the Body.
- Create a Collection Webhook Sets up a webhook for a collection under a Name. Add an Environment to run the collection with.
- Create a Folder Comment Posts a Comment on one folder of a collection, using the Folder ID. Use Thread ID to answer an existing thread and Tagged Users to mention people.
- Create a Mock Response Defines a server response on a mock server from a Name. Use Headers, Language and Body to shape what the mock sends back.
- Create a Mock Server Spins up a mock server from a collection in a workspace. Pick an Environment, give it a Name, and set Private to restrict callers. It returns the Mock Url.
- Create a Monitor Schedules a collection run on a Cron expression in a Time Zone. Turn on Active to run it, and tune Retry Attempts, Notification Limit, Email on Error and Email on Failure.
- Create a Request Comment Writes a Comment on one request of a collection, using its Request ID. Reply in a thread with Thread ID or mention people through Tagged Users.
- Create a Response Comment Adds a Comment to a saved example, using its Response ID. Set Thread ID to continue a thread, or Tagged Users to mention teammates.
- Create a Spec Writes an API spec into a workspace from a Name, a Type and its Files. Each file carries a Path and its Content.
- Create a Spec File Puts another file into a spec at the Path of your choice, along with its Content. The new file returns with its Id, Created At and Created By.
- Create a Spec Version Tag Marks the current state of a spec with a Name, giving you a version to return to later.
- Create a Workspace Opens a workspace from a Name and a Type. Add context with Description and About, and assign it to a team through Team.
- Create a Workspace Update Publishes a post to a workspace with a Topic, a Description and a Category. Add Related Resources, each with a Resource and Resource ID, to link what it covers.
- Create an API Registers an API in a workspace from a Name, with an optional Summary and Description. The API is returned with those three values.
- Create an API Version Releases a version of an API from a Name. Link Schema IDs and Collection IDs to it, and add Release Notes to explain what changed.
- Create an Environment Builds an environment in a workspace from a Name. Add Variables, each with a Key, Value, Type, Enabled flag and Description, to start with values.
- Delete a Collection Deletes a collection, the saved set of folders and requests.
- Delete a Collection Comment Deletes the collection comment that carries a Comment ID.
- Delete a Collection Folder Removes the folder with a given Folder ID from its collection.
- Delete a Collection Request Deletes a single request from its collection, using Request ID.
- Delete a Collection Response Removes a saved example response from its request, using Response ID.
- Delete a Folder Comment Removes a folder comment by its Comment ID, from the Folder ID folder.
- Delete a Mock Response Removes a mock server response by Server Response ID.
- Delete a Mock Server Removes a mock server, the fake API backed by a collection.
- Delete a Monitor Removes a scheduled monitor from your Postman account.
- Delete a Request Comment Removes a request comment by Comment ID, under the request with the Request ID.
- Delete a Response Comment Removes a comment by Comment ID from the saved response with the Response ID.
- Delete a Spec Deletes an API spec from your workspace.
- Delete a Spec File Deletes one file from an API spec by File Path.
- Delete a Workspace Deletes a workspace once Confirm is turned on.
- Delete a Workspace Update Removes an update post by its Update ID from a workspace.
- Delete an API Deletes an API definition from Postman.
- Delete an API Version Deletes the release that matches a Version ID from the version list of an API.
- Delete an Environment Deletes a named environment, the variable set of a workspace.
- Duplicate a Collection Copies a collection into a target Workspace. Use Suffix to tell the copy apart from the original.
- Fork a Collection Forks a collection into a target Workspace. Use Label to name the fork.
- Fork an Environment Makes a fork of an environment in a Workspace. Use Fork Name to title the fork.
- Generate a Collection from a Spec Builds a collection out of an API spec under a Name. Use Folder Strategy, Indent Character and Include Deprecated to shape it. It returns a Task Id and Url for following the run.
- Generate a Spec from a Collection Writes an API spec out of a collection from a Name, using Type and Format to set the spec style. Follow the run with its Task Id and Url.
- Get a Collection Downloads a whole collection: Info, Item, Auth, Event and Variable. Use Model to switch the response format and Access Key to read a shared collection.
- Get a Collection Folder Pulls one folder by Folder ID, returning its Name, Description and Owner. Turn on Populate to include what is inside.
- Get a Collection Merge Status Polls a merge task by Task ID and reports its Status.
- Get a Collection Request Looks up one request by Request ID, returning its Name, Owner and Last Revision. Turn on Populate for more detail.
- Get a Collection Response Fetches the saved example response behind a Response ID, with the Request it belongs to, plus its Name and Owner.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with BugBug and Postman 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 Postman.
References
List of sources used to gather information about the BugBug and Postman integration.
- BugBug and Postman integration source code, module specs and credentials implementation.
- Our BugBug and Postman integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for BugBug and Postman, 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
- Postman integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted BugBug and Postman integration page documentation. Used sources, the role of AI, and how the team validates the result.

