Productivity · Integration

Rally

Add Rally to your product for your customers, and give your AI agents governed access to it.

Rally, Broadcom's agile planning tool and formerly CA Agile Central, models delivery as work items: user stories and defects, the tasks beneath them, the iterations and releases they are committed to, and the portfolio items they roll up into. The hierarchy is the point, because a story means little without its parent feature and the iteration it was committed to, and that is what every burndown and portfolio view is built on. Scoping is the trap. Everything lives inside a workspace and a project, and a query that omits the project scope answers confidently for the wrong team. Custom fields are added per workspace, so field mapping is configuration per customer. fastn keeps the credentials per tenant and tracks the API.

Start freeBook a demo

In your product

Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.

Let each customer connect their own Rally subscription so your product reads and writes work items in the workspace and project they nominate.

Create a defect from something your product detected, with the iteration and owner already set so nobody triages it twice.

Roll a story up to its parent feature so your reporting matches what the customer's own portfolio view shows.

Scope every query to a workspace and project, because an unscoped Rally query quietly answers for the wrong team.

For your AI agents

Governed, audited access for the agents you build, through the MCP server.

An agent reports what is committed to the current iteration and what has already slipped.

An agent creates or updates a story or defect within scoped permissions, with the change attributed.

An agent reads a story's parent feature and iteration before it says who should pick the work up.

Example prompt

What is still open in the current iteration for this project, and which defects are blocking it?

Set up Rally in 4 steps

  1. 01Enable the Rally connector in your fastn dashboard.
  2. 02Have each customer authorise their own Rally subscription with an API key scoped to the workspaces your product touches.
  3. 03Map the work item types, custom fields, iterations and the workspace and project every query must be scoped to.
  4. 04Call it from your product and expose the same connection to your agents through the MCP gateway.

Why teams use the Rally integration

What you get by embedding it with fastn instead of building it yourself.

  • Ship a Rally integration without building it. Your customers connect their own Rally account inside your product and work their work items, assignees and due dates there, with no per-customer code on your side.
  • Handle the part that actually costs time: every team configures its own fields, statuses and workflow stages. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Rally update is not your on-call problem.
  • One integration serves your product and your agents. The same governed Rally connection powers in-product features and gives AI agents scoped, audited access, so you keep work items in step with what happens in your product without wiring it twice.

Used by these teams

HR & People OpsOperations

Compare with

JiraLinear

Works well with

Azure DevOps

Often used alongside

Tools the same teams tend to run next to Rally, across other categories.

NotionBoxDocusignAWS Simple Storage Service

Rally integration FAQ

How do I add a Rally integration to my product?

Enable the Rally connector in your fastn dashboard, then let each customer authenticate their own Rally account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Rally client code in your app and no per-customer branch in your codebase. Setup is 4 steps.

Do my customers each connect their own Rally account?

Yes. Every connection is scoped to the individual customer, so each authorises their own Rally account and only ever sees their own work items, assignees and due dates. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.

Can AI agents use this Rally integration?

Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports what is committed to the current iteration and what has already slipped.

Who maintains the Rally integration?

fastn does. When Rally changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.

Can my product create and update work in Rally automatically?

Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in Rally can trigger your workflows in return.

Does it adapt to each team's own Rally setup?

Yes. However a team has configured Rally, whether that is custom fields, statuses and workflow stages or its own calendars and working hours, those are mapped per customer, so an unusual setup works without custom code from you.

What can I build with the Rally integration?

A common starting point: let each customer connect their own Rally subscription so your product reads and writes work items in the workspace and project they nominate. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.

How much does the Rally integration cost?

It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Rally does not change your per-connector cost. You can start free with 3 connected accounts.

Add Rally to your product

Start free with 3 connected accounts. No sales call required, and no per-customer integration code.

Start freeRead the docs
← All integrations