Nodes Reference

Node types overview

Starships blueprints are graphs of nodes connected by edges. Each node has:

• type: core behavior (e.g. start, code, http_request)
• parameters: configuration for that behavior
• runtime contract: what data it expects on input and what it returns

This page gives you a high-level map of the main node types and links to deeper docs.

Execution nodes

• start: entrypoint; receives the tool or workflow input as ctx.input.
• end: exit; returns a final result. Use the output parameter (full-string template) to shape the returned value.
• code: runs JavaScript/TypeScript-like code with async function main(ctx) { ... }. See nodes/code.
• http_request: performs raw HTTP calls via the HostRuntime (absolute http(s)://... URLs only).
• connector_action: performs connector-backed HTTP calls (base URL + auth + mapping defined by connector_templates). Required for connector-based integrations and for Starships-hosted agent/tool execution flows where the server injects auth and enforces allow/ask/deny policies.
• llm: calls an LLM provider via the host; supports tools/function calling and streaming.
• workflow: runs a nested blueprint.
• tool: executes a nested blueprint provided in ToolParams (it does not perform slug-based tool lookup).

Control-flow and data nodes

• conditional: computes an edgeCondition and routes along matching edges.
• transform: pure data reshaping using JSON-like transforms operations and templates.
• mutate: updates execution state using reducer functions.
• user_prompt: pauses execution and waits for a user choice.

For concrete, code-level examples of how these nodes execute, see packages/autopilot/src/examples in the repo, especially the code-node examples. More detailed node-specific pages will be added incrementally.