# Nodes (/docs/concepts/nodes)

What nodes are, their categories, and how data flows through them.



Nodes are the building blocks of a workflow. Each node performs one action - fetch a price, call an AI model, send a message, execute a swap.

Anatomy [#anatomy]

Every node has:

* **Input port** (left) - receives data from upstream nodes
* **Output port** (right) - passes results to downstream nodes
* **Config panel** - opens on click, contains node-specific settings
* **Status indicator** - shows idle, running, success, or error during execution

Categories [#categories]

| Category  | Nodes                                                                                        | Purpose                                                                                                |
| --------- | -------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
| AI        | OpenRouter                                                                                   | LLM inference (GPT, Claude, Gemini, etc.)                                                              |
| DeFi      | Jupiter, Raydium, Pump.fun, Orca, Meteora, Kamino, Sanctum, DFlow, Drift, Phoenix            | Swaps, quotes, liquidity, lending, perps trading                                                       |
| Data      | Birdeye, Helius, Pyth, CoinGecko, Polymarket, Dune, DefiTheOdds                              | Prices, on-chain data, analytics                                                                       |
| Messaging | Telegram, Discord                                                                            | Send alerts and notifications                                                                          |
| Utility   | HTTP, x402, Balance, Storage, Log, Delay, Transform, Merge, Code, Filter, Condition, ForEach | Requests, paid requests, wallet reads, storage, data shaping, merging, control flow, batched iteration |

Data flow [#data-flow]

Each node outputs a JSON object. Downstream nodes reference upstream outputs using template expressions:

```
{responseName.field.path}
```

For example, if a Birdeye node outputs `{ data: { value: 150.23 } }`, a downstream Log node can reference it as `{birdeyeResponse.data.value}`.

Status states [#status-states]

| State   | Meaning                                        |
| ------- | ---------------------------------------------- |
| Idle    | Not yet executed in this run                   |
| Running | Currently processing                           |
| Success | Completed without error                        |
| Error   | Failed - check the error message in run detail |

Next steps [#next-steps]

* [Edges](/docs/concepts/edges) - connecting nodes together
* [Node Reference](/docs/nodes) - detailed docs for each node type