View as Markdown
Komos icon

Komos ACTION

Queue Task Run

Queue a saved Komos task run with optional inputs. See the documentation
  • Action
  • Writes data
  • API key
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's Komos account once, then configure and run Queue Task 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: "komos-queue-task-run",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    komos: { authProvisionId: "apn_xxxxxxx" },
    taskId: "Task ID",
    inputs: "Task Inputs",
  },
})

console.log(result)

SCHEMA

Inputs

Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.

Queue Task Run inputs
Property Type Description
taskId Task ID string
The Komos task ID to run. Example: 3c90c3cc-0d44-4b50-8888-8dd25736052a. Use the List Tasks action to discover task IDs.
Required
inputs Task Inputs object
Optional input values that match the saved Komos task input schema. Must be a JSON object, for example { "userId": "u123", "options": { "verbose": true } }.
Optional
clientRequestId Client Request ID string
Optional idempotency key. Reusing the same value returns the existing run. Example: client-req-20240501-xyz.
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
komos-queue-task-run
Version
0.0.1
App
Komos
Authentication
API key
Read-only
No
Destructive
No
Open world
Yes