Connect Hyper Browser integrations

Verified

Hyper Browser: Run cloud browser sessions, scrape and crawl websites, run AI browser agents and manage sandboxes, connected to WEXTL workflows and AI agents. Send Hyper Browser deploys, issues and webhook events into your engineering workflows. When Watch Events fires, update the docs, notify a team or continue with Fetch a Web Page.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region
  • Hyper Browser
  • WEXTL
  • Alchemy
  • Adafruit
  • Lokalise
  • TinyFish
  • Supadata
  • GetScreenshot
  • Apify
  • CircleCI
  • GitLab
  • Travis CI
  • Google Sheets
  • Bright Data
  • Piloterr
  • Documenso
  • Peekalink
  • Oneflow
  • Radar
  • ScreenshotOne
  • swiDOC

Supported triggers and actions for Hyper Browser integration

Triggers can detect changes in Hyper Browser and run actions that can create, search or modify data inside Hyper Browser automatically[3], exactly how you set them.

  • Watch Events Starts the workflow when a Hyperbrowser session event fires. It runs instantly through a webhook with the Event Type, Data and Timestamp.
  • Fetch a Web Page Loads a page from its URL and returns its content as Data. Use Outputs to choose formats, with Stealth, Browser, Navigation and Cache for finer control.
  • Get a Profile Loads a saved browser profile with its Name, Team Id and timestamps.
  • Get a Sandbox Loads a sandbox to check its Status, Runtime Class and whether it is Ready.
  • Get a Sandbox Snapshot Loads the stored details of one memory snapshot that was taken from a sandbox.
  • Get a Secret Loads a secret record with its Name, Description, Type and Metadata. The stored value is not part of it.
  • Get a Session Loads a browser session with its Status, Start Time and End Time.
  • Get a Session Downloads URL Gives a link to the files a session downloaded. Check the Status to see when it is ready, and read any Error. Only works if Save Downloads was on for the session.
  • Get a Session Recording URL Provides a link to replay the pages of a session as a recording, available once the Status is complete. Also reports an Error when recording went wrong.
  • Get a Session Video Recording URL Fetches the link to the video file of a session, plus any Error. The session needs Enable Video Web Recording turned on at creation.
  • Get a Vault Loads a vault with its Name, Description and Entries.
  • Get a Volume Loads a storage volume with its Name, Size and Transfer Amount.
  • Get a WebMCP Invocation Result Reads the outcome of a tool call started in a session, using its Invocation ID. Use Wait Seconds to hold the request open until the call finishes.
  • Get an Image Build Loads one sandbox image build with its progress and details.
  • Get Batch Scrape Job Results Reads the outcome of a batch scrape, with the scraped Data for each page, plus Total Scraped Pages and Total Page Batches.
  • Get Batch Scrape Job Status Checks whether a batch scrape is still running and returns only its Status.
  • Get Browser Use Task Results Reads what a Browser Use run produced, with its Status, Data and any Error.
  • Get Browser Use Task Status Polls a Browser Use run and reads only its Status.
  • Get Claude Computer Use Task Results Pulls the answer Claude produced for a browser job, plus the Status and any Error.
  • Get Claude Computer Use Task Status Checks the progress of a Claude browser job. Only the Status is read.

How to integrate Hyper Browser in automation workflow?

Hyper Browser in three steps: start with "Watch Events", connect one credential, then add your next step.

How Hyper Browser connects and integrates with WEXTL

Save and approve your credentials once. WEXTL® stores authorization information encrypted and reuses the authentication whenever Hyper Browser app is called in workflows. That allows your developer tools automations to run without your attention, per defined schedule[7]. See the integration guide[6] for a detailed list of fields that Hyper Browser supports.

Full Hyper Browser API documentation

The following table illustrates what fields Hyper Browser integration require during authorization flow inside our workflow builder[4].

Connect Hyper Browser

  • API Key*Text

    ••••••••

Demonstration of Hyper Browser connection step inside WEXTL Workflow Builder[4].
FieldTypeHelp
API KeyRequired
password

Open the Hyperbrowser dashboard and create an API key under API Keys. Calls spend credits from your team.

Connect Hyper Browser to popular apps on WEXTL

Enter a name of the other app you want to sync with Hyper Browser below. Click on selected app to explore integration options with Hyper Browser. If the app you search for is not available in WEXTL yet, you can use HTTP node[10] instead to integrate it directly.

Example automation with Hyper Browser integration

Select Watch Events trigger from Hyper Browser - this will be a starting point in your automation. Whenever event happens in Hyper Browser, workflow will start[7] from Watch Events node.

Search for Add an Extension, connect it as the next step of integration sequence. You can use filters between Watch Events and Add an Extension, so only important data pass from Watch Events to the next step. WEXTL gives you full control over the process of Hyper Browser automation. All parts of workflow are visible on the canvas[4].

Hyper Browser on WEXTL has 107 modules for creating developer tools automations. Explore Hyper Browser documentation for more.

  • Hyper BrowserWatch Events
  • AlchemyPerforms action

OR

  • AlchemyTriggers
  • Hyper BrowserAdd an Extension
Demonstration of how visual Hyper Browser automation[6] looks in WEXTL.

Frequently asked questions

Common questions about automating Hyper Browser in your workflows.

What triggers does Hyper Browser support?

Hyper Browser has 1 trigger, including "Watch Events". Triggers are start points of the workflow, and automations may start from them.

What actions can I run in Hyper Browser?

Integration has 106 actions, including "Fetch a Web Page", "Get a Profile", and "Get a Sandbox", and more. Refer to our Hyper Browser Documentation for detailed inputs and outputs.

Do I need to write code to build automations?

No. The 106 Hyper Browser modules, like "Fetch a Web Page", are forms on the canvas: pick a field, map data from an earlier step. Code is optional[4].

Is the integration secure?

Yes. You fill in the Hyper Browser credential once. WEXTL encrypts it at rest, and only your team can use it.

How does WEXTL integrate with Hyper Browser?

Through the official Hyper Browser API: 106 modules, plus "Make an API Call" for any endpoint they don't cover[3].

Can I use webhooks with Hyper Browser?

Yes. "Watch Events" is instant: Hyper Browser pushes each event, so there is no polling delay.

Why use WEXTL platform for Hyper Browser automation?

WEXTL is an AI-first visual canvas: describe the Hyper Browser flow in plain words and AI wires the nodes[4].

Automate Hyper Browser on WEXTL®

Claim your 3-day trial to build Hyper Browser integrations and access every WEXTL® feature.

Cancel anytime.

References

List of sources used to gather information about the Hyper Browser integration.

  1. Hyper Browser integration source code, module specs and credentials implementation.
  2. Internal Hyper Browser integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official Hyper Browser vendor API documentation, 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. WEXTL® Apps Library
  6. WEXTL® Hyper Browser App Documentation
  7. WEXTL® Workflow Scheduler
  8. WEXTL® HTTP node documentation

How we write and maintain Hyper Browser app documentation

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