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. See the documentationWritev0.0.2 -
Get Defect
actionGet details of a defect. See the documentationRead-onlyv0.0.2 -
Get Requirement
actionGet details of a requirement. See the documentationRead-onlyv0.0.2 -
List Project ID Options
actionRetrieves available options for the Project ID field.Read-onlyv0.0.1 -
Submit Defect
actionSubmit a new defect. See the documentationWritev0.0.2 -
Update Defect
actionUpdate a defect. See the documentationWritev0.0.2 -
Update Requirement
actionUpdate a requirement. See the documentationWritev0.0.2
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
- 7
- Triggers
- 0
- API proxy
- Available