# Cloudflare Browser Rendering AI integration on Definable

> Cloudflare Browser Rendering enables developers to programmatically control and interact with headless browser instances running on Cloudflare’s global network, facilitating tasks such as automating browser interactions, capturing screenshots, generating PDFs, and extracting data from web pages.

## What this connects

Cloudflare Browser Rendering enables developers to programmatically control and interact with headless browser instances running on Cloudflare’s global network, facilitating tasks such as automating browser interactions, capturing screenshots, generating PDFs, and extracting data from web pages.

Vendor: https://developers.cloudflare.com/browser-rendering/

## Tools available

**4** tools available. First 4:

- `CLOUDFLARE_BROWSER_RENDERING_CAPTURE_SCREENSHOT` — Capture Screenshot — Tool to capture a webpage screenshot. Use when you need a visual snapshot of a URL or HTML with optional viewport and clipping. Always validate screenshot content — the tool returns a successful result even when the captured page is a 404 or error page, with no error signal raised.
- `CLOUDFLARE_BROWSER_RENDERING_LIST_ACCOUNTS` — List Accounts — List all Cloudflare accounts accessible to the authenticated API token. Returns account IDs, names, types, and settings. Use this to retrieve a valid account_id required by other browser-rendering actions like capture_screenshot, scrape_html_elements, and take_webpage_snapshot.
- `CLOUDFLARE_BROWSER_RENDERING_SCRAPE_HTML_ELEMENTS` — Scrape HTML Elements — Tool to scrape HTML elements for text, HTML, attributes, and box metrics. Use when you need detailed data of matched selectors after rendering a page.
- `CLOUDFLARE_BROWSER_RENDERING_TAKE_WEBPAGE_SNAPSHOT` — Take Webpage Snapshot — Capture both rendered HTML content and a screenshot of a webpage in a single request. Returns the full DOM content as a string and a Base64-encoded screenshot image. Useful when you need both visual representation and page content for analysis.

## Auth

Auth schemes: `API_KEY`.

## How agents use Cloudflare Browser Rendering

Inside a Definable workflow, Cloudflare Browser Rendering is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Cloudflare Browser Rendering** — the Researcher (GPT-5.5) pulls context from Cloudflare Browser Rendering (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Cloudflare Browser Rendering** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Cloudflare Browser Rendering (create record, post message, draft email).
- **Designer / Engineer → Distributor → Cloudflare Browser Rendering** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Cloudflare Browser Rendering (attach file, open PR comment, post status).

The Verifier checks every Cloudflare Browser Rendering call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- ai web scraping — https://definable.ai/apps/category/ai-web-scraping/
- developer tools — https://definable.ai/apps/category/developer-tools/

## Related

- HTML page: https://definable.ai/apps/cloudflare_browser_rendering/
- Same category (ai web scraping): https://definable.ai/apps/category/ai-web-scraping/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt