Skip to content
Rally logo

Connectors / Operations · HTTP Connector

Automate Rally with Tray.ai

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.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.

See all connectors

What can you do with Rally on Tray.ai?

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.

  • When Rally sends “Defect closed”, resolve the linked ticket in your help desk and tell the customer.
  • Create a defect in Rally when support escalates a confirmed bug from your help desk.
  • Post new work to the team's channel in your team chat when Rally sends “User story created”.
Connects through
HTTP Connector
Authentication
An API key in a request header or basic authentication
Base URL
https://rally1.rallydev.com/slm/webservice/v2.0

Set it up

Connect Rally to Tray.ai

Each step uses Rally's own API details, from its documentation.

Step 1

Save Rally's API key

Save the key as a Tray.ai authentication. The HTTP Client puts it in the request header, read from $.auth. The key stays out of the workflow and out of the logs.

Step 2

Point the HTTP Client at the API

Add an HTTP Client step and use https://rally1.rallydev.com/slm/webservice/v2.0 as the base URL. Or paste a cURL example from Rally's API docs, and Tray.ai fills in the method, URL, and headers.

Step 3

Start with “Get a defect”

It's one of 12 documented actions, under Defects. The response comes back as data the next step can map into your other apps.

Step 4

Start workflows from Rally events

Give Rally the URL of a Tray.ai webhook trigger. “User story created” can then start a workflow, and so can 3 other events.

What the Rally API covers

4 resources and 12 documented actions, each one a call the HTTP Connector can make from a Tray.ai workflow. Connecting it takes a few clicks: here's how.

Defects

  • Create a defect
  • Get a defect
  • Update a defect
  • Delete a defect
  • Query defects

User stories

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

Projects

  • Query projects
  • Get a project

Workspaces

  • Get a subscription
  • List workspaces

Events Rally can send to a Tray.ai webhook trigger

  • User story created
  • Defect renamed
  • Defect closed
  • Discussion entry added

Checked against Rally's own documentation on 2026-10-22

techdocs.broadcom.com/us/en/ca-enterprise-software/valueo…

Frequently asked questions

What can a Tray.ai workflow do in Rally?

+

The Rally API documents 12 actions across 4 resources (Defects, User stories, Projects, Workspaces). For example: Create a defect; Query user stories; Query projects. A workflow can make any documented call through the HTTP Connector.

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.

Which Rally events can start a Tray.ai workflow?

+

Rally sends 4 events to a webhook URL, for example: User story created; Defect renamed; Defect closed; Discussion entry added. A Tray.ai webhook trigger receives them and starts a workflow.

See Rally working against your stack.

We'll walk through a tailored demo with your systems plugged in.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.