Yutori ACTION
Get Research Task Result
Fetch the current status and result of a research task started with Run Research Task. Place a Delay step (15 minutes recommended) before this action to give the task time to complete. Research tasks typically take 5–15 minutes. If the task is still running, the step returns the current status — re-run or increase the delay if needed. See the documentation
- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Yutori account once, then configure and run Get Research Task Result 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: "yutori-get-research-task-result",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
yutori: { authProvisionId: "apn_xxxxxxx" },
taskId: "Task ID",
},
})
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": "yutori-get-research-task-result",
"configured_props": {
"yutori": { "authProvisionId": "apn_xxxxxxx" },
"taskId": "Task ID"
}
}'// 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": "yutori",
},
},
},
)
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: "yutori-get-research-task-result",
arguments: {
taskId: "Task ID",
},
})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 |
|---|---|---|
taskId Task ID | string | The task ID returned by the Run Research Task step, e.g. {{steps.run_research_task.$return_value.task_id}} Required |
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
- yutori-get-research-task-result
- Version
- 0.0.2
- App
- Yutori
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗