CONNECT APP
Build with Cloudflare Browser Rendering
Developer Tools
- API key
MCP
Give your agent Cloudflare Browser Rendering tools
Every Cloudflare Browser Rendering action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Cloudflare Browser Rendering account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "cloudflare_browser_rendering",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Get HTML Content:
const result = await mcp.callTool({
name: "cloudflare_browser_rendering-get-html-content",
arguments: {
html: "HTML",
url: "URL",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "cloudflare_browser_rendering",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Get HTML Content:
result = await session.call_tool("cloudflare_browser_rendering-get-html-content", {
"html": "HTML",
"url": "URL",
})API PROXY
Call the Cloudflare Browser Rendering API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Cloudflare Browser Rendering API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://api.example.com/v1/me",
})
// Any allowed Cloudflare Browser Rendering endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://api.example.com/v1/me
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkuZXhhbXBsZS5jb20vdjEvbWU?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Cloudflare Browser Rendering actions from your backend
Connect a user's Cloudflare Browser Rendering account once, then run Get HTML Content on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "cloudflare_browser_rendering-get-html-content",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
cloudflare_browser_rendering: { authProvisionId: "apn_xxxxxxx" },
html: "HTML",
url: "URL",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="cloudflare_browser_rendering-get-html-content",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"cloudflare_browser_rendering": {"authProvisionId": "apn_xxxxxxx"},
"html": "HTML",
"url": "URL",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "cloudflare_browser_rendering-get-html-content",
"configured_props": {
"cloudflare_browser_rendering": { "authProvisionId": "apn_xxxxxxx" },
"html": "HTML",
"url": "URL"
}
}'TOOLS
Cloudflare Browser Rendering actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Get HTML Content
actionFetches rendered HTML content from provided URL or HTML. See the documentationRead-onlyv0.0.2 -
Get PDF
actionFetches rendered PDF from provided URL or HTML. See the documentationWritev0.0.3 -
Get Screenshot
actionTakes a screenshot of a webpage from provided URL or HTML. See the documentationWritev0.0.3 -
Scrape
actionGet meta attributes like height, width, text and others of selected elements. See the documentationWritev0.0.3
EVENTS
Cloudflare Browser Rendering triggers
Event sources your backend can deploy for users and receive through a webhook.
No Cloudflare Browser Rendering triggers are available yet.
MULTI-APP
Use Cloudflare Browser Rendering with other popular apps
Most products don't stop at one integration. Pair Cloudflare Browser Rendering with the other apps your users rely on, and ship use cases that span both.
REFERENCE
App details
Reference metadata for the Cloudflare Browser Rendering connector in the Pipedream registry.
- App slug
- cloudflare_browser_rendering
- Authentication
- API key
- Categories
- Developer Tools
- Actions
- 4
- Triggers
- 0
- API proxy
- Available