Strale ACTION
Search and Execute
Describe what you need in plain language — Strale picks the best capability and executes it in one step. Use this when you don't know the exact capability slug. If you already know the slug, use Execute Capability instead; if you only want to discover matches without running anything, use Search Capabilities. See the documentation
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Strale account once, then configure and run Search and Execute 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: "strale-search-and-execute",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
strale: { authProvisionId: "apn_xxxxxxx" },
task: "Task",
inputs: "Inputs",
},
})
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": "strale-search-and-execute",
"configured_props": {
"strale": { "authProvisionId": "apn_xxxxxxx" },
"task": "Task",
"inputs": "Inputs"
}
}'// 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": "strale",
},
},
},
)
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: "strale-search-and-execute",
arguments: {
task: "Task",
inputs: "Inputs",
},
})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 |
|---|---|---|
task Task | string | A natural-language description of what you need (e.g. "verify a Swedish company", "validate this VAT number"). Required |
inputs Inputs | object | Input parameters for the capability as a JSON object (e.g. { "vat_number": "SE556677889901" } or { "email": "ops@example.com" }). The required fields depend on the capability being called. Optional |
maxPriceCents Max Price (cents) | integer | Maximum price in euro cents you are willing to pay per execution. Optional |
dryRun Dry Run | boolean | If true, validates the request and returns the matched capability without executing or charging. 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
- strale-search-and-execute
- Version
- 0.0.2
- App
- Strale
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗