Workflow node kinds (registry)
Synced from bicycle-studio-api
Source: _generated/workflow-kinds.md in the local directory context-collection (not yet on origin/platform), synced 2026-09-26. Do not edit this page here; change the source and run yarn sync:studio.
That source is itself generated (by arch/context-collection/build.py from data-app-runtime b21a421 bicycle_workflow_core/spec/kinds.json + registry.py RUNNABLE_V1); change its source and re-run its build.
| kind | spec status | runs on the workflow-runner | why not |
|---|---|---|---|
query | v1 | yes | |
sql | v1 | yes | |
python | v1 | no | python does not run in this build; write a code function and call it with a function node |
llm | v1 | yes | |
function | v1 | yes | |
snapshot | v1 | yes | |
action | v1 | yes | |
source | v1 | no | source uploads are v1.5 |
input | v1 | no | input tables need the table editor and its versions; not in this build |
detect | draft | no | detect runs on agent-service through the remote runner path, which v1 cuts; run it from a panel, chat or MCP |
explain | draft | no | explain runs on agent-service through the remote runner path, which v1 cuts; run it from a panel, chat or MCP |
classify | draft | yes |
status: draft with runs = yes (classify) means it runs but its spec may still change. There is no agent kind: call an agent-kind function from a function node. detect / explain validate and plan but are cut from v1: use Detect and Explain from a panel, chat or MCP (07-detect-explain.md).