---
title: "List node templates"
method: GET
path: "/hub/nodes"
tags: ["Nodes"]
---

# List node templates

`GET /hub/nodes`

Retrieves a list of node templates, optionally filtered by collection and type

## Path parameters

- `collection_topic` string, required

## Response `200`

Nodes retrieved successfully

- ListNodesResponse
  - `results` object[]
    - `subject` string — Subject identifier for the node
    - `data` NodeData
      - `id` string — Unique identifier for the node
      - `name` string — Name of the node
      - `description` string — Description of the node
      - `node_type` 'function' | 'flow' | 'condition' | 'map' | 'eval' | 'integration' — ## Node Types ### 1. `function` **Definition**: A **Hydra function node** used to provide a *subject* or perform a custom computation. It encapsulates reusable logic defined within the Hydra platform. ### 2. `flow` **Definition**: A node that **invokes another flow**, either **synchronously** or **asynchronously**, enabling flow modularization and reuse. ### 3. `condition` **Definition**: A **branching node** that evaluates a condition to determine the **flow of execution**, similar to `if`/`else` logic in programming. ### 4. `map` **Definition**: A **data transformation node** used to **reshape or remap the payload**, allowing the flow to adapt the structure of data as it progresses. ### 5. `eval` **Definition**: Executes **simple JavaScript code** to dynamically **evaluate expressions**, perform calculations, or manipulate data inline within the flow. ### 6. `integration` **Definition**: Similar to a `function` node, but specifically tied to **predefined APIs**. It uses an HTTP-like interface and references **a known set of external services** managed by the platform.
      - `subject` string — Subject identifier for function or flow node types
      - `payload` unknown
      - `response_map` unknown
      - `options` NodeOptions — Node execution options
        - `flat_map` boolean — Whether to flatten the response
        - `backoff_ms` integer — Backoff duration in milliseconds - how long to wait before next attempt. Applies to function and flow nodes only.
        - `timeout` integer — Timeout duration in milliseconds. Applies to function and flow nodes only.
        - `attempts` integer — Number of retry attempts. Applies to function and flow nodes only.
        - `ignore_response_codes` integer[] — List of HTTP response codes to ignore. Applies to function nodes only.
      - `await` boolean — Whether to wait for completion nad return the result
    - `modified` integer — Timestamp of last modification
  - `results_total` integer — Total number of results

## Other responses

- `400` — Bad request

---

[API](https://skmtc.net/quivaworks/apis/quiva-ai-gateway-3.md) · [All operations](https://skmtc.net/quivaworks/apis/quiva-ai-gateway-3/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/quivaworks/quiva-ai-gateway-3/revisions/872d6eb3b682/schema)