# SHAI — Cloudflare

> Cloudflare is entry 147 on the integrations list SHAI was asked to match. SHAI has not written this tool up, so it will not describe it — what it records is the route.

Canonical page: /integrations/cloudflare

## How SHAI connects to it
SHAI connects to it through Pipedream, which holds the sign-in so no token ever reaches SHAI or the model. Pipedream publishes 2 components under this name — `cloudflare_api_key`, `cloudflare_r2` — and SHAI will not pick one for you: you choose when you connect.

## What it needs
the operator's Pipedream project — then nothing from you but a sign-in.

Pipedream publishes 2 components under this name (`cloudflare_r2`, `cloudflare_api_key`). SHAI will not pick one for you — choose the one you want when you connect, and it runs through the same door as every other Pipedream app. One click once the operator connects a Pipedream project to this deployment.

## Where that was read
https://github.com/PipedreamHQ/pipedream@58ecb26:components/cloudflare_r2/cloudflare_r2.app.mjs · https://github.com/PipedreamHQ/pipedream@58ecb26:components/cloudflare_api_key/cloudflare_api_key.app.mjs, verified 2026-09-16.

Connect it: /connections?tool=cloudflare