CONNECT APP
Build with Tricentis qTest
Web & App Development
- OAuth
MCP
Give your agent Tricentis qTest tools
Every Tricentis qTest action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Tricentis qTest account for each tool call — you store no tokens.
// 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()
// e.g. run Create Requirement:
const result = await mcp.callTool({
name: "tricentis_qtest-create-requirement",
arguments: {
projectId: "Project ID",
parentId: "Parent ID",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"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",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Create Requirement:
result = await session.call_tool("tricentis_qtest-create-requirement", {
"projectId": "Project ID",
"parentId": "Parent ID",
})API PROXY
Call the Tricentis qTest API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Tricentis qTest API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://api.example.com/v1/me",
})
// Any allowed Tricentis qTest endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://api.example.com/v1/me
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkuZXhhbXBsZS5jb20vdjEvbWU?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Tricentis qTest actions from your backend
Connect a user's Tricentis qTest account once, then run Create Requirement on their behalf from your own code — TypeScript, Python, or plain HTTP.
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",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="tricentis_qtest-create-requirement",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"tricentis_qtest": {"authProvisionId": "apn_xxxxxxx"},
"projectId": "Project ID",
"parentId": "Parent ID",
},
)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"
}
}'TOOLS
Tricentis qTest actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Create Requirement
actionCreate 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 documentationWritev1.0.0 -
Get Defect
actionGet full details of a specific defect by ID. Use List Defects to find the defect ID and List Defect Fields to interpret field IDs in the response. Example:projectId: 1, defectId: "201"→ returns{id: 201, properties: [{field_id: 1, field_value: "Login crash"}, {field_id: 2, field_value: "New"}]}. See the documentationRead-onlyv0.0.3 -
Get Requirement
actionGet 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 documentationRead-onlyv0.0.3 -
List Defect Fields
actionList all available fields for defects in a qTest project, including field IDs, types, and allowed values. Use this to discover field IDs before submitting or updating defects. Passfields(e.g.["id", "label", "required"]) to keep only those attributes per field — some fields'allowed_valueslists are long, so omitting them when you only need the field ID/label keeps the response small. Example:projectId: 1→ returns[{id: 1, label: "Summary", attribute_type: "String", required: true}, {id: 2, label: "Status", attribute_type: "String", allowed_values: [{label: "New", value: "1"}], required: true}]. See the documentationRead-onlyv0.0.1 -
List Defects
actionList defects in a qTest project updated after a given start time. Use this to find defect IDs to use when getting or updating a specific defect. If the response contains a full page of results, increment the Page parameter and call again for more. Defaults to defects updated in the last 30 days, and includes only theSummaryproperty per defect to keep the response small — projects with long-running defect logs can return large payloads otherwise, since some properties (like Description) may contain lengthy text. Passfields(e.g.["Summary", "Status"]) to include different or additional named properties instead. Use Get Defect for a defect's full property set. Example:projectId: 1, startTime: "2026-09-01T00:00:00Z"→ returns[{id: 201, properties: [{field_id: 1, field_value: "Login crash"}]}, ...]. See the documentationRead-onlyv0.0.1 -
List Modules
actionList all modules in a qTest project, including nested submodules. Use List Project ID Options for the project ID. Use this to find module IDs to use as the Parent ID in Create Requirement. Example:projectId: 1→ returns[{id: 10, name: "Authentication"}, {id: 11, name: "Checkout"}]. See the documentationRead-onlyv0.0.1 -
List Project ID Options
actionList all qTest projects accessible to the connected account. Use this to find the Project ID required by all other actions. Example: returns[{label: "Acme QA", value: 1}, {label: "Frontend Suite", value: 2}]. See the documentation.Read-onlyv0.0.2 -
List Requirement Fields
actionList all available fields for requirements in a qTest project, including field IDs, types, and allowed values. Use this to discover field IDs before creating or updating requirements. Passfields(e.g.["id", "label", "required"]) to keep only those attributes per field — some fields'allowed_valueslists are long, so omitting them when you only need the field ID/label keeps the response small. Example:projectId: 1→ returns[{id: 3, label: "Priority", attribute_type: "String", allowed_values: [{label: "High", value: "1"}, {label: "Medium", value: "2"}], required: false}]. See the documentationRead-onlyv0.0.1 -
List Requirements
actionList 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 documentationRead-onlyv0.0.1 -
Submit Defect
actionSubmit a new defect in a qTest project. Use List Project ID Options for the project ID and List Defect Fields to discover field IDs and required fields for the Properties parameter. Example:projectId: 1, properties: "[{\"field_id\": 1, \"field_value\": \"Button not clickable\"}, {\"field_id\": 2, \"field_value\": \"1\"}]"→ returns{id: 202, properties: [...]}. See the documentationWritev1.0.0 -
Update Defect
actionUpdate an existing defect in a qTest project. Use List Defects to find the defect ID and List Defect Fields to discover field IDs for the Properties parameter. Example:projectId: 1, defectId: "201", properties: "[{\"field_id\": 2, \"field_value\": \"2\"}]"→ returns the updated defect object. See the documentationWritev1.0.0 -
Update Requirement
actionUpdate ONE existing requirement in a qTest project. Use List Requirements to find the requirement ID and List Requirement Fields to discover field IDs for the Properties parameter. Name is required by the API on every update — resupply the requirement's current name (from Get Requirement) if you only want to change Properties. This tool has no bulk/mass-update mode — before calling it repeatedly to apply the same change across many requirements, confirm the full scope (which requirements, what change) with the user first; do not sweep an entire project's requirements on a single broad instruction. If you ask for that confirmation and don't receive an explicit yes, STOP — do not call this tool anyway. Proceeding without an actual confirmation is exactly the behavior this warning exists to prevent, even if the original instruction sounded broad enough to imply it. This warning is about scope (which/how many requirements), not about calling this tool at all — a single, already-specific instruction (a named requirement ID and field change) needs no extra confirmation. Example:projectId: 1, requirementId: "101", name: "User can log in", properties: "[{\"field_id\": 3, \"field_value\": \"1\"}]"→ returns the updated requirement object. See the documentationWritev1.0.0
EVENTS
Tricentis qTest triggers
Event sources your backend can deploy for users and receive through a webhook.
No Tricentis qTest triggers are available yet.
MULTI-APP
Use Tricentis qTest with other popular apps
Most products don't stop at one integration. Pair Tricentis qTest with the other apps your users rely on, and ship use cases that span both.
- App slug
- tricentis_qtest
- Authentication
- OAuth
- Categories
- Web & App Development
- Actions
- 12
- Triggers
- 0
- API proxy
- Available