Skip to main content
Custom fields store case data that does not fit the built-in properties. Every case in the workspace shows the same set of fields under Fields in the case side panel, and your workflows read and write them by reference. Custom fields on a case

Create a field

  1. Go to Cases and open the custom fields view from the header toolbar.
  2. Select Add field.
  3. Enter a Name. Tracecat derives the field reference from the name and shows it under the input, such as Analyst verdict → analyst_verdict.
  4. Choose a Data type.
  5. For Select and Multi-select, add the allowed Options.
  6. Optionally set a default value.
Custom fields list Add a custom field

Data types

Long text is stored as TEXT and URL is stored as JSONB; the data type only changes how the case UI renders the value. Use a dropdown instead of a Select field when you want the values to appear as a case list filter with colors and icons.

Edit values on a case

Open a case and edit values under Fields in the side panel. Select View all fields to see every field, including empty ones. Field values persist when the case changes status.

Read and write fields from workflows

Pass a fields object keyed by field reference to core.cases.create_case or core.cases.update_case. update_case only changes the keys you pass.
Tracecat rejects keys that do not match an existing field reference. To start a workflow when a field changes, select fields_changed in a case trigger.
  • See Dropdowns to add colored, filterable classifications to cases.
  • See Closure requirements to require a field before a case is closed or resolved.
  • See Cases for the case action inputs that read and update fields.