Skyvern ACTION
Run Workflow
Trigger a predefined workflow in Skyvern, allowing the execution of complex routines from Pipedream. See the documentation
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Skyvern account once, then configure and run Run Workflow 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: "skyvern-run-workflow",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
skyvern: { authProvisionId: "apn_xxxxxxx" },
workflowId: "Workflow ID",
data: "Data",
},
})
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": "skyvern-run-workflow",
"configured_props": {
"skyvern": { "authProvisionId": "apn_xxxxxxx" },
"workflowId": "Workflow ID",
"data": "Data"
}
}'// 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": "skyvern",
},
},
},
)
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: "skyvern-run-workflow",
arguments: {
workflowId: "Workflow ID",
data: "Data",
},
})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 |
|---|---|---|
workflowId Workflow ID | string | The unique identifier for a workflow Required Dynamic |
data Data | object | The data field is used to pass in required and optional parameters that a workflow accepts. See the documentation for further information. Optional |
webhookCallbackUrl Webhook Callback URL | string | URL where system will send callback once it finishes executing the workflow run. 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
- skyvern-run-workflow
- Version
- 0.0.3
- App
- Skyvern
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗