Apify and Browserless Integration

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

Connect Apify and Browserless 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 Browserless

Detailed info you need to know about Apify and Browserless 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]

  • Browserless

    • Developer Tools
    • 15 searches
    • 24 actions

    Render pages to PDFs and screenshots, scrape sites and run crawls in cloud browsers.[6]

How to connect Apify to Browserless

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

How does the integration between Apify and Browserless work in WEXTL?

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

Browserless modules

  • Audit Page Performance Runs a Lighthouse audit on a Page URL and returns the Lighthouse Report. Use Categories to pick which scores to compute and Budgets to set performance limits.
  • Cancel a Batch Scrape Halts a multi-URL scrape that is still underway.
  • Cancel a Crawl Ends a site crawl that is in progress. A crawl that has finished cannot be cancelled.
  • Cancel an Agent Run Stops an agent run that is still active. A run that has already finished is deleted instead, together with its result.
  • Create a PDF Renders a Page URL or your own HTML to a PDF file. Set the Paper Format and Margin Top, switch to Landscape, or give Page Ranges to print only some pages.
  • Create a Session Starts a persistent browser that is billed while open and closes after the Time to Live (ms). Add a Profile to reuse saved logins, or a Start URL to open a page right away.
  • Delete a Profile Deletes a saved browser profile along with its stored logins and cookies, and returns its Name with a Deleted flag.
  • Delete a Session Stops a running browser session. Turn on Force to end it even when it is busy.
  • Download Files Runs your Puppeteer JavaScript Code, which should click a download link, and returns the File the browser downloaded. Use Context for values the script reads.
  • Export a Page Saves a page as a file from its Page URL. Turn on Include Resources to get a zip with its images, scripts and styles.
  • Get a Batch Scrape Reports the Status, Total Pages, Completed Pages and Failed Pages of a batch scrape. Use Skip to move past results already read.
  • Get a Crawl Checks on a crawl and reports its Status and how many Completed Pages it has. Use Skip with the Next Page URL from the previous answer to read further pages.
  • Get a Profile Shows one saved browser profile, with its Name, its Cookies and Origins, and when it was Last Used.
  • Get a Profile State Exports the saved Cookies and the Origins for one profile. Because the reply contains session cookies, keep it out of logs.
  • Get an Agent Run Reads the Status, Result and Steps of an AI browser agent run, including any Error. Use Max Response Size (bytes) to limit how much is returned.
  • Get Page Content Loads a Page URL, or HTML of your own, and returns the resulting HTML. Use Wait for Selector to hold until an element appears, and Cookies to open a page with cookies already set.
  • Get the Service Info Reports the Version of Browserless along with the browser builds it runs: Chromium, WebKit, Firefox, Playwright and Puppeteer.
  • List Agent Runs Shows agent runs, each with its Run ID, Status and a Preview. Use Status to list runs that are in one state.
  • List Crawls Returns crawls with their URL, Status and Total Pages. Narrow the list to one Status, or lower Limit to return fewer crawls.
  • List Profiles Retrieves saved browser profiles with Name, Domain Auth and Last Used. Use Limit to restrict how many are read.
  • List Proxy Cities Finds the countries and cities where city-level proxying is available. Use Country to look at a single country, and read Total Cities for the count.
  • List Scrapers Returns the ready-made scrapers Browserless provides, together with a Version number.
  • List Site Skills Lists the skills saved for one Domain, each with its Title and Version. Use Task to narrow them to a particular job.
  • List Website URLs Maps a site to its page URLs, returning URLs and a Count. Use Search to filter the URLs by text, and Sitemap to include, skip or use only the sitemap.
  • Make an API Call Calls the Browserless REST API directly with a free-form request under your saved credential.
  • Run a BrowserQL Query Executes a BrowserQL GraphQL document that drives a cloud browser and returns its Data or Errors. Pass Variables to parameterise the Query.
  • Run a Function Runs your Puppeteer JavaScript in a cloud browser and returns its Result with the Content Type. Use Context to feed variables to the code.
  • Run a Scraper Calls one of the ready-made scrapers listed by List Scrapers, such as google. Use Parameters to pass the inputs its API expects.
  • Scrape a Page Extracts a page through Browserless smart scrape. Use Formats to choose Markdown, HTML or Links, and turn on Only Main Content to skip menus and footers.
  • Scrape Page Elements Reads the text, HTML and attributes of everything that matches the CSS selectors. Add selectors to Elements and point at a Page URL, or feed markup through HTML.
  • Search the Web Runs a web search for a Query and returns Web Results, News Results or Image Results. Use Scrape Results As to fetch the content of each hit.
  • Start a Batch Scrape Queues an asynchronous scrape of many URLs. Turn on Skip Invalid URLs to ignore bad entries and use Webhook URL to be told when it ends.
  • Start a Crawl Begins an asynchronous crawl of a site from a Start URL. Use Page Limit and Max Depth to bound it, and Include Paths or Exclude Paths to steer it.
  • Start an Agent Run Launches an AI browser agent on a Task, optionally from a Start URL. Use Max Steps to cap its work. The reply gives a Run ID and Status.
  • Take a Screenshot Renders a Page URL or HTML to an image file. Use Selector to capture one element, Full Page for the whole scroll height, and Image Type for the format.
  • Unblock a Page Loads a page protected by bot detection and returns its HTML, Cookies or a Screenshot (Base64). Turn on Keep Browser Open to keep working in the same browser.
  • Update a Profile Name Renames a saved browser profile to a New Name. A name that another profile already uses is rejected.
  • Update a Profile State Replaces the stored Cookies and Origins of a profile by supplying a new State, a JSON object shaped like an export of the same profile.
  • Upload a Profile Makes a new browser profile out of a Name and a State of cookies and origins. Returns the Profile ID.

Explore alternative integrations

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

Automate Apify and Browserless on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Apify and Browserless.

How do I connect Apify and Browserless?

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

Example: when the "Watch Aborted Runs" trigger in Apify fires, WEXTL can "Audit Page Performance" in Browserless. Apify has 4 triggers (including Watch Aborted Runs, Watch Failed Runs, and Watch Succeeded Runs). Browserless has 39 actions (including Audit Page Performance, Cancel a Batch Scrape, and Cancel a Crawl). Add filters and transforms between steps when you need them.[1]

Can Apify trigger actions in Browserless, and Browserless 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 Browserless?

No. Apify-to-Browserless 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 Browserless in real time?

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

You can build your Apify + Browserless 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 Browserless integration.

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

Explore Apify and Browserless, or get started