BugBug and Rollbar Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Build developer tools workflows between BugBug and Rollbar 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 Rollbar

Detailed info you need to know about BugBug and Rollbar integrations in WEXTL. Explore which modules apps support and how you connect them.

  • BugBug

    • Developer Tools
    • 3 triggers
    • 51 searches
    • 50 actions

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

  • Rollbar

    • Developer Tools
    • 3 triggers
    • 43 searches
    • 39 actions

    Error monitoring that tracks, groups and helps fix errors in your code.[6]

How to connect BugBug to Rollbar

Set up your BugBug and Rollbar integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between BugBug and Rollbar work in WEXTL?

WEXTL exposes actions and triggers for BugBug and Rollbar 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 triggersRollbar 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.

Rollbar modules

  • Add a User to a Team Puts a Rollbar user into a team so they get the access that team has.
  • Assign a Team to a Project Gives a whole team access to a Rollbar project. Listing projects here takes an account access token.
  • Cancel an Invitation Withdraws a team invitation that is still pending.
  • Cancel an RQL Job Stops a running RQL query job. Account tokens can add a Project ID to say which project it belongs to.
  • Check a Team on a Project Finds out whether a team currently has access to a project and returns the Assigned flag.
  • Check a User in a Team Tests whether a user belongs to a team and answers with the Assigned flag.
  • Configure a PagerDuty Integration Connects a project to PagerDuty with the integration key from Service Key and switches the integration on or off.
  • Configure a Slack Integration Sends project notifications to a Slack Channel through the Service Account ID taken from the Rollbar Slack settings. Turn on Show Message Buttons for action buttons in messages.
  • Configure a Webhook Integration Sets the default Webhook URL that Rollbar posts project notifications to, replacing the one the project had.
  • Configure an Email Integration Switches email notifications on or off for a project. Set Include Request Parameters to Yes to add request data to the emails.
  • Create a Project Begins a Rollbar project from a Name. Set Copy Settings From to reuse the configuration of an existing project.
  • Create a Project Access Token Issues a token for a project under a Name. Use Scopes to decide what it may do and Rate Limit Calls to cap its calls per window.
  • Create a Service Link Adds a link template to your project that points from Rollbar to another service, built from a Name and a Template with placeholders.
  • Create a Team Adds a team with a Name and an Access Level to the account.
  • Create an Item Reports an error to Rollbar as a new item in a named Environment, using a Body (JSON) with a message, trace or crash report. Add Level, Title, Platform and Code Version for further detail.
  • Create an Item Comment Adds a Comment to the discussion thread of an error item in a Project, so teammates see your note.
  • Create an RQL Job Runs a Rollbar Query Language statement as a background job. Turn on Force Refresh to rerun it even when an identical recent result exists.
  • Create Notification Rules Adds up to 50 rules to a notification Channel at once. Fill Rules (JSON) with an array in which each rule has a trigger, a status and a config.
  • Delete a Notification Rule Removes a single rule from the rules of a notification channel.
  • Delete a Project Removes a whole project. This cannot be undone.
  • Delete a Project Access Token Revokes one access token of a project, using its public ID or the token value itself.
  • Delete a Service Link Deletes a link template from a project.
  • Delete a Session Replay Deletes a recorded replay of a user session in one environment.
  • Delete a Team Deletes the chosen team in Rollbar.
  • Delete an Occurrence Deletes one occurrence of an error, which cannot be undone.
  • Get a Code Version Shows how one code version fared in an environment, with its counts of New items and Resolved items.
  • Get a Deploy Looks up one deploy by Deploy ID with its Environment, Revision, Comment, Start time and Finish time.
  • Get a Notification Rule Reads a single rule from a notification channel with its Trigger, Status, Config and Filters.
  • Get a Person Deletion Status Follows up on a privacy deletion request with the Job ID that Request Person Deletion returned.
  • Get a Project Reads a project with its Name, Status and creation and modification dates.
  • Get a Service Link Reads one link template with its Name and Template.
  • Get a Session Replay Pulls a recorded session from an environment and returns the Events of the chosen Replay ID.
  • Get a Team Reads a team with its Name and Access level.
  • Get a User Reads one account user with their Username and Email.
  • Get Activated Item Counts Reports how many items became active per time bucket, as rows with a Timestamp and a Count. Use Bucket Size and Buckets to shape the series and Environments to filter it.
  • Get an Invitation Checks a team invitation by Invitation ID. The answer includes the To email address, the Status and when it was redeemed.
  • Get an Item Loads an error item by its numeric Item ID, with its Title, Counter, Framework and first and last occurrence.
  • Get an Item by Counter or UUID Finds an item from the Counter seen in the Rollbar interface, or from the Occurrence UUID returned when an occurrence was created. Supply one of them.
  • Get an Occurrence Loads a single error event by Occurrence ID, with its Timestamp, Version and the full Data payload.
  • Get an RQL Job Checks the Status and Query string of an RQL job by Job ID. Add Expand with result to include the output as well.
  • Get Item Metrics Fetches metrics for several error items at once. Give Item Counters as the numbers Rollbar shows after a hash sign, separated by commas.
  • Get Occurrence Counts Counts occurrences per time bucket. Narrow the numbers with Minimum Level, Maximum Level, Environments or one Item ID.
  • Get Occurrence Metrics Queries occurrence metrics for the period from Start Time to End Time. Use Granularity and Time Zone to control how rows are grouped.
  • Get Resolution Time Metrics Measures how long items take to be resolved over a period that begins at Start Time. Use Function to pick the statistic and Project IDs to limit the projects.
  • Get RQL Job Results Downloads the Result rows of a finished RQL job. Use Expand to fold the job details in too.
  • Get Top Active Items Ranks the busiest items of the last Hours, each with its Counts. Use Sort for another order and Environments to filter.
  • Invite a User to a Team Emails an invitation to join a team to one Email address.
  • List Deploys Shows deployments with their Revision, Environment and timestamps, up to Limit.
  • List Environments Lists the environments a project has reported from, each with its Visible flag.
  • List Item Events Walks through the activity on an item, such as comments and status changes. Use Event Type to see one kind of event only.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with BugBug and Rollbar integrations. Pick any from the list below if the current combination isn't the one you need.

Automate BugBug and Rollbar on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting BugBug and Rollbar.

How do I connect BugBug and Rollbar?

Connect your BugBug and Rollbar accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between BugBug and Rollbar?

Example: when the "Watch Events" trigger in BugBug fires, WEXTL can "Add a User to a Team" in Rollbar. BugBug has 3 triggers (including Watch Events, Watch Suite Runs, and Watch Test Runs). Rollbar has 82 actions (including Add a User to a Team, Assign a Team to a Project, and Cancel an Invitation). Add filters and transforms between steps when you need them.[1]

Can BugBug trigger actions in Rollbar, and Rollbar in BugBug?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate BugBug and Rollbar?

No. BugBug-to-Rollbar automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does BugBug integrate with Rollbar in real time?

Yes. Trigger-based automations start the moment BugBug (or Rollbar) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a BugBug + Rollbar integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect BugBug with Rollbar?

You can build your BugBug + Rollbar automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

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

  1. BugBug and Rollbar integration source code, module specs and credentials implementation.
  2. Our BugBug and Rollbar integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for BugBug and Rollbar, 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. BugBug integration information
  6. Rollbar integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

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

Explore BugBug and Rollbar, or get started