# Rally integrations: defects and user stories

> Create a defect in Rally and start a workflow when Rally sends “User story created”. Connect Rally to the rest of your operations stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/rally-integrations/
**Categories:** Operations
**Connects through:** HTTP Connector

## Overview

Rally, from Broadcom, is agile planning software where teams manage user stories, defects, features, iterations and releases across projects and workspaces. Tray.ai connects to Rally through the HTTP Connector, so your workflows can call the Rally API alongside the rest of your stack.

## Use cases

### Defects

Read, create, update, and delete defects in Rally from any Tray.ai workflow. The Rally API covers calls such as create a defect and get a defect.

- Create a defect
- Get a defect
- Update a defect

### User stories

Read user stories in Rally from any Tray.ai workflow. The Rally API covers calls such as query user stories and get a user story.

- Query user stories
- Get a user story
- List child stories

### Projects

Read projects in Rally from any Tray.ai workflow. The Rally API covers calls such as query projects and get a project.

- Query projects
- Get a project

### Workspaces

Read workspaces in Rally from any Tray.ai workflow. The Rally API covers calls such as get a subscription and list workspaces.

- Get a subscription
- List workspaces

### Rally events

Start a Tray.ai workflow the moment something happens in Rally. Rally sends events such as user story created and defect renamed to a Tray.ai webhook trigger.

- User story created
- Defect renamed
- Defect closed

## Challenges Tray.ai solves

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

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

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

The Rally API uses an API key in a request header and basic authentication. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Rally connector?

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