Bugbug is a low-code test automation tool. The easiest way to cut costs of software testing. Automate your web app testing 3x faster without scaling your QA team.
Bugbug is a low-code test automation tool. The easiest way to cut costs of software testing. Automate your web app testing 3x faster without scaling your QA team. On Nagent, Bugbug is exposed as a fully-configurable developer tools integration that any agent can call — 4 actions, and API key authentication. No code is required to wire Bugbug into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Bugbug to automate the kinds of tasks developer tools teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Bugbug into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Bugbug, with input parameters and output schema. Drop these into any step of an agent built in Helix.
BUGBUG_GET_TEST_RUN_DETAILSGet detailed information about test runs from BugBug. This action retrieves a paginated list of test runs with comprehensive details including execution status, timing information, browser settings, and error details. Supports filtering by start time and sorting by various fields. Useful for monitoring test execution history, analyzing test performance, and debugging test failures.
Input parameters
Page number for pagination
Sort order for results
Number of items per page
ISO 8601 formatted timestamp to filter runs that started after this time
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGBUG_LIST_SUITESList all available test suites in the Bugbug platform. This tool makes a GET request to the /suites/ endpoint and returns a list of available test suites with pagination support.
Input parameters
Page number for pagination
Number of items per page
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGBUG_LIST_TESTSRetrieves a list of all available tests in the BugBug account. This action provides access to all tests in the account with pagination support. It returns basic information about each test including its ID, name, active status, and recording status.
Input parameters
Page number for pagination
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGBUG_RUN_TESTExecute a test in BugBug and return the test run details. This action triggers a test run with optional configuration for browser, device, viewport, and variable overrides. It returns the test run ID, status, modification timestamp, and a URL to view detailed results in the BugBug web application.
Input parameters
Model for test run profile configuration.
The unique identifier of the test to execute (UUID format)
List of variables to override for this test run
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 90 agents privately built on Nagent that already use Bugbug.
Build on Nagent
Connect Bugbug to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Bugbug, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Bugbug is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Bugbug is connected, you configure its 4 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Bugbug steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Bugbug event fires, the agent kicks off automatically.
Every Bugbug action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Bugbug ships with 4 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Bugbug together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Bugbug-based workflows tailored to your business.