# DevCycle integrations: projects and features

> Create a project, create a feature and create an environment in DevCycle. Connect DevCycle to the rest of your developer tools stack with Tray.ai.

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

## Overview

DevCycle is a feature flag platform for releasing features gradually, targeting audiences, running experiments, and switching features on or off per environment. Tray.ai connects to DevCycle through the HTTP Connector, so your workflows can call the DevCycle API alongside the rest of your stack.

## Use cases

### Projects

Read, create, update, and delete projects in DevCycle from any Tray.ai workflow. The DevCycle API covers calls such as list projects and get a project.

- List projects
- Get a project
- Create a project

### Features

Read, create, and update features in DevCycle from any Tray.ai workflow. The DevCycle API covers calls such as list features and get a feature.

- List features
- Get a feature
- Create a feature

### Environments

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

- List environments
- Create an environment
- Update an environment

### Audiences

Read, create, update, and delete audiences in DevCycle from any Tray.ai workflow. The DevCycle API covers calls such as list audiences and create an audience.

- List audiences
- Create an audience
- Update an audience

### Variables

Read, create, and update variables in DevCycle from any Tray.ai workflow. The DevCycle API covers calls such as list variables and create a variable.

- List variables
- Create a variable
- Update a variable

### Webhooks

Read, create, update, and delete webhooks in DevCycle from any Tray.ai workflow. The DevCycle API covers calls such as list webhooks and create a webhook.

- List webhooks
- Create a webhook
- Update a webhook

## Challenges Tray.ai solves

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

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

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

The DevCycle API uses 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 DevCycle connector?

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