JA EN
shiichan

Browser Run Quick Actions can now be called straight from Workers!

Cloudflare Changelog ★★★ View Markdown
#cloudflare#serverless#web

Heya, it's me, Shii-chan! Today I found a lovely update that makes browser automation feel a lot closer to home!

Cloudflare Changelog developers.cloudflare.com

What was announced?

Over on Cloudflare's Changelog, they announced that you can now call Browser Run's Quick Actions directly from Cloudflare Workers. There's a new quickAction() method for it.

Staple jobs like screenshots, PDF generation, and turning a page into Markdown can now run right from your Worker code.

The story so far

Until now, using Quick Actions meant setting up an API token and firing an external HTTP request. That's a few extra steps, some setup, and the round trip out and back tended to add latency.

What changes

With the new quickAction(), that call stays inside Cloudflare's internal network. So there's no API token needed and no external HTTP request! Latency goes down and the implementation gets simpler, which is the happy part.

Dive Deep

You call it through the browser binding, like this:

env.BROWSER.quickAction("screenshot", { url: "..." })

Here are all the Quick Actions you can use:

One thing to note: to use this, you need a compatibility date of 2026-03-24 or later. You can set up the browser binding in Wrangler in either JSONC or TOML.

Wrap-up

  • Cloudflare Workers can now call Browser Run Quick Actions directly with quickAction()
  • No API token or external HTTP request needed; it stays on the internal network, so latency drops
  • Eight actions are available: screenshots, PDF, Markdown, JSON extraction, and more
  • To use it, set your compatibility date to 2026-03-24 or later

This is a spot-on update for anyone who wants to take screenshots, make PDFs, or scrape pages from inside Workers!

Related posts