# Netlify integrations: sites, deploys and forms

> Create a site, create a deploy and create environment variables in Netlify, and start a workflow when Netlify sends “Deploy started”.

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

## Overview

Netlify is a web hosting and deployment platform that builds sites from Git, serves them on a global CDN, and handles forms and serverless functions. Tray.ai connects to Netlify through the HTTP Connector, so your workflows can call the Netlify API alongside the rest of your stack.

## Use cases

### Sites

Read, create, update, and delete sites in Netlify from any Tray.ai workflow. The Netlify API covers calls such as list sites and get a site.

- List sites
- Get a site
- Create a site

### Deploys

Read, create, and update deploys in Netlify from any Tray.ai workflow. The Netlify API covers calls such as create a deploy and get a deploy.

- Create a deploy
- Get a deploy
- Restore a deploy

### Forms

Read and delete forms in Netlify from any Tray.ai workflow. The Netlify API covers calls such as list forms and delete a form.

- List forms
- Delete a form

### Submissions

Read, update, and delete submissions in Netlify from any Tray.ai workflow. The Netlify API covers calls such as list submissions and mark submission as spam.

- List submissions
- Mark submission as spam
- Delete a submission

### Environment variables

Read, create, update, and delete environment variables in Netlify from any Tray.ai workflow. The Netlify API covers calls such as list environment variables and create environment variables.

- List environment variables
- Create environment variables
- Update an environment variable

### Hooks

Read, create, and delete hooks in Netlify from any Tray.ai workflow. The Netlify API covers calls such as list hooks and create a hook.

- List hooks
- Create a hook
- Delete a hook

## Challenges Tray.ai solves

### Keeping Netlify 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 Netlify 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 Netlify 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 Netlify 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 Netlify?

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

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

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

### Can I get a dedicated Netlify connector?

Netlify runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Netlify connector from the Netlify 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/