# Egnyte integrations: files and folders

> Upload a file and create a folder in Egnyte, and start a workflow when Egnyte sends “File added”.

**Canonical page:** https://tray.ai/connectors/egnyte-integrations/
**Categories:** Documents and e-signature
**Connects through:** HTTP Connector

## Overview

Egnyte is a content collaboration and governance platform where companies store, share, and secure business files across cloud and on-premises storage. Tray.ai connects to Egnyte through the HTTP Connector, so your workflows can call the Egnyte API alongside the rest of your stack. API access comes through Egnyte's partner program or API plan, so you need approved credentials first.

## Use cases

### Files

Read and create files in Egnyte from any Tray.ai workflow. The Egnyte API covers calls such as upload a file and download a file.

- Upload a file
- Download a file
- Lock a file

### Folders

Read and create folders in Egnyte from any Tray.ai workflow. The Egnyte API covers calls such as create a folder and list folder contents.

- Create a folder
- List folder contents
- Get folder statistics

### Files and folders

Create, update, and delete files and folders in Egnyte from any Tray.ai workflow. The Egnyte API covers calls such as move a file or folder and copy a file or folder.

- Move a file or folder
- Copy a file or folder
- Delete a file or folder

### Webhooks

Read webhooks in Egnyte from any Tray.ai workflow. The Egnyte API covers calls such as register a webhook and list webhooks.

- Register a webhook
- List webhooks

## Challenges Tray.ai solves

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

Yes. Tray.ai connects to Egnyte through the HTTP Connector, which calls the Egnyte API directly. Any call the Egnyte API documents can run as a step in a Tray.ai workflow. API access comes through Egnyte's partner program or API plan, so you need approved credentials first.

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

The Egnyte API uses OAuth 2.0 and 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 Egnyte connector?

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