Testmo ACTION
Create Automation Run
Creates a new automation run in a target project in preparation for adding threads and test results. See the documentation
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Testmo account once, then configure and run Create Automation Run 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: "testmo-create-automation-run",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
testmo: { authProvisionId: "apn_xxxxxxx" },
projectId: "Project Id",
name: "Name",
},
})
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": "testmo-create-automation-run",
"configured_props": {
"testmo": { "authProvisionId": "apn_xxxxxxx" },
"projectId": "Project Id",
"name": "Name"
}
}'// 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": "testmo",
},
},
},
)
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: "testmo-create-automation-run",
arguments: {
projectId: "Project Id",
name: "Name",
},
})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 the target project. Required Dynamic |
name Name | string | Name of the new automation run. Required |
source Source | string | Name of the source for the new automation run. If this source does not already exist in the target project, Testmo automatically creates a new one. It is recommended to keep source names short. Good examples are backend, frontend or mobile-iphone. Required Dynamic |
config Config | string | Name of the configuration for the new automation run. Optional |
configId Config Id | string | ID of the configuration for the new automation run. If both config and configId are specified, configId is given precedence. Optional |
milestone Milestone | string | Name of the milestone for the new automation run. Optional |
milestoneId Milestone Id | string | ID of the milestone for the new automation run. If both milestone and milestoneId are specified, milestoneId is given precedence. Optional Dynamic |
tags Tags | string[] | List of tags for the new automation run. If a milestone in the same project has one or more matching automation tags, the new automation run is automatically linked to that milestone (unless milestone or milestoneId is also specified). Optional |
artifacts Artifacts | string[] | List of externally stored test artifacts to link to the new automation run (such as log files, screenshots or test data). See de documentation for details Optional |
fields Fields | string[] | List of fields to attach to the new automation run (such as environment variables, errors or terminal output). See de documentation for details Optional |
links Links | string[] | List of links to attach to the new automation run (such as a link back to the build in the CI tool that triggered the tests). See de documentation for details Optional |
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
- testmo-create-automation-run
- Version
- 0.0.4
- App
- Testmo
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗