> ## Documentation Index
> Fetch the complete documentation index at: https://docs.open.cx/llms.txt
> Use this file to discover all available pages before exploring further.

# Structured Fields

> Create typed fields and nested choices, then use them as variables in Agentic Workflows.

Structured Fields give workflows a shared, typed vocabulary for ticket data. Use a simple field such as a date, or organize choices into a tree.

<Tip>
  Open [**Settings → Structured Fields**](https://platform.open.cx/settings/structured-fields) to create your first field.
</Tip>

## Create a field

<Steps>
  <Step title="Add the field">
    Click **New structured field**, then enter its name and description.
  </Step>

  <Step title="Choose its type">
    Use **Enum** for authored choices. Text, Number, Boolean, and Date hold workflow values; User, Team, and Tag read their choices from your organization.
  </Step>

  <Step title="Check the API name">
    The API name is generated from the field name. It cannot change after creation because workflows use it as the field's stable identifier.
  </Step>
</Steps>

## Build nested choices

Enum fields show an **Add top-level choice** button. Hover over any choice and click **+** to add a child below it. Each choice has a name, description, and immutable API value.

Only leaf choices are workflow outputs. For example, leaves with API values `refund` and `invoice` resolve as `refund||invoice`; parent choices only organize the tree.

## Use fields in workflows

Reference a field with `{{structuredFields.<api_name>}}` or choose one of the two Structured Fields actions:

| Action                                | Use it to                                             |
| ------------------------------------- | ----------------------------------------------------- |
| **Set Structured Field Value**        | Set or clear a Text, Number, Boolean, or Date value.  |
| **Update Structured Field or Choice** | Rename, redescribe, or remove a field or enum choice. |

## Limits

|                                    |     Limit |
| ---------------------------------- | --------: |
| Structured fields per organization |        50 |
| Choices per enum field             |     1,000 |
| Choice nesting depth               | 10 levels |

***

## Related Documentation

<CardGroup cols={2}>
  <Card title="Agentic Workflows" icon="robot" href="/build-agents/get-started">Build and run customer-support workflows.</Card>
  <Card title="AI Actions" icon="bolt" href="/actions/introduction">Let agents take action in connected systems.</Card>
  <Card title="Action Execution" icon="diagram-project" href="/actions/execution">Understand how workflow actions run.</Card>
  <Card title="MCP Tools" icon="wrench" href="/mcp/tools">Use OpenCX tools from an MCP client.</Card>
</CardGroup>