Apify and Hyper Browser Integration

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

Connect Apify and Hyper Browser to automate developer tools workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.

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

Learn about Apify and Hyper Browser

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

  • Apify

    • Developer Tools
    • 4 triggers
    • 55 searches
    • 60 actions

    Run Apify Actors and tasks, manage datasets and stores, and watch for Actor run completion events.[5]

  • Hyper Browser

    • Developer Tools
    • 1 trigger
    • 51 searches
    • 55 actions

    Run cloud browser sessions, scrape and crawl websites, run AI browser agents and manage sandboxes.[6]

How to connect Apify to Hyper Browser

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

How does the integration between Apify and Hyper Browser work in WEXTL?

WEXTL exposes actions and triggers for Apify and Hyper Browser 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.

Apify triggersHyper Browser actions

Apify modules

  • Abort a Build Aborts a build while it is still running and ends its work early.
  • Abort a Build (Cross-Actor) Ends a build directly through its Build, without first naming the Actor that owns it.
  • Abort a Run Cancels a run that has not finished yet and halts whatever the Actor was doing.
  • Abort a Run (Cross-Actor) Terminates a run directly through its Run, with no Actor needed.
  • Add a Request to a Queue Puts a single new request into a request queue, where it waits to be processed.
  • Batch Add Requests Adds up to 25 requests to a request queue in one call, each with a Unique key, URL, Method and Payload. Turn on Add to the front to place them at the head of the queue.
  • Build an Actor Kicks off a new build for an Actor, producing a build record with a Status and Data.
  • Charge Events in a Run Applies charges for events to an Actor run, identified by its Actor and Run.
  • Create a Dataset Sets up a dataset in Apify storage and returns its Created at time.
  • Create a Key-Value Store Opens a new key-value store, a place that keeps records under keys.
  • Create a Request Queue Opens a new request queue that holds requests waiting to be processed.
  • Create a Schedule Registers a schedule through Apify and returns its Name.
  • Create a Task Saves a task with Apify and returns its Updated at time.
  • Create a Version Attaches another version to an Actor, alongside the ones it already has.
  • Create an Actor Creates an Actor in Apify and returns its ID and Name.
  • Create an Environment Variable Defines a new environment variable on a particular Version of an Actor.
  • Decode and Verify Data Decodes an encoded value and verifies it, the reverse of Encode and Sign Data.
  • Delete a Dataset Removes a dataset from your Apify storage.
  • Delete a Key-Value Store Deletes a key-value store held in your Apify storage.
  • Delete a Record Removes the record kept under a given Recordkey in a key-value store.
  • Delete a Request Removes the request with a given Requestid from a request queue.
  • Delete a Request Queue Deletes a request queue from your Apify storage.
  • Delete a Schedule Removes a schedule that exists in your Apify account.
  • Delete a Task Deletes a stored task from your account.
  • Delete a Version Removes a version that was attached to an Actor.
  • Delete a Webhook Deletes a webhook configured on your Apify account.
  • Delete an Actor Deletes an Actor from your Apify account.
  • Delete an Environment Variable Removes an environment variable from the chosen Actor Version.
  • Download Records (Batch Export) Downloads every record kept in a key-value store as one batch export.
  • Encode and Sign Data Encodes and signs data, producing a value that Decode and Verify Data can check.
  • Get a Build Reads a build of an Actor and reports its Status and last update.
  • Get a Build (Cross-Actor) Reads a build straight from its Build, even when the owning Actor is not known.
  • Get a Build Log Returns the log text that was produced while a build ran.
  • Get a Build Log (Cross-Actor) Returns the log text of a build addressed by Build alone, whichever Actor it belongs to.
  • Get a Dataset Reads the details of a dataset, including its Name and creation time.
  • Get a Key-Value Store Reads the details of a key-value store such as its Name and timestamps.
  • Get a Record by Key Reads the record kept under a given Recordkey in a key-value store.
  • Get a Request Reads a single request from a request queue by its Requestid, including its Status and Data.
  • Get a Request Queue Returns a request queue with its Name and creation time.
  • Get a Run Fetches a single Actor run together with its Status and Updated at.
  • Get a Run (by ID, Cross-Actor) Reads a run straight from its Run, regardless of the Actor behind it.
  • Get a Schedule Returns a schedule with its Name, Status and Created at.
  • Get a Schedule Log Returns the log describing what a schedule has done so far.
  • Get a Task Reads the stored configuration of a task, along with its timestamps.
  • Get a Task Input Reads the input values that are stored with a task and used when it runs.
  • Get a Version Reads a version of an Actor together with its Name and timestamps.
  • Get a Webhook Returns a webhook configuration with its Name and timestamps.
  • Get a Webhook Dispatch Reads a single webhook dispatch by its Dispatchid, including its Status.
  • Get an Actor Looks up an Actor and returns its ID, Name, Status and Data.
  • Get an Environment Variable Reads a single environment variable defined for an Actor Version, with its Name.

Hyper Browser modules

  • Add an Extension Uploads a browser extension package as a zip File so sessions can load it. Give it a Name to find it later. Returns the new extension with its Id and timestamps.
  • Cancel a WebMCP Invocation Asks Hyperbrowser to cancel a tool call that is running in a session, using its Invocation ID. The reply shows whether Cancellation Requested was recorded.
  • Cancel an Image Build Stops an image build that is still running before it finishes.
  • Complete an Image Build Upload Tells Hyperbrowser the image archive has finished uploading and starts the build. Repeat the Input SHA-256 and Input Size Bytes from the build, and add Input Format if one was set.
  • Create a Profile Makes a saved browser profile that keeps cookies and storage between sessions. Use Name to label it.
  • Create a Sandbox Boots an isolated machine from an image, a snapshot or a macOS disk. Set the Region, vCPUs and Memory Mi B, add a GPU, and use Exposed Ports or Mounts to wire it up. Returns the Status and whether it is Ready.
  • Create a Sandbox Memory Snapshot Captures the memory of a running sandbox for a later restore. Use Snapshot Name to label it. Returns the Snapshot Id and its Status.
  • Create a Secret Stores a secret record under a Name, with Description, Type, Metadata and Protection. Add the value afterwards from the Hyperbrowser dashboard or SDK, since this module cannot set it.
  • Create a Session Launches a cloud browser session. Turn on Use Stealth or Use Ultra Stealth for the stealth modes, add Use Proxy with a Proxy Country, and use Solve CAPTCHAs for challenges. Returns the Id and Status of the session.
  • Create a Vault Creates a vault that holds credentials under a Name. Use Entries to fill it right away, and Description to say what it is for.
  • Create a Volume Creates persistent storage under a Name that sandboxes can mount. Returns its Id, Size and Transfer Amount.
  • Create an Image Build Registers a sandbox image build, with Image Name, Input SHA-256 and Input Size Bytes. Upload the archive yourself, then finish the upload. Turn on Enable GPU Builds to publish a GPU image too. Returns the Build and Upload details.
  • Delete a Profile Deletes a saved browser profile from your account.
  • Delete a Sandbox Image Removes an uploaded image from your sandbox images. Confirms with Deleted and the Image Name.
  • Delete a Sandbox Snapshot Removes a memory snapshot that was taken of a sandbox.
  • Delete a Secret Removes a stored secret. The Id and Name of the removed secret are returned.
  • Delete a Secret Version Removes one numbered Version of a secret.
  • Delete a Vault Deletes a credential vault. The Id and Name of the removed vault are returned.
  • Delete a Volume Deletes a storage volume from your account and returns its Id and Name.
  • Evaluate a Session CAPTCHA Tries to solve a CAPTCHA on a live session. Provide a CAPTCHA with its CAPTCHA Type, or text and image details, and use Max Iterations to bound the attempts. Shows how many Iterations Run and whether it was Solved.
  • Expose a Sandbox Port Opens a Port on a running sandbox to the outside through a URL. Use Auth to protect it. Returns the Url and when the Browser Url Expires At.
  • 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.
  • Fill a Credential Types stored login details into a form on a live session. Pass the Fields to fill and take values from a Credential, Vault or One Password. Use Page ID, Page URL and Frame to aim at the right form.
  • Fork a Profile Copies a profile into a new one that starts with the same cookies and storage. Use Name to title the copy.
  • 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.
  • Get Crawl Job Results Reads the pages a crawl has collected so far, each with its Url, Status, Metadata, Markdown and Html. Set Limit to choose how many pages to read.
  • Get Crawl Job Status Checks whether a site crawl is still running, using the Status alone.
  • Get CUA Task Results Collects the Data of a finished CUA agent, together with its Status and any Error.
  • Get CUA Task Status Tells you whether a CUA agent has finished, through its Status alone.
  • Get Extract Job Results Reads the structured Data an extract job pulled from your URLs, and the Error when a job failed.
  • Get Extract Job Status Checks whether an extract job is still running by reading the Status without any extracted Data.
  • Get Gemini Computer Use Task Results Returns the Data from a Gemini browser job, and an Error if it failed.
  • Get Gemini Computer Use Task Status Looks up the Status of a Gemini browser job on its own, without the Data.

Explore alternative integrations

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

Automate Apify and Hyper Browser on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Apify and Hyper Browser.

How do I connect Apify and Hyper Browser?

Connect your Apify and Hyper Browser 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 Apify and Hyper Browser?

Example: when the "Watch Aborted Runs" trigger in Apify fires, WEXTL can "Add an Extension" in Hyper Browser. Apify has 4 triggers (including Watch Aborted Runs, Watch Failed Runs, and Watch Succeeded Runs). Hyper Browser has 106 actions (including Add an Extension, Cancel a WebMCP Invocation, and Cancel an Image Build). Add filters and transforms between steps when you need them.[1]

Can Apify trigger actions in Hyper Browser, and Hyper Browser in Apify?

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 Apify and Hyper Browser?

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

Does Apify integrate with Hyper Browser in real time?

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

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

References

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

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

How we write our apps documentation

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

Explore Apify and Hyper Browser, or get started