> ## Documentation Index > Fetch the complete documentation index at: https://docs.roark.ai/llms.txt > Use this file to discover all available pages before exploring further. # Replace a scripted flow's steps > Replaces a scripted flow's conversation graph with the tree you send. This is a full replace, not a merge: a step you omit is removed. Include `nodeId` on a step to update the existing one, omit it to create a new step. Where two branches rejoin, keep the `mergeIntoNodeIds` references a read gave you. Dropping them un-merges those branches and is refused unless `allowUnmerge` is set. A change to the set of paths re-seeds the flow's variants, which the response reports as `variantsReshaped` along with the resulting variants. ## OpenAPI ````yaml /api-reference/openapi.documented.json put /v1/simulation/customer-flow/{flowId}/steps openapi: 3.1.0 info: title: Roark Analytics API description: >- The Roark Analytics API gives you access to the same API that powers the award winning Roark Analytics platform. version: 1.0.0 servers: - description: Production url: https://api.roark.ai security: - Bearer: [] tags: - name: Agent - name: Agent Endpoint - name: Call - name: Chat - name: Metric - name: Metric Policy - name: Metric Collection Job - name: Simulation Persona - name: Simulation Environment - name: Simulation Customer Flow - name: Simulation Customer Flow Variant - name: Simulation Scenario - name: Simulation Run Plan - name: Simulation Run Plan Job - name: Simulation Job - name: HTTP Request Definition - name: Webhook - name: Issue - name: Knowledge Base - name: Call Analysis - name: Health paths: /v1/simulation/customer-flow/{flowId}/steps: put: tags: - Simulation Customer Flow summary: Replace a scripted flow's steps description: >- Replaces a scripted flow's conversation graph with the tree you send. This is a full replace, not a merge: a step you omit is removed. Include `nodeId` on a step to update the existing one, omit it to create a new step. Where two branches rejoin, keep the `mergeIntoNodeIds` references a read gave you. Dropping them un-merges those branches and is refused unless `allowUnmerge` is set. A change to the set of paths re-seeds the flow's variants, which the response reports as `variantsReshaped` along with the resulting variants. operationId: putV1SimulationCustomer-flowByFlowIdSteps parameters: - in: path name: flowId schema: type: string format: uuid required: true requestBody: content: application/json: schema: $ref: '#/components/schemas/ReplaceFlowStepsInput' responses: '200': description: The flow graph after the write content: application/json: schema: type: object properties: data: $ref: '#/components/schemas/ReplaceFlowStepsResponse' required: - data '400': content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: Validation error example: type: validation code: invalid_parameter message: The request was invalid param: email description: Bad Request '401': content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: Authentication error example: type: authentication code: unauthorized message: Authentication required description: Unauthorized '403': content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: Permission error example: type: forbidden code: permission_denied message: You do not have permission to access this resource description: Forbidden '404': content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: Not found error example: type: not_found code: resource_not_found message: The requested resource could not be found description: Not Found '409': description: >- The write drops branches that currently rejoin. Set allowUnmerge to confirm. content: application/json: schema: _def: unknownKeys: strip catchall: _def: typeName: ZodNever ~standard: version: 1 vendor: zod typeName: ZodObject ~standard: version: 1 vendor: zod _cached: null '429': content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: Rate limit error example: type: rate_limit code: too_many_requests message: Rate limit exceeded description: Too Many Requests '500': content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: Server error example: type: internal code: internal_error message: Internal server error description: Internal Server Error x-codeSamples: - lang: JavaScript source: |- import Roark from '@roarkanalytics/sdk'; const client = new Roark({ bearerToken: process.env['ROARK_API_BEARER_TOKEN'], // This is the default and can be omitted }); const response = await client.simulationCustomerFlow.replaceSteps( '182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e', { steps: [{ type: 'AGENT_TURN' }] }, ); console.log(response.data); - lang: Python source: |- import os from roark_analytics import Roark client = Roark( bearer_token=os.environ.get("ROARK_API_BEARER_TOKEN"), # This is the default and can be omitted ) response = client.simulation_customer_flow.replace_steps( flow_id="182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e", steps=[{ "type": "AGENT_TURN" }], ) print(response.data) components: schemas: ReplaceFlowStepsInput: type: object properties: steps: type: array items: $ref: '#/components/schemas/FlowStep' minItems: 1 description: >- The complete set of steps. This replaces the flow's existing steps rather than merging into them. allowUnmerge: type: boolean description: >- Confirms a write that drops branches which currently rejoin. Only needed when the request omits mergeIntoNodeIds references the flow already had; a faithful round trip never needs it. required: - steps ReplaceFlowStepsResponse: type: object properties: steps: type: array items: $ref: '#/components/schemas/FlowStep' stepsSharedWithOtherFlows: type: array items: type: string format: uuid variantsReshaped: type: boolean description: >- True when the write changed the set of paths, so the flow's variants were re-seeded and any variant id you were holding may no longer exist. variants: type: array items: $ref: '#/components/schemas/FlowVariantResponse' description: The variants after the write. warnings: type: array items: type: string required: - steps - stepsSharedWithOtherFlows - variantsReshaped - variants - warnings ErrorResponse: type: object properties: type: type: string enum: - validation - authentication - forbidden - not_found - conflict - payment_required - rate_limit - internal description: The error type category examples: - validation - authentication code: type: string description: Machine-readable error code identifier examples: - invalid_parameter - missing_required_field - unauthorized message: type: string description: Human-readable error message examples: - The request was invalid - Authentication required param: type: string description: The parameter that caused the error (if applicable) examples: - email - user_id details: description: Additional error context information required: - type - code - message FlowStep: type: object properties: nodeId: type: string format: uuid ref: type: string minLength: 1 maxLength: 64 type: type: string enum: - AGENT_TURN - CUSTOMER_TURN - CUSTOMER_FIRST_MESSAGE - CUSTOMER_SILENCE - CUSTOMER_DTMF - VOICEMAIL - SCENARIO_LINK content: type: - string - 'null' dtmfDigits: type: - string - 'null' silenceDurationSeconds: type: - integer - 'null' exclusiveMinimum: 0 linkedCustomerFlowId: type: - string - 'null' format: uuid linkedCustomerFlowVariantId: type: - string - 'null' format: uuid steps: type: array items: $ref: '#/components/schemas/FlowStep' mergeIntoNodeIds: type: array items: type: string minLength: 1 required: - type description: >- One step in a scripted flow's conversation. `nodeId` is the identity contract: include it to update the existing step, omit it to create a new one. A step continues into `steps` (more than one child is a branch point) and/or `mergeIntoNodeIds`, which names steps elsewhere in the same request that this step rejoins. Branches that come back together are represented that way rather than by repeating the shared step, so reading a flow, editing it and writing it back preserves it exactly. A merge target is named by its `nodeId` when it already exists, or by `ref` when it is being created in the same request. `ref` is a label you choose, it is request-local, and it is never stored or returned. Put the shared step inline under the first branch that reaches it and point the others at it: a top-level step is a root wired straight from the start of the flow, so a merge target parked there would also be reachable directly. FlowVariantResponse: type: object properties: id: type: string format: uuid customerFlowId: type: string format: uuid title: type: string minLength: 1 isDefault: type: boolean default: false personaId: type: - string - 'null' format: uuid environmentId: type: - string - 'null' format: uuid prompt: type: - string - 'null' latestPathId: type: - string - 'null' format: uuid precededByCustomerFlowId: type: - string - 'null' format: uuid precededByCustomerFlowVariantId: type: - string - 'null' format: uuid isGenerated: type: boolean default: false isAutoGeneratedTitle: type: boolean default: false createdAt: type: string description: Creation timestamp in ISO 8601 format updatedAt: type: string description: Last update timestamp in ISO 8601 format additionalExpectations: type: array items: $ref: '#/components/schemas/FlowExpectationResponse' required: - id - customerFlowId - title - isDefault - personaId - environmentId - latestPathId - precededByCustomerFlowId - precededByCustomerFlowVariantId - isGenerated - isAutoGeneratedTitle - createdAt - updatedAt - additionalExpectations description: >- One way of running a flow. Exactly one variant per flow is the default; the others inherit its persona and environment wherever they leave those unset. On a scripted flow each variant is bound to one path through the graph and the path engine owns that binding. FlowExpectationResponse: type: object properties: id: type: string format: uuid llmPrompt: type: string orderIndex: type: integer default: 0 sourceStepNodeId: type: - string - 'null' format: uuid required: - id - llmPrompt - orderIndex - sourceStepNodeId description: >- An expectation the agent under test is graded against. On a scripted flow these are derived from the agent turns in the graph, so they are read-only there. securitySchemes: Bearer: type: http scheme: bearer bearerFormat: JWT ````