Agenty and BugBug Integration

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

Keep Agenty and BugBug matched by integrating their events and actions. When developer tools events happen in Agenty, 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 Agenty and BugBug

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

  • Agenty

    • Developer Tools
    • 1 trigger
    • 28 searches
    • 43 actions

    Cloud web scraping, crawling and change detection. Create and run scraping, crawling and monitoring agents, feed them URLs or stored lists, start jobs on demand or on a schedule, pull the extracted rows and logs, and react when a job completes.[5]

  • BugBug

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

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

How to connect Agenty to BugBug

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

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

WEXTL exposes actions and triggers for Agenty 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.

Agenty triggersBugBug actions

Agenty modules

  • Watch Agent Jobs Starts the workflow instantly through a webhook, as soon as an agent job finishes or fails.
  • Add Agents to a Project Files existing agents under an Agenty project. Use Agents to list which ones to include.
  • Add Rows to a List Adds rows to a stored list. Use Rows for free-form row objects, which are sent as the entire request body.
  • Cancel a Running Job Stops a job that is still running in Agenty. Use Agent to narrow the job choices to one agent.
  • Change Agent Schedule Status Switches the run schedule of an agent on or off. Turn on Enabled to activate the schedule, or turn it off to pause it.
  • Change API Key Status Changes the status of an Agenty API key by its numeric id from the API keys page. How the new status is chosen is undocumented and may toggle, so a retry may not be safe.
  • Change Workflow Status Enables or disables an Agenty automation, which this app calls a workflow. Turn on Enabled to activate it, or turn it off to stop it from firing. Output returns Enabled.
  • Copy an Agent Makes a duplicate of an existing agent. Add a Name to title the copy, bearing in mind the copy body is undocumented and the name goes out only if present.
  • Create a List Creates a stored list. Give it a Name of up to 100 characters, and add a Description of up to 250 if useful. Output has the List ID.
  • Create a Project Opens a new project for organizing agents. Add a Name to title it and a Description to explain it.
  • Create a Workflow Sets up an Agenty automation, called a workflow here. It watches Agents for events chosen with Fire On, such as Job Failed or Change Detected, then runs its Actions. Use Enabled to start it on or off.
  • Create an Agent Builds a new agent from a Name, a Type such as Scraping or Crawling, an Input to run against and a Config whose shape depends on the Type. Turn on Start after creation to run it straight away. Output gives the Agent ID.
  • Create an API Key Generates a new API key in your Agenty account. Use Name as its display name, although the create body is undocumented and the name goes through only if present.
  • Delete a Connection Removes a stored OAuth grant, and automations whose actions reference it will fail.
  • Delete a List Deletes a stored list from Agenty. Removal is one-way.
  • Delete a List Row Removes one row from a stored list, using the Row ID. The id is a string, even though list ids are numbers. The deletion sticks.
  • Delete a Workflow Deletes an Agenty automation, which this app calls a workflow. Deleted items are lost.
  • Delete Agents by Id Deletes several agents in a single call. Deleted data is lost.
  • Delete an Agent Deletes one agent from your Agenty account. It stays removed.
  • Delete an Agent Schedule Removes the run schedule that was set on an agent.
  • Delete an API Key Deletes an Agenty API key. Nothing guards against deleting the very key this credential authenticates with. Deletion is one-way.
  • Delete Projects by Id Deletes several projects in one call. It stays gone.
  • Delete Rows by Id Removes several rows from a stored list at once. Fill Row IDs with their ids as one comma-separated string.
  • Delete Users by Id Removes team members from your Agenty account. Deleted items stay gone.
  • Download a Job Result Downloads the result of one job as a file. Use Collection to pick which output collection by number, Format for the file type, and Search to narrow the rows.
  • Download API Keys as CSV Saves your API keys as a CSV file, narrowed with a Search text and arranged by Sort.
  • Download Jobs as CSV Pulls job records into a CSV file, for every agent or for just one Agent. Order them with Sort.
  • Download List Rows as CSV Writes every row of one stored list to a single CSV file.
  • Get a Job Reads one agent job. Use Agent to narrow the job choices, then name the Job to read.
  • Get a Job Output File Fetches one file produced by a job. Use File Name exactly as it appears in the job result.
  • Get a Job Result Reads the rows a job produced. Use Collection to read a later collection than the first, Format for the result format, and Sort, Order or Search to shape the rows.
  • Get a List Fetches a stored list record, giving its List ID, Name and Description.
  • Get a List Row Fetches one row from a stored list. Give Row ID as a string here, since the row schema documents no stable id field.
  • Get a Project Fetches the record of one Agenty project, to read its details.
  • Get a User Looks up one team member, giving the User ID, Name, Email and Role.
  • Get a Workflow Reads one automation with its Workflow ID, Name and the Agents it watches.
  • Get an Account Usage Report Reads the usage dashboard of your Agenty account for a time window, running from Start to End, both inclusive.
  • Get an Agent Fetches one agent, including its Agent ID, Project ID and Name.
  • Get an Agent Input Shows what an agent is set to run against, as a Type and its Data.
  • Get an Agent Schedule Reads the schedule attached to an agent, giving the next and the last run times as Next Scheduled Run At and Last Scheduled Run At.
  • Get an API Key Looks up one API key by the numeric id shown on the API keys page in Agenty. There is no picker, because listing keys can expose secret material.
  • Get Lists Browses your stored lists. Fill Search with free text to narrow them, and add Order to set the direction.
  • Get the Latest Agent Result Reads the most recent result of an agent. Agenty requires Download on this read, to choose between inline rows and a file. Add Collection, Sort, Order or Search to narrow what is read.
  • Invite a User Invites someone to join your Agenty team by Email. Use Role to grant owner, admin or manager access, and Name to add a display name.
  • List Agents Shows the agents in your account, filtered by a Search text and ordered with Sort and Order.
  • List API Keys Retrieves your Agenty API keys, optionally narrowed by a Search text.
  • List Connections Lists the OAuth connections stored in your Agenty account.
  • List Job Logs Reads the log lines of one job, narrowed by Search or arranged by Sort.
  • List Jobs Finds agent jobs across every agent, or only those of one Agent. Add Order to choose the direction.
  • List Projects Gives you the projects that group your agents, with an optional Search filter.

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.

Explore alternative integrations

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

Automate Agenty and BugBug on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Agenty and BugBug.

How do I connect Agenty and BugBug?

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

Example: when the "Watch Agent Jobs" trigger in Agenty fires, WEXTL can "Check a Project Import" in BugBug. Agenty has 1 trigger (including Watch Agent Jobs). 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 Agenty trigger actions in BugBug, and BugBug in Agenty?

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

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

Does Agenty integrate with BugBug in real time?

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

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

References

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

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

Explore Agenty and BugBug, or get started