> ## 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. # Update a node > Updates an existing node's properties ## OpenAPI ````yaml /api-reference/endpoint/hub-flows/openapi.json patch /hub/nodes/{collection_topic}/{node_topic} 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/nodes/{collection_topic}/{node_topic}: parameters: - $ref: '#/components/parameters/collectionTopic' - $ref: '#/components/parameters/nodeTopic' patch: tags: - Nodes summary: Update a node description: Updates an existing node's properties operationId: updateNode requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/UpdateNodeRequest' examples: UpdatePayload: summary: Update node payload value: subject: ms.hub.config.node.805092869.98765432 data: name: ProcessPayment node_type: function subject: quiva-function.stripe-charge payload: amount: '{{trigger.amount}}' currency: '{{trigger.currency}}' customer_id: '{{trigger.customer_id}}' metadata: order_id: '{{trigger.order_id}}' UpdateOptions: summary: Update node options value: subject: ms.hub.config.node.805092869.98765432 data: name: ProcessPayment node_type: function subject: quiva-function.stripe-charge payload: amount: '{{trigger.amount}}' options: timeout: 60000 attempts: 5 backoff_ms: 2000 ignore_response_codes: - 404 - 429 - 503 UpdateDescription: summary: Update node description value: subject: ms.hub.config.node.1025086208.55667788 data: name: TransformOrderData description: 'Updated: Transforms and enriches order data for analytics' node_type: map payload: order_id: '{{trigger.id}}' ArchiveNode: summary: Archive a node value: subject: ms.hub.config.node.805092869.11223344 data: name: DeprecatedValidator node_type: function subject: quiva-function.old-validator archived: true responses: '200': description: Node updated successfully content: application/json: schema: $ref: '#/components/schemas/SuccessResponse' example: message: success '400': description: Bad request content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: SubjectRequired: value: error: a subject is required FunctionNotFound: value: error: function not found '404': description: Resource not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: FlowNotFound: value: error: flow not found 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' nodeTopic: name: node_topic in: path description: Node topic - hash of the names the node was created with required: true schema: type: string example: '98765432' schemas: UpdateNodeRequest: type: object required: - subject - data properties: data: $ref: '#/components/schemas/NodeData' archived: type: boolean description: Whether the node is archived SuccessResponse: type: object properties: message: type: string description: Success message ErrorResponse: type: object properties: error: type: string description: Error message 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 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 ````