> ## Documentation Index > Fetch the complete documentation index at: https://microstrate-1133-notifications-prefs.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # List workflows > Retrieves a list of workflows, optionally filtered by collection and type ## OpenAPI ````yaml /api-reference/endpoint/hub-flows/openapi.json get /hub/workflows openapi: 3.0.0 info: title: quiva.ai Gateway description: API for managing collections, nodes, and workflows in quiva.ai Hub version: 0.1.0 contact: name: quiva.ai Support servers: - url: https://api.quiva.ai description: Production API server security: - bearerAuth: [] - apiKeyAuth: [] tags: - name: Collections description: Operations related to collections - name: Nodes description: Operations related to nodes - name: Workflows description: Operations related to workflows - name: Oauth description: Oauth configurations and connections paths: /hub/workflows: get: tags: - Workflows summary: List workflows description: >- Retrieves a list of workflows, optionally filtered by collection and type operationId: listWorkflows parameters: - $ref: '#/components/parameters/collectionTopic' - name: filter in: query description: Filter workflows by type. If not specified, all types will be listed required: false schema: type: string enum: - draft - published examples: draft: summary: List only draft workflows value: draft published: summary: List only published workflows value: published responses: '200': description: Workflows retrieved successfully content: application/json: schema: $ref: '#/components/schemas/ListWorkflowsResponse' examples: multipleWorkflows: summary: Multiple workflows returned value: results: - subject: ms.hub.config.workflow.draft.1234567890.98765432 name: DataProcessor description: Processes incoming data config: nodes: - data: id: input name: Input node_type: map payload: data: '{trigger}' edges: [] result: input modified: 1651395678 - subject: ms.hub.config.workflow.draft.1234567890.12345678 name: NotificationSender description: Sends notifications to users config: nodes: - data: id: send name: Send node_type: function subject: quiva-function.send-email payload: to: '{trigger.email}' edges: [] result: send modified: 1651395679 results_total: 2 emptyList: summary: No workflows found value: results: [] results_total: 0 singleWorkflow: summary: Single workflow returned value: results: - subject: ms.hub.config.workflow.1234567890.11111111 name: ProductionWorkflow description: Published production workflow config: nodes: - data: id: process name: Process node_type: function subject: quiva-function.processor payload: {} edges: [] result: process modified: 1651400000 results_total: 1 '400': description: Bad request content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: invalid request components: parameters: collectionTopic: name: collection_topic in: path description: >- The topic is a hash of the name that was used when a collection was created required: true schema: type: string example: '1234567890' schemas: ListWorkflowsResponse: type: object properties: results: type: array items: type: object properties: subject: type: string description: Subject identifier for the workflow name: type: string description: Name of the workflow description: type: string description: Description of the workflow config: $ref: '#/components/schemas/WorkflowConfig' modified: $ref: '#/components/schemas/Modified' results_total: type: integer description: Total number of results ErrorResponse: type: object properties: error: type: string description: Error message WorkflowConfig: type: object properties: nodes: type: array items: type: object properties: data: $ref: '#/components/schemas/NodeData' position: type: object description: Visual position of the node in the workflow editor style: type: object description: Visual styling of the node description: Array of nodes in the workflow edges: type: array items: $ref: '#/components/schemas/Edge' description: Array of edges connecting nodes in the workflow static: type: object description: Static data available to all nodes in the workflow result: type: string description: Expression to determine the final result of the workflow options: type: object properties: run_type: type: string enum: - debounced - ordered description: Execution mode for the workflow order_on: type: string description: Field to order workflow executions by debounce_on: type: string description: Field to debounce workflow executions on debounce_time: type: integer description: Debounce time in milliseconds debounce_max: type: integer description: Maximum debounce time in milliseconds Modified: type: integer description: Timestamp of last modification NodeData: type: object properties: id: type: string description: Unique identifier for the node name: type: string description: Name of the node description: type: string description: Description of the node node_type: type: string enum: - function - flow - condition - map - eval - integration description: >- ## 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: type: string description: Subject identifier for function or flow node types payload: description: Payload data for the node response_map: description: Mapping for response transformation options: $ref: '#/components/schemas/NodeOptions' await: type: boolean description: Whether to wait for completion nad return the result Edge: type: object required: - source - target properties: source: type: string description: ID of the source node target: type: string description: ID of the target node id: type: string description: Optional unique identifier for the edge sourceHandle: type: string description: Optional source handle identifier targetHandle: type: string description: Optional target handle identifier NodeOptions: type: object description: Node execution options properties: flat_map: type: boolean description: Whether to flatten the response backoff_ms: type: integer format: int64 description: >- Backoff duration in milliseconds - how long to wait before next attempt. Applies to function and flow nodes only. timeout: type: integer format: int64 description: >- Timeout duration in milliseconds. Applies to function and flow nodes only. attempts: type: integer format: int32 description: Number of retry attempts. Applies to function and flow nodes only. ignore_response_codes: type: array items: type: integer description: >- List of HTTP response codes to ignore. Applies to function nodes only. securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: JWT Authorization header using the Bearer scheme apiKeyAuth: type: apiKey in: header name: X-Api-Key ````