HARPA AI ACTION
Run AI Command
Run an AI command. See the documentation
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's HARPA AI account once, then configure and run Run AI Command 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: "harpa_ai-run-ai-command",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
harpa_ai: { authProvisionId: "apn_xxxxxxx" },
url: "URL",
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": "harpa_ai-run-ai-command",
"configured_props": {
"harpa_ai": { "authProvisionId": "apn_xxxxxxx" },
"url": "URL",
"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": "harpa_ai",
},
},
},
)
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: "harpa_ai-run-ai-command",
arguments: {
url: "URL",
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 |
|---|---|---|
url URL | string | the page to run the AI command over Required |
name Name | string | A command name to execute such as Summary Optional |
inputs Inputs | string[] | An array of Strings, each one passed down into command in place of the user input. Inputs are used to bypass waiting for the user input in multi-step commands. For example [ "REPORT", "DONE" ] for the Summary command. Optional |
resultParam Result Param | string | A HARPA {{parameter}} to interpret as the command result. By default is set to "message" to take the last chat message. Supports dot notation, e.g. "g.data.email". Refer to AI Commands Guide for more details. Optional |
node Node | string | A target Node ID which should run the command. If omitted, the first available Node will be used. Optional |
timeout Timeout | string | Synchronous action execution timeout Optional |
resultsWebhook Results Webhook | string | An asynchronous webhook URL to send the results to upon completion Optional |
connection Connection | string | The title or ID of AI connection to use for AI actions. If not specified or connection not found, default connection is used. 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
- harpa_ai-run-ai-command
- Version
- 0.0.2
- App
- HARPA AI
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗