Tricentis qTest ACTION
Create Requirement
Create a new requirement under a parent module in a qTest project. Use List Project ID Options for the project ID, List Modules for the parent module ID, and List Requirement Fields to discover field IDs for the Properties parameter. Example:
projectId: 1, parentId: "10", requirementName: "User can reset password", properties: "[{\"field_id\": 3, \"field_value\": \"1\"}]" → returns {id: 103, name: "User can reset password", ...}. See the documentation- Action
- Writes data
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Tricentis qTest account once, then configure and run Create 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-create-requirement",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
tricentis_qtest: { authProvisionId: "apn_xxxxxxx" },
projectId: "Project ID",
parentId: "Parent ID",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "tricentis_qtest-create-requirement",
"configured_props": {
"tricentis_qtest": { "authProvisionId": "apn_xxxxxxx" },
"projectId": "Project ID",
"parentId": "Parent ID"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "tricentis_qtest",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "tricentis_qtest-create-requirement",
arguments: {
projectId: "Project ID",
parentId: "Parent ID",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| 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 |
parentId Parent ID | string | The ID of the parent module which will contain the newly created requirement. Use the List Modules action to retrieve available module IDs. Required |
requirementName Requirement Name | string | The name of the new requirement Required |
properties Properties | string | A JSON array of field properties to set on the record. Use List Requirement Fields to discover requirement field IDs, or List Defect Fields to discover defect field IDs. Example: [{"field_id": 3, "field_value": "1"}] 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-create-requirement
- Version
- 1.0.0
- App
- Tricentis qTest
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗