Can I use Pipedream as a CLI?

Yes. KosmoKrator exposes a Pipedream CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Pipedream through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Pipedream tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Pipedream credentials stored?

Pipedream credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Pipedream MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Pipedream CLI for AI Agents

Use the Pipedream CLI from KosmoKrator to call Pipedream tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

Pipedream CLI Setup

Pipedream can be configured headlessly with `kosmokrator integrations:configure pipedream`.

Install, configure, and verify

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure pipedream --set access_token="$PIPEDREAM_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor pipedream --json
kosmokrator integrations:status --json

Credentials

Authentication type: Bearer token bearer_token. Configure credentials once, then reuse the same stored profile from scripts, coding CLIs, Lua, and MCP.

Key	Env var	Type	Required	Label
`access_token`	`PIPEDREAM_ACCESS_TOKEN`	Secret `secret`	yes	Access Token
`url`	`PIPEDREAM_URL`	URL `url`	no	API Base URL

Command Patterns

The generic command is stable across every integration. The provider shortcut is shorter for humans.

Generic CLI call

kosmo integrations:call pipedream.pipedream_list_workflows '{"page":1,"limit":1}' --json

Provider shortcut

kosmo integrations:pipedream pipedream_list_workflows '{"page":1,"limit":1}' --json

Discovery

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

Discovery commands

kosmo integrations:docs pipedream --json
kosmo integrations:docs pipedream.pipedream_list_workflows --json
kosmo integrations:schema pipedream.pipedream_list_workflows --json
kosmo integrations:search "Pipedream" --json
kosmo integrations:list --json

Automation Contexts

The same configured command surface works in these environments. The command does not change unless the host wrapper, credentials, or permissions change.

CI Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status. Cron Jobs Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config. Shell Scripts Call integration functions from shell scripts with stable JSON input and output. Headless Automation Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers. Coding Agents Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

CLI Functions

Every function below can be called headlessly. Commands are highlighted, copyable, and scroll horizontally when payloads are long.

`pipedream.pipedream_list_workflows`

List automation workflows in Pipedream. Returns a paginated list of workflows with their IDs, names, and statuses.

Read read

Parameters: page, limit

Generic call

kosmo integrations:call pipedream.pipedream_list_workflows '{"page":1,"limit":1}' --json

Shortcut

kosmo integrations:pipedream pipedream_list_workflows '{"page":1,"limit":1}' --json

`pipedream.pipedream_get_workflow`

Get details of a specific Pipedream workflow by ID, including its configuration, steps, and current status.

Read read

Parameters: id

Generic call

kosmo integrations:call pipedream.pipedream_get_workflow '{"id":"example_id"}' --json

Shortcut

kosmo integrations:pipedream pipedream_get_workflow '{"id":"example_id"}' --json

`pipedream.pipedream_list_components`

List available Pipedream components (actions, triggers, etc.). Components are reusable building blocks for connecting to third-party APIs.

Read read

Parameters: type, limit

Generic call

kosmo integrations:call pipedream.pipedream_list_components '{"type":"example_type","limit":1}' --json

Shortcut

kosmo integrations:pipedream pipedream_list_components '{"type":"example_type","limit":1}' --json

`pipedream.pipedream_get_component`

Get details of a specific Pipedream component by app and component key. Returns the component configuration, props, and version info.

Read read

Parameters: app, id

Generic call

kosmo integrations:call pipedream.pipedream_get_component '{"app":"example_app","id":"example_id"}' --json

Shortcut

kosmo integrations:pipedream pipedream_get_component '{"app":"example_app","id":"example_id"}' --json

`pipedream.pipedream_list_connected_accounts`

List connected third-party accounts in Pipedream. These are the OAuth-connected accounts used by workflows to interact with external services.

Read read

Parameters: page, limit

Generic call

kosmo integrations:call pipedream.pipedream_list_connected_accounts '{"page":1,"limit":1}' --json

Shortcut

kosmo integrations:pipedream pipedream_list_connected_accounts '{"page":1,"limit":1}' --json

`pipedream.pipedream_list_triggers`

List event triggers for a specific Pipedream workflow. Triggers define the events that cause a workflow to run.

Read read

Parameters: workflow_id

Generic call

kosmo integrations:call pipedream.pipedream_list_triggers '{"workflow_id":"example_workflow_id"}' --json

Shortcut

kosmo integrations:pipedream pipedream_list_triggers '{"workflow_id":"example_workflow_id"}' --json

`pipedream.pipedream_get_current_user`

Get the currently authenticated Pipedream user profile, including name, email, and workspace details.

Read read

Parameters: none

Generic call

kosmo integrations:call pipedream.pipedream_get_current_user '{}' --json

Shortcut

kosmo integrations:pipedream pipedream_get_current_user '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

pipedream.pipedream_list_workflows 2 parameters

Schema command

kosmo integrations:schema pipedream.pipedream_list_workflows --json

Parameter	Type	Required	Description
`page`	integer	no	Page number for pagination (default: 1).
`limit`	integer	no	Number of workflows to return per page (default: 25, max: 100).

pipedream.pipedream_get_workflow 1 parameters

Schema command

kosmo integrations:schema pipedream.pipedream_get_workflow --json

Parameter	Type	Required	Description
`id`	string	yes	The workflow ID.

pipedream.pipedream_list_components 2 parameters

Schema command

kosmo integrations:schema pipedream.pipedream_list_components --json

Parameter	Type	Required	Description
`type`	string	no	Component type filter. Common values: "action", "trigger". Omit to list all types.
`limit`	integer	no	Number of components to return per page (default: 25, max: 100).

pipedream.pipedream_get_component 2 parameters

Schema command

kosmo integrations:schema pipedream.pipedream_get_component --json

Parameter	Type	Required	Description
`app`	string	yes	The app slug (e.g., "slack", "github", "google_sheets").
`id`	string	yes	The component key or ID (e.g., "send-message").

pipedream.pipedream_list_connected_accounts 2 parameters

Schema command

kosmo integrations:schema pipedream.pipedream_list_connected_accounts --json

Parameter	Type	Required	Description
`page`	integer	no	Page number for pagination (default: 1).
`limit`	integer	no	Number of accounts to return per page (default: 25, max: 100).

pipedream.pipedream_list_triggers 1 parameters

Schema command

kosmo integrations:schema pipedream.pipedream_list_triggers --json

Parameter	Type	Required	Description
`workflow_id`	string	yes	The workflow ID to list triggers for.

pipedream.pipedream_get_current_user 0 parameters

Schema command

kosmo integrations:schema pipedream.pipedream_get_current_user --json

Parameter	Type	Required	Description
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.