Node Types
Every step in a PropellerDeck Workflow is represented by a node. Each node type serves a distinct purpose. Choosing the right node for each step is key to building reliable, maintainable workflows.
Agent Node
An Agent node runs an AI agent with full reasoning capabilities. Use Agent nodes for tasks that require understanding natural language, generating text, or making judgment calls based on context. You can configure each Agent node with its own system prompt, tools, and knowledge. See Workflow Prompts and Knowledge for configuration details.
Function Node
A Function node executes deterministic code. Use Function nodes when you need precise, repeatable logic — such as parsing a JSON payload, validating form fields, transforming data formats, or calling an external API. Function nodes do not use AI reasoning; they run exactly what you define.
Conversational Node
A Conversational node enables interactive, multi-turn dialogue within a workflow. When execution reaches this node, it opens a chat interface where the user and the AI exchange messages over several turns before the workflow continues. Use Conversational nodes when you need to gather detailed input or clarify ambiguous requirements.
Decision Node
A Decision node branches the workflow based on conditions you define. When execution reaches this node, it evaluates one or more rules against the current data and routes to the appropriate downstream node. Use Decision nodes to handle different cases — for example, routing high-priority tickets differently from low-priority ones.
Human Node
A Human node pauses workflow execution and waits for a person to take action — reviewing output, approving a step, or providing additional input. The workflow resumes only after the human responds. Use Human nodes for compliance checkpoints or quality review steps.
System Nodes: Input and Output
System nodes mark the boundaries of your workflow. The Input node is the entry point — it receives data that starts the workflow. The Output node is the exit point — it delivers the final result. Every workflow must have at least one Input and one Output node.
For guidance on connecting these nodes together, see Connecting Nodes.