Skip to main content

Automating Custom Fields in Torq Cases: Track Additional Case Details

Learn how to automate custom fields to efficiently capture, manage, and analyze organization-specific case details.

Overview

Use custom fields to capture and organize additional case information specific to the team's requirements. Custom fields support various data types for accurate categorization and thorough case analysis.

Learn how to review custom fields during a case investigation.

Full list of custom field operators

  • Add a custom field to a case

  • Get a custom field's value

  • Lists custom fields of a case

  • Remove custom field from a case

  • Retrieve custom field keys

  • Retrieve custom field values by key

  • Set custom fields values

How to use

Automate custom fields

Add custom fields

Use the Add a custom field to a case step, selecting from types like short text, number, boolean, or list single select for tailored data capture.

Manage custom fields

Use the Set custom fields values and Remove custom field from a case steps to update or remove custom fields as needed to keep case data relevant and up-to-date. The Set custom fields values step allows you to update up to 40 custom fields at once.

Retrieve custom field data

Use the Retrieve custom field keys, Retrieve custom field values by key, and List custom fields of a case steps to extract custom field keys or specific values across the workspace for comprehensive case insights

Workflow triggers for custom fields

Use the Custom field updated workflow trigger to run a workflow whenever a custom field is added or modified.

Embed custom field mentions in a case description

Add embedded mentions directly to case descriptions for high visibility. Use [mention://custom_field/<field_name>] in the Description field in the following workflow steps:

  • Create a case

  • Create a case from JSON

  • Create a case from template

  • Change case description

Learn how to manually embed custom fields in case descriptions here.

Custom field actions are case-specific and do not impact other cases within the workspace.

Use case: Case classification

Use the list single select type for a Tier field to classify cases by the required analyst group: tier1, tier2, tier3.

Use case: Ticket synchronization

Track related tickets across teams by specifying external ticket IDs in custom fields, ensuring coordinated case resolution efforts.

Use case: Sub-categorization for detailed analysis

Employ custom fields for sub-categorizing cases within broader categories, such as IAM scenarios, to gather detailed data for analysis and reporting.

Did this answer your question?