> For the complete documentation index, see [llms.txt](https://docs.middle.app/middle-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.middle.app/middle-docs/product/accounts/workflow-parameters/advanced-parameters.md).

# Advanced Parameters

Advanced parameters are most often used in the context of an action, such as an action that passes in an array of objects. You can also use advanced parameters to create lists of values, such as a list of strings to use within [array manipulation](https://docs.middle.app/middle-docs/product/accounts/workflow-parameters/array-manipulation.md).

The examples use the JSON found in a [copied workflow](https://docs.middle.app/middle-docs/product/accounts/workflow-parameters.md). Each object describes a parameter; evaluating it produces the result described below.

## Construct Object

JSON type: `construct_object`.

Create a new object, typically an object that's defined within an action. Each child in `params` supplies one field. The child's `key` is the exact field key, and the child's result is the field's value. Use the keys and value types defined by the destination, such as an Action input, Begin input, or workflow variable. The editor uses that definition to offer the fields you can fill in.

Construct Object does not parse JSON entered in `expression`. Copied workflows may include `"expression": "{}"`; the fields still come from the child parameters. A missing child leaves that field out of the result; a child of type `make_null` includes the field with a null value. Each field should have a unique `key`.

For a destination with a text field named `email` and a number field named `points`, this parameter produces `{"email": "sally@example.com", "points": 10}`. In a real workflow you could use Variable Selector for the email instead of fixed text.

```json
{
  "type": "construct_object",
  "expression": "{}",
  "params": [
    {
      "key": "email",
      "type": "template",
      "expression": "sally@example.com"
    },
    {
      "key": "points",
      "type": "math_expression",
      "expression": "10"
    }
  ]
}
```

## Construct Array

JSON type: `construct_array`.

Create a new array from the children in `params`. Children are evaluated in order. A child that returns a single value adds one item; a child that returns an array adds all of that array's items. It does not create nested arrays.

All items must have the same type. For example, an array can contain numbers or strings, but not a mixture of both. Empty child arrays add no items. With no children, Construct Array returns an empty array.

This example combines a single value with another array, returning `["Yoga", "Pilates", "Cycling"]`.

```json
{
  "type": "construct_array",
  "params": [
    {"type": "template", "expression": "Yoga"},
    {
      "type": "construct_array",
      "params": [
        {"type": "template", "expression": "Pilates"},
        {"type": "template", "expression": "Cycling"}
      ]
    }
  ]
}
```

For an array of objects, use Construct Object for each child and supply the fields expected by the destination. To build one object for each item in an existing array, use [Map Array](https://docs.middle.app/middle-docs/product/accounts/workflow-parameters/array-manipulation.md#map-array) with Construct Object as its second child.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.middle.app/middle-docs/product/accounts/workflow-parameters/advanced-parameters.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
