Browserless and Updown.io Integration

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

Connect Browserless and Updown.io 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 Browserless and Updown.io

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

  • Browserless

    • Developer Tools
    • 15 searches
    • 24 actions

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

  • Updown.io

    • Developer Tools
    • 1 trigger
    • 8 searches
    • 9 actions

    Website uptime monitoring with checks, alerts, status pages and downtime reports.[6]

How to connect Browserless to Updown.io

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

How does the integration between Browserless and Updown.io work in WEXTL?

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

Updown.io triggersBrowserless actions

Updown.io modules

  • Create a Check Starts monitoring a URL or a heartbeat with updown.io. Use Period (Seconds) to set how often it runs and Apdex Threshold to set the response time that counts as satisfying.
  • Create a Recipient Adds a place to send alerts, such as an email address, a phone number for SMS, or a webhook URL. Use Select on All Checks to attach it to every check you already have.
  • Create a Status Page Builds a page that shows the state of several Checks, in the order given. Use Visibility and Access Key to control who can open it.
  • Delete a Check Deletes one monitoring check from updown.io. This cannot be undone.
  • Delete a Recipient Removes an alert recipient from your updown.io account. A webhook recipient may belong to a workflow trigger.
  • Delete a Status Page Removes a published status page. This cannot be undone.
  • Get a Check Reads one check with its URL, Uptime, Period and current Down state. Turn on Include Metrics for the last hour of performance figures, or Include Results for the last 5 requests.
  • Get Check Metrics Reads Uptime, Apdex, Timings and Requests for one check over a period. Use From and To to set the window and Group By to split the totals.
  • List Check Downtimes Finds each outage of one check with its Started At, Ended At and Duration (Seconds). Turn on Include Results to add the requests before the downtime and after recovery.
  • List Checks Lists every check in your updown.io account with its Token, URL, Alias and Uptime. Use Limit to return fewer rows when you only need a few.
  • List Node IP Addresses Lists the IP Address values that updown.io sends its checks from, for firewall allow lists. Use Address Family to get only IPv4 or only IPv6.
  • List Nodes Shows the monitoring locations of updown.io with their Code, City and Country. Each row also has IPv4 and IPv6 values for that node.
  • List Recipients Gets the alert recipients on your account, each with its ID, Type, Name and Value. Run it to find the ID of a recipient before removing one.
  • List Status Pages Retrieves your status pages, each with its Token, Name and Visibility. Checks on every page are included.
  • Make an API Call Calls the Updown.io REST API directly with a free-form request under your saved credential.
  • Update a Check Edits the URL, Period (Seconds), Apdex Threshold or Enabled setting of an existing check. Alias, String Match and Mute Until change only when filled in.
  • Update a Status Page Renames a status page or edits its Description, Visibility and Access Key. Use Checks to replace the whole list of checks it shows.
  • Watch Events Starts the workflow the moment updown.io reports a check going down or coming back up. Use the Event, Time and Description values of each alert, plus the Check Alias and Check URL.

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 Browserless and Updown.io integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Browserless and Updown.io on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Browserless and Updown.io.

How do I connect Browserless and Updown.io?

Connect your Browserless and Updown.io 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 Browserless and Updown.io?

Example: when the "Watch Events" trigger in Updown.io fires, WEXTL can "Audit Page Performance" in Browserless. Browserless has 39 actions (including Audit Page Performance, Cancel a Batch Scrape, and Cancel a Crawl). Updown.io has 17 actions (including Create a Check, Create a Recipient, and Create a Status Page). Add filters and transforms between steps when you need them.[1]

Can Browserless trigger actions in Updown.io, and Updown.io in Browserless?

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 Browserless and Updown.io?

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

Does Browserless integrate with Updown.io in real time?

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

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

References

List of sources used to gather information about the Browserless and Updown.io integration.

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

How we write our apps documentation

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

Explore Browserless and Updown.io, or get started