BugBug and Merge.dev Integration

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

Build developer tools workflows between BugBug and Merge.dev 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 Merge.dev

Detailed info you need to know about BugBug and Merge.dev 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]

  • Merge.dev

    • Developer Tools
    • 15 triggers
    • 62 searches
    • 18 actions

    Unified API platform that connects HRIS, ATS, and CRM systems through a single integration.[6]

How to connect BugBug to Merge.dev

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

How does the integration between BugBug and Merge.dev work in WEXTL?

WEXTL exposes actions and triggers for BugBug and Merge.dev 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 triggersMerge.dev 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.

Merge.dev modules

  • Create a Contact Adds a person to the CRM, starting from their First Name. Attach a Last Name and an Account, plus Phone Numbers or Email Addresses, each with a type such as Mobile or Work.
  • Create a Lead Adds a lead to the CRM with a Lead Source, Title and Company, plus First Name and Last Name. Use Converted Contact and Converted Account to link a lead that already became a contact and account.
  • Create a Note Writes note Content into the CRM and attaches it to an Account ID, a Contact ID or an Opportunity ID, one at a time. Give an Owner ID to assign the note.
  • Create a Task Opens a CRM task with a Subject and Content, an Owner, a Due Date and a Status. Link it to an Account, an Opportunity or a Contact.
  • Create a Time Off Request Records a time off request for an Employee, with an Approver, a Start Time and End Time. Use Time-Off Units to count the Amount in hours or days, and add an Employee Note for the reason.
  • Create a Timesheet Entry Books hours against an Employee, with Hours Worked and a Start Time in ISO 8601.
  • Create an Account Adds a CRM account with an Account Name and a Number of Employees. Assign an Owner ID, and give the account one or more postal addresses through Addresses.
  • Create an Engagement Logs an engagement in the CRM against an Owner, an Account or a Subject, with at least one of the three supplied. It can also carry an Engagement Type and related Contacts.
  • Create an Opportunity Adds an opportunity under an Opportunity Name, with an Amount and a Status of OPEN, WON or LOST. Tie it to an Account ID, an Owner ID and a Stage ID. Output includes the new Opportunity ID.
  • Get a Bank Info Record by ID Reads one bank account saved for an employee, with its Bank name, Account type, Account number and Routing number.
  • Get a Benefit by ID Loads one benefit with its Provider name, Employee contribution and Company contribution, plus Start date and End date.
  • Get a Company by ID Fetches one company from the HRIS with its Legal name, Display name and Eins.
  • Get a Contact by ID Pulls a CRM contact by ID with their First name, Last name, Email addresses and Phone Numbers. Use Expand with a value like account,owner to return those relations in full.
  • Get a Dependent by ID Reads a dependent of an employee: Relationship, Date of birth, Gender and Is student. Turn on Include Sensitive Fields to add values such as social security numbers.
  • Get a Group by ID Reads a group, showing its Parent group, Type and whether Is commonly used as team is set. Use Show Enum Origins to return enum values as the provider names them.
  • Get a Lead by ID Pulls one CRM lead, including its Company and Lead source.
  • Get a Location by ID Reads one location with its Street 1, City, State, Zip code, Country and Location type.
  • Get a Note by ID Loads a note with its Content and the Contact, Account and Opportunity it is linked to.
  • Get a Pay Group by ID Reads one pay group and returns its Pay group name from the HRIS.
  • Get a Payroll Run by ID Reads one payroll run with its Run state, Run type, Start date, End date and Check date.
  • Get a Stage by ID Reads one pipeline stage from the CRM and returns its Name.
  • Get a Task by ID Reads a task, listing the Subject, Due date, Completed date and Status.
  • Get a Time Off Balance by ID Reads a time off balance with the Balance, Used and Policy type for one employee.
  • Get a Time Off Request by ID Loads one time off request with its Employee, Approver, Status, Request type and Amount. Use Expand Relations with a value like employee,approver to return those people in full.
  • Get a User by ID Reads one CRM user, with a Name, an Email and an Is active flag.
  • Get Account Metadata Describes the payload of an account create call in the CRM, giving a Request schema and a Status.
  • Get Account Patch Metadata Describes what updating one existing account will accept, as a Request schema.
  • Get Accounts Lists CRM accounts, showing Name, Industry, Website and Number of employees. Search by Name or Owner ID.
  • Get an Account by ID Pulls one CRM account with its Name, Industry, Website and Number of employees.
  • Get an Employee by ID Reads one employee with an Employee number, Preferred name, Username and Work email. Turn on Include Sensitive Fields for sensitive values, or use Show Enum Origins to get the provider enum values.
  • Get an Employee Payroll Run by ID Reads what one employee received in a payroll run: Gross pay, Net pay, Earnings, Deductions and Taxes.
  • Get an Employer Benefit by ID Reads a benefit offered by the employer, including its Benefit plan type, Name and Deduction code.
  • Get an Employment by ID Reads one employment record, showing the Job title, Pay rate, Pay frequency, Pay currency and Effective date. Use Show Enum Origins to get the original third-party values of enum fields.
  • Get an Engagement by ID Returns an engagement from the CRM, showing the Direction, Engagement type and Start time. Turn on Include Remote Fields to add fields not mapped to the common model.
  • Get an Engagement Type by ID Fetches one engagement type, giving its Name and Activity type.
  • Get an Opportunity by ID Reads an opportunity from the CRM, covering its Amount, Stage, Status and Close date.
  • Get Bank Info Records Lists saved bank accounts with Bank name, Account type, Routing number and Employee. Restrict by Employee ID, Account Type (SAVINGS or CHECKING) or Bank Name, and sort with Order By.
  • Get Benefits Lists benefits with the Provider name, Benefit plan type, Employee contribution and Company contribution of each. Use Employee ID to return the benefits of one employee.
  • Get Companies Lists companies with their Legal name, Display name and Eins. Turn on Include Deleted Data to also return companies deleted in the third-party platform.
  • Get Contacts Lists CRM contacts with First name, Last name, Account and Owner. Search by Account ID, Email Addresses or Phone Numbers.
  • Get Contacts Metadata Lists what a create call for a CRM contact will accept, in a Request schema alongside a Status and Has conditional params.
  • Get CRM Contact Metadata Shows the shape of a valid new CRM contact as a Request schema, with Has required linked account params.
  • Get Dependents Lists dependents with Relationship, Date of birth and Is student. Use Employee ID to see the dependents of one employee.
  • Get Employee Creation Metadata Fetches the fields a new HRIS employee may carry, as a Request schema with Has conditional params.
  • Get Employees Lists employees with filters such as Job Title, Employment Status, Manager ID, Team ID or Work Email. Each has an Employee number, names and a Work email.
  • Get Employer Benefits Lists the benefits an employer offers, each with a Benefit plan type, Name and Deduction code.
  • Get Employments Lists employment records with Job title, Pay rate, Pay period and Employment type. Use Order By to sort by effective date, and Employee to see one person.
  • Get Engagement Creation Metadata Pulls the Request schema behind engagement creation, together with Remote field classes from the linked CRM.
  • Get Engagements Lists CRM engagements with Subject, Direction and Engagement type, plus when each began and ended. Narrow by when they began with Started After and Started Before.
  • Get Groups Lists groups from the HRIS, returning a Name, a Type, a Parent group and an Is commonly used as team flag per group. Narrow them through Group Types or Group Names.

Explore alternative integrations

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

Automate BugBug and Merge.dev on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting BugBug and Merge.dev.

How do I connect BugBug and Merge.dev?

Connect your BugBug and Merge.dev 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 Merge.dev?

Example: when the "Watch Events" trigger in BugBug fires, WEXTL can "Create a Contact" in Merge.dev. BugBug has 3 triggers (including Watch Events, Watch Suite Runs, and Watch Test Runs). Merge.dev has 80 actions (including Create a Contact, Create a Lead, and Create a Note). Add filters and transforms between steps when you need them.[1]

Can BugBug trigger actions in Merge.dev, and Merge.dev 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 Merge.dev?

No. BugBug-to-Merge.dev 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 Merge.dev in real time?

Yes. Trigger-based automations start the moment BugBug (or Merge.dev) 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 + Merge.dev 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 Merge.dev?

You can build your BugBug + Merge.dev 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 Merge.dev integration.

  1. BugBug and Merge.dev integration source code, module specs and credentials implementation.
  2. Our BugBug and Merge.dev integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for BugBug and Merge.dev, 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. Merge.dev 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 Merge.dev integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore BugBug and Merge.dev, or get started