Torq supports custom fields on cases. Custom fields in Torq are stored as case timeline events — they are not properties on the ticket body itself. This means they are per-ticket by nature, and Project ID must always be *.
The Field Path (Provider) in each mapping must be the key name of the custom field as it appears in Torq's case timeline events (event type EVENT_TYPE_CUSTOM_FIELD_UPDATED).
To find key names, navigate to a case in Torq that has custom fields set and inspect the custom field keys shown in the case detail view. The key name displayed in Torq is the value to use in Field Path (Provider).
When creating or editing your integration, enable the Custom Field Mappings toggle. Click + Add CustomFieldMapping to add an entry for each field you want to map. Fill in the following for each entry:
Project ID Must be *. Torq custom fields are not project-scoped.
Field Path (Provider) The Torq field key name found in Step 1 (e.g., alert_source).
Name A unique key used to reference this field in the custom_fields object when creating or patching tickets (e.g., alert_source).
Click + Add CustomFieldMapping to add additional mappings.