Tricentis qTest icon

CONNECT APP

Build with Tricentis qTest

Scalable test management, operations, and analytics to centralize testing and orchestrate quality at speed, with visibility throughout the software development lifecycle.

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",
  },
})

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.

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",
  },
})

EVENTS

Tricentis qTest triggers

Event sources your backend can deploy for users and receive through a webhook.

No Tricentis qTest triggers are available yet.

REFERENCE

App details

Reference metadata for the Tricentis qTest connector in the Pipedream registry.

App slug
tricentis_qtest
Authentication
OAuth
Categories
Web & App Development
Actions
7
Triggers
0
API proxy
Available