AssemblyAI and BugBug Integration

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

Keep AssemblyAI and BugBug matched by integrating their events and actions. When developer tools events happen in AssemblyAI, update the BugBug automatically - without any line of code in visual workflow builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about AssemblyAI and BugBug

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

  • AssemblyAI

    • Developer Tools
    • 8 searches
    • 6 actions

    Speech AI APIs for transcription, understanding, and voice-powered applications.[5]

  • BugBug

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

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

How to connect AssemblyAI to BugBug

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

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

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

AssemblyAI modules

  • Create a Transcript Starts a speech-to-text job for the media at Audio URL. Turn on Speaker Labels, Sentiment Analysis, Summarization or Redact PII to add those analyses, and use Webhook URL to be told when it finishes.
  • Delete a Transcript Removes a transcript that AssemblyAI has stored for you. Nothing can be recovered.
  • Get a LeMUR Response Reads an earlier LeMUR answer again by its Request ID, with the Response text and the Usage it consumed.
  • Get a Transcript Reads a transcript with its Status, Audio Url and the language and analysis settings the job ran with.
  • Get the Redacted Audio of a Transcript Returns the Redacted Audio Url of a transcript whose media had spoken personal data beeped out, along with its Status.
  • Get Transcript Paragraphs Reads a finished transcript grouped into paragraphs. Output includes its Paragraphs and Confidence.
  • Get Transcript Sentences Splits a completed transcript into sentences, each with its own timing. Output includes the Sentences and the Audio Duration.
  • Get Transcript Subtitles Exports a transcript as a caption file in either of two formats. Use Characters Per Caption to limit how long each caption runs, and Subtitle Format to pick the format.
  • List Transcripts Lists transcripts on your account, filtered by Status or by Created On date. Turn on Throttled Only to see just throttled ones, which overrides the status filter.
  • Make an API Call Calls the AssemblyAI REST API directly with a free-form request under your saved credential.
  • Run a LeMUR Task Sends a Prompt to a LeMUR model together with transcripts from Transcript IDs or your own Input Text. Use Final Model to switch between the Anthropic Claude versions offered, and Temperature to make answers more or less creative.
  • Search Words in a Transcript Looks up keywords inside a finished transcript and reports each match with its Count and Timestamps. Use Words to give the terms to find.
  • Summarize a Transcript (LeMUR) Has LeMUR summarize completed transcripts. Use Answer Format for the style, such as TLDR or bullet points, and Prompt to steer what the summary covers.
  • Upload a Media File Uploads the File Data to AssemblyAI and returns a URL that a new transcript can then use as its audio source.

Explore alternative integrations

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

Automate AssemblyAI and BugBug on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting AssemblyAI and BugBug.

How do I connect AssemblyAI and BugBug?

Connect your AssemblyAI and BugBug 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 AssemblyAI and BugBug?

Example: when the "Watch Events" trigger in BugBug fires, WEXTL can "Create a Transcript" in AssemblyAI. AssemblyAI has 14 actions (including Create a Transcript, Delete a Transcript, and Get a LeMUR Response). BugBug has 101 actions (including Check a Project Import, Check a Test Import, and Create a Component). Add filters and transforms between steps when you need them.[1]

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

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 AssemblyAI and BugBug?

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

Does AssemblyAI integrate with BugBug in real time?

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

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

References

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

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

How we write our apps documentation

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

Explore AssemblyAI and BugBug, or get started