> ## 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 workflow > Updates an existing draft workflow's properties ## OpenAPI ````yaml /api-reference/endpoint/hub-flows/openapi.json patch /hub/workflows/{collection_topic}/{flow_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/workflows/{collection_topic}/{flow_topic}: parameters: - $ref: '#/components/parameters/collectionTopic' - $ref: '#/components/parameters/flowTopic' patch: tags: - Workflows summary: Update a workflow description: Updates an existing draft workflow's properties operationId: updateWorkflow requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/UpdateWorkflowRequest' examples: updateNameAndDescription: summary: Update name and description only value: name: UpdatedWorkflowName description: Updated workflow description updateConfig: summary: Update workflow configuration value: name: UpdatedWorkflow description: Updated workflow description config: nodes: - data: id: start name: Start node_type: map payload: message: Updated start of workflow - data: id: process name: Process node_type: function subject: quiva-function.updated-process-function payload: input: '{start}' edges: - source: start target: process id: edge1 result: process addNode: summary: Add a new node to existing workflow value: config: nodes: - data: id: start name: Start node_type: map payload: message: Start - data: id: process name: Process node_type: function subject: quiva-function.process payload: input: '{start}' - data: id: notify name: Notify node_type: integration subject: slack.chat.postMessage payload: channel: '#alerts' text: 'Processed: {process.result}' edges: - source: start target: process id: e1 - source: process target: notify id: e2 result: notify archiveWorkflow: summary: Archive a workflow value: archived: true responses: '200': description: Workflow updated successfully content: application/json: schema: $ref: '#/components/schemas/UpdateWorkflowResponse' examples: updated: summary: Workflow updated successfully value: subject: ms.hub.config.workflow.draft.1234567890.98765432 name: UpdatedWorkflow description: Updated workflow description config: nodes: - data: id: start name: Start node_type: map payload: message: Updated start of workflow - data: id: process name: Process node_type: function subject: quiva-function.updated-process-function payload: input: '{start}' edges: - source: start target: process id: edge1 result: process modified: 1651395678 '400': description: Bad request content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: SubjectRequired: value: error: subject is required InvalidDraftSubject: value: error: a valid draft subject is required '404': description: Workflow not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: workflow 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' flowTopic: name: flow_topic in: path description: Flow topic - hash of the names the node was created with required: true schema: type: string example: '21312322' schemas: UpdateWorkflowRequest: type: object properties: name: type: string description: Updated name of the workflow description: type: string description: Updated description of the workflow config: $ref: '#/components/schemas/WorkflowConfig' archived: type: boolean description: Whether the workflow is archived UpdateWorkflowResponse: 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' 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 ````