View as Markdown
Tricentis qTest icon

Tricentis qTest ACTION

List Requirements

List requirements in a qTest project. Use this to find requirement IDs to use when getting or updating a specific requirement. If the response contains a full page of results, increment the Page parameter and call again to retrieve the next page. Example: projectId: 1, page: 1 → returns [{id: 101, name: "User can log in"}, {id: 102, name: "Password reset via email"}]. See the documentation
  • Action
  • Read only
  • OAuth
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's Tricentis qTest account once, then configure and run List Requirements from your backend or agent.

import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const result = await pd.actions.run({
  id: "tricentis_qtest-list-requirements",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    tricentis_qtest: { authProvisionId: "apn_xxxxxxx" },
    projectId: "Project ID",
    page: 10,
  },
})

console.log(result)

SCHEMA

Inputs

Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.

List Requirements inputs
Property Type Description
projectId Project ID string
The ID of a project, e.g. 1. Use the List Project ID Options action to retrieve available project IDs.
Required
page Page integer
Page number for paginated results (1-based)
Optional

REFERENCE

Tool details

Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.

Registry key
tricentis_qtest-list-requirements
Version
0.0.1
App
Tricentis qTest
Authentication
OAuth
Read-only
Yes
Destructive
No
Open world
Yes