# Cloudflare integrations: zones and DNS records

> Create a zone, create a DNS record and upload a Worker module in Cloudflare. Connect Cloudflare to the rest of your developer tools stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/cloudflare-integrations/
**Categories:** Developer tools
**Connects through:** HTTP Connector

## Overview

Cloudflare is a global network for websites and apps, providing DNS, content delivery, caching, DDoS protection, a web application firewall, and serverless Workers. Tray.ai connects to Cloudflare through the HTTP Connector, so your workflows can call the Cloudflare API alongside the rest of your stack.

## Use cases

### Zones

Read, create, update, and delete zones in Cloudflare from any Tray.ai workflow. The Cloudflare API covers calls such as list zones and get zone details.

- List zones
- Get zone details
- Create a zone

### DNS records

Read, create, update, and delete dns records in Cloudflare from any Tray.ai workflow. The Cloudflare API covers calls such as list DNS records and create a DNS record.

- List DNS records
- Create a DNS record
- Update a DNS record

### Cache

Read and update cache in Cloudflare from any Tray.ai workflow. The Cloudflare API covers calls such as purge cached content and get Cache Reserve setting.

- Purge cached content
- Get Cache Reserve setting
- Change Cache Reserve setting

### Worker scripts

Read, create, and delete worker scripts in Cloudflare from any Tray.ai workflow. The Cloudflare API covers calls such as list Worker scripts and download a Worker script.

- List Worker scripts
- Download a Worker script
- Upload a Worker module

## Challenges Tray.ai solves

### Keeping Cloudflare credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Cloudflare credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Cloudflare API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Cloudflare API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Cloudflare?

Yes. Tray.ai connects to Cloudflare through the HTTP Connector, which calls the Cloudflare API directly. Any call the Cloudflare API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Cloudflare?

The Cloudflare API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Cloudflare connector?

Cloudflare runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Cloudflare connector from the Cloudflare API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/