View as Markdown
Tricentis qTest icon

Tricentis qTest ACTION

Get Requirement

Get full details of a specific requirement by ID. Use List Requirements to find the requirement ID. Example: projectId: 1, requirementId: "101" → returns {id: 101, name: "User can log in", properties: [{field_id: 3, field_value: "High"}]}. 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 Get Requirement 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-get-requirement",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    tricentis_qtest: { authProvisionId: "apn_xxxxxxx" },
    projectId: "Project ID",
    requirementId: "Requirement ID",
  },
})

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.

Get Requirement 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
requirementId Requirement ID string
The ID of a requirement. Use the List Requirements action to retrieve available requirement IDs.
Required

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-get-requirement
Version
0.0.3
App
Tricentis qTest
Authentication
OAuth
Read-only
Yes
Destructive
No
Open world
Yes