# ....
workflows:
  - workflowId: some-test
    steps:
      - stepId: update
        operationId: updateUser
        parameters:
          - name: id
            in: path
            value: "some-test-id" # A literal value can be provided inline for parameters that matches the json schema of the parameter as defined in the associated operation
        requestBody:
          contentType: application/json
          payload: # literals values that match the content type of the request body can be provided inline
            {
              "email": "Trystan_Crooks@hotmail.com",
              "first_name": "Trystan",
              "last_name": "Crooks",
              "age": 32,
              "postal_code": 94110,
              "metadata":
                {
                  "allergies": "none",
                  "color": "red",
                  "height": 182,
                  "weight": 77,
                  "is_smoking": true,
                },
            }
        successCriteria:
          - condition: $statusCode == 200
```

**Payload values**

If you use the `payload` field of a request body input, its value can be any of the following:

- A static value
- A value with interpolated [runtime expressions](/openapi/arazzo#runtime-expressions)
- A [runtime expression](/openapi/arazzo#runtime-expression) by itself

You can then overlay the payload value using the `replacements` field, which represents a list of targets within the payload that will be replaced with the value of the replacements. These replacements can be static values or [runtime expressions](/openapi/arazzo#runtime-expression).

```yaml
arazzo: 1.0.0