Skip to content

Zoho: Field updates schemas

36 Zoho schemas with complete fields and constraints.

← Field updates operations · All schemas

Create Field Update — request body — body

FieldTypePresenceDescription and constraints
$objectRootThe request body wrapper for creating or updating a field update action. Must contain a field_updates array with exactly one entry.
Additional keys: not allowed
field_updatesarrayRequired within parentArray containing one field update configuration object. Exactly one item is allowed per request.
Maximum items: 1
field_updates[]ModelEach itemExpand Create Field Update — request body — body field updates item

Referenced models: Create Field Update — request body — body field updates item

Create Field Update — request body — body field updates item

FieldTypePresenceDescription and constraints
$objectRootDefines a single field update action, including the target module, target field, mapping type, and the value to apply. Some properties are conditionally required depending on the target field's type — for example, Owner fields require notify and related_records.
Additional keys: not allowed
apply_assignment_thresholdbooleanOptionalWhether to enforce assignment-threshold rules when updating the Owner field. This key is applicable only for Owner updates, and is required only when active owner-assignment thresholds exist for the module. If thresholds are not configured, sending this key can be rejected as not allowed.
Default: false
dependent_fieldsarray or nullOptionalDependent fields that must be set alongside the target field. Required for dependent picklist relationships. Common chains: Pipeline -> Stage, Layout -> Pipeline, and Layout -> Pipeline -> Stage (nested via dependent_fields inside the Pipeline node).
Maximum items: 1
dependent_fields[]ModelEach itemExpand Create Field Update — request body — body field updates item dependent fields item
feature_typestringOptionalAutomation feature where this field update action is used. Supports baseline features plus connected_workflows. No cadence support.
The automation feature this field update is associated with. Defaults to 'workflow' if omitted. All enum values are supported for creation via API.
One of: workflow, approval_process, blueprint_transition, blueprint_state, assignment_rules, kiosk, commandcenter_service, connected_workflows
Maximum length: 255
fieldModelRequired within parentExpand Create Field Update — request body — body field updates item field
Target field to be updated. Provide both field.id and field.api_name. If both are present but inconsistent, ambiguity or invalid-data errors can be returned.
moduleModelRequired within parentExpand Create Field Update — request body — body field updates item module
The CRM module where this field update should be applied. Specify using the module's unique ID and/or API name (e.g., Deals, Leads, Contacts).
namestringRequired within parentName of the field update action. Must be unique within the org. This label is displayed in the automation rule configuration UI.
Maximum length: 255
notifybooleanOptionalWhether to send an email notification to the new owner when the Owner field is updated. Required when the target field is Owner (omitting returns DEPENDENT_FIELD_MISSING). Must not be sent when the target field is not Owner (returns NOT_ALLOWED).
Default: false
related_moduleModelOptionalExpand Create Field Update — request body — body field updates item related module
Related module context when the field update is configured on a related module's records (e.g., updating a field on Contacts related to Accounts). Pass null or omit when not applicable.
related_recordsarray or nullOptionalRelated modules whose open record ownership should also be transferred when the Owner field is updated. Common activity modules (Tasks, Calls, Events) are available for all modules. Additional modules depend on the parent module: Accounts can also include Contacts and Deals; Contacts can also include Deals. Required when the target field is Owner (omitting returns DEPENDENT_FIELD_MISSING). Must not be sent when the target field is not Owner (returns NOT_ALLOWED). Pass null to skip ownership transfer on related records.
Maximum items: 5
related_records[]ModelEach itemExpand Create Field Update — request body — body field updates item related records item
typestringRequired within parentThe mapping type used when creating or updating the field update action. Only static is accepted; merge_field appears only in GET responses for existing actions.
Create/update mapping type. Only static is accepted for create/update payloads.
One of: static
Maximum length: 255
update_typeModelOptionalExpand Create Field Update — request body — body field updates item update type
Strategy for applying the value. Required for multi-select fields: 'overwrite' replaces all existing values, 'append' adds to them. Omit or pass null for single-value fields.
valueJSONRequired within parentThe value to assign to the target field when this action is triggered. The type must match the target field's data type - a mismatch returns DEPENDENT_MISMATCH. Pipeline expects a string value from Pipelines metadata; Layout expects a layout object from Layouts metadata; Owner expects a user object from Users API.
value (anyOf 1)stringAlternativeA string value used for text, single-picklist, date, or Pipeline fields. Picklist and Pipeline values are validated against the field's configured options.
Maximum length: 255
value (anyOf 2)ModelAlternativeExpand Create Field Update — request body — body field updates item value array
value (anyOf 3)ModelAlternativeExpand Create Field Update — request body — body field updates item value id, name
value (anyOf 4)booleanAlternativeA boolean value used for checkbox fields, where true marks the field as checked and false marks it as unchecked.
value (anyOf 5)numberAlternativeA numeric value used for number, currency, decimal, or percentage fields.
value (anyOf 6)nullAlternativeNull value - clears/empties the target field, removing any previously set value.

Referenced models: Create Field Update — request body — body field updates item dependent fields item, Create Field Update — request body — body field updates item field, Create Field Update — request body — body field updates item value array, Create Field Update — request body — body field updates item value id, name, Create Field Update — request body — body field updates item update type, Create Field Update — request body — body field updates item module, Create Field Update — request body — body field updates item related module, Create Field Update — request body — body field updates item related records item

Create Field Update — request body — body field updates item dependent fields item

FieldTypePresenceDescription and constraints
$objectRootA dependent field that must be included alongside the target field's value, used when the target field's valid options depend on another field (for example, Pipeline requires Stage). Supports nesting up to 3 levels.

Additional keys: not allowed
dependent_fieldsarrayOptionalNested dependent fields that must be set when the current dependent field itself has further dependencies.
Maximum items: 10
dependent_fields[]ModelEach itemExpand Create Field Update — request body — body field updates item dependent fields item dependent fields item
fieldModelRequired within parentExpand Create Field Update — request body — body field updates item field
Specify the API name and ID of the dependent field to be updated.
valuestringRequired within parentContains value of the dependent field.
Maximum length: 255

Referenced models: Create Field Update — request body — body field updates item dependent fields item dependent fields item, Create Field Update — request body — body field updates item field

Create Field Update — request body — body field updates item dependent fields item dependent fields item

FieldTypePresenceDescription and constraints
$objectRootSecond-level dependent field in a chained dependency. Example: Stage in a Pipeline -> Stage chain.
Additional keys: not allowed
dependent_fieldsarrayOptionalThird-level dependent fields for deeper dependency chains.
Maximum items: 10
dependent_fields[]ModelEach itemExpand Create Field Update — request body — body field updates item dependent fields item dependent fields item dependent fields item
fieldModelRequired within parentExpand Create Field Update — request body — body field updates item field
Specify the API name and ID of the dependent field to be updated.
valuestringRequired within parentContains value of the dependent field.
Maximum length: 255

Referenced models: Create Field Update — request body — body field updates item dependent fields item dependent fields item dependent fields item, Create Field Update — request body — body field updates item field

Create Field Update — request body — body field updates item dependent fields item dependent fields item dependent fields item

FieldTypePresenceDescription and constraints
$objectRootThird-level (deepest) dependent field in a chained dependency. No further nesting is supported beyond this level.
Additional keys: not allowed
fieldModelRequired within parentExpand Create Field Update — request body — body field updates item field
Specify the API name and ID of the dependent field to be updated.
valuestringRequired within parentContains value of the dependent field.
Maximum length: 255

Referenced models: Create Field Update — request body — body field updates item field

Create Field Update — request body — body field updates item field

FieldTypePresenceDescription and constraints
$objectRootIdentifies the target field to update. Requires both id and api_name; if they refer to different fields, the request fails with AMBIGUITY_DURING_PROCESSING.

Additional keys: not allowed
api_namestringRequired within parentAPI name of the CRM field (e.g., Deal_Name, Pipeline, Owner, Layout, Multi_Select_1).
Maximum length: 255
data_typestringOptionalData type of the CRM field, for example text, picklist, or lookup.
Maximum length: 255
field_labelstringOptionalDisplay label of the CRM field, as shown in the CRM UI.
Maximum length: 255
idstringRequired within parentUnique identifier of the CRM field. Mandatory in create/update payloads.
Maximum length: 255
ui_typeintegerOptionalInternal UI type code for the field. Present only in response; not required in requests.
Format: int32

Create Field Update — request body — body field updates item module

FieldTypePresenceDescription and constraints
$objectRootModule metadata for the primary CRM module associated with the field update action.
Additional keys: not allowed
api_namestringRequired within parentCRM module API name used in automation configuration (e.g., Leads, Contacts, Deals).
Maximum length: 255
idstringOptionalUnique identifier of the CRM module corresponding to api_name.
Maximum length: 255
moduleNamestringOptionalInternal module name. Present only in responses.
Maximum length: 255
plural_labelstringOptionalPlural display label of the module (e.g., Deals, Leads). Present only in responses.
Maximum length: 255
singular_labelstringOptionalSingular display label of the module (e.g., Deal, Lead). Present only in responses.
Maximum length: 255

Create Field Update — request body — body field updates item related module

FieldTypePresenceDescription and constraints
$object or nullRootRelated module metadata for automation contexts that operate on related records. Null when no related module context applies.
Additional keys: not allowed
api_namestringOptionalCRM related-module API name used in automation configuration (e.g., Notes).
Maximum length: 255
idstringOptionalUnique identifier of the related CRM module corresponding to api_name.
Maximum length: 255

Create Field Update — request body — body field updates item related records item

FieldTypePresenceDescription and constraints
$objectRootIdentifies a related module whose open records' ownership should be transferred alongside the parent record when the Owner field is updated. Available modules depend on the parent module context.
Additional keys: not allowed
api_namestringRequired within parentAPI name of the related module. Events, Calls, Tasks - open activity records, available for all modules. Contacts - available only when the parent module is Accounts. Deals - available when the parent module is Accounts or Contacts.
One of: Events, Calls, Tasks, Contacts, Deals
Maximum length: 255
idstringOptionalUnique identifier of the related module. This is the module ID corresponding to the api_name.
Maximum length: 255

Create Field Update — request body — body field updates item update type

FieldTypePresenceDescription and constraints
$string or nullRootSpecifies how the new value is applied to a multi-select picklist or Owner field: overwrite replaces the existing value, append adds to the existing entries. Omit or set to null for single-value fields.
One of: overwrite, append, null
Maximum length: 255

Create Field Update — request body — body field updates item value array

FieldTypePresenceDescription and constraints
$arrayRootAn array of string values used for multi-select picklist fields, where each element represents one selected option.
Maximum items: 25
$[]stringEach itemIndividual option value for the multi-select field.
Maximum length: 255

Create Field Update — request body — body field updates item value id, name

FieldTypePresenceDescription and constraints
$objectRootAn object value used for Owner or Layout fields, identified by id (a user ID for Owner fields or a layout ID for Layout fields), with an optional name for display.
Additional keys: not allowed
idstringRequired within parentUnique identifier of the user to assign as the new owner.
Maximum length: 255
namestringOptionalOptional display name for readability.
Maximum length: 255

Create Field Update — response body

FieldTypePresenceDescription and constraints
$objectRootSuccess response returned when a field update action is created. Contains an array with a single result object indicating the outcome and the server-generated ID of the new field update.
Additional keys: not allowed
field_updatesarrayOptionalArray containing the result of the create operation. Always contains exactly one item since only one field update can be created per request.
Maximum items: 1
field_updates[]ModelEach itemExpand Create Field Update — response body — field updates item

Referenced models: Create Field Update — response body — field updates item

Create Field Update — response body — field updates item

FieldTypePresenceDescription and constraints
$objectRootResult object for a field update create, update, or delete operation. Contains the operation outcome code, a human-readable message, the status, and details including the server-generated ID.
Additional keys: not allowed
codestringRequired within parentOperation result code. 'SUCCESS' for successful operations. In bulk operations (DELETE 207), individual items may return error codes like 'NOT_ALLOWED' or 'INVALID_DATA'.
Known values: SUCCESS, NOT_ALLOWED, INVALID_DATA
Maximum length: 255
detailsModelRequired within parentExpand Create Field Update — response body — field updates item details
messagestringRequired within parentHuman-readable message describing the operation outcome.
Maximum length: 255
statusstringRequired within parentOverall status of the operation. 'success' for successful operations, 'error' for failed individual items in bulk operations.
Known values: success, error
Maximum length: 255

Referenced models: Create Field Update — response body — field updates item details

Create Field Update — response body — field updates item details

FieldTypePresenceDescription and constraints
$objectRootDetails object within an action result, containing the server-generated unique identifier of the created, updated, or deleted field update action.
Additional keys: not allowed
idstringRequired within parentUnique identifier of the field update action that was created, updated, or deleted.
Maximum length: 255

Delete Field Update — response body

FieldTypePresenceDescription and constraints
$objectRootIndicates that the field update was deleted successfully.
Additional keys: not allowed
field_updatesarrayOptionalArray containing the deleted field update action. Contains exactly one item.
Maximum items: 1
field_updates[]ModelEach itemExpand Create Field Update — response body — field updates item

Referenced models: Create Field Update — response body — field updates item

Get Field Update By Id — response body — field updates

FieldTypePresenceDescription and constraints
$objectRootResponse payload for retrieving a single field update action by ID.
Additional keys: not allowed
field_updatesarrayOptionalArray containing the matched field update action. Contains one item for a valid ID.
Maximum items: 1
field_updates[]ModelEach itemExpand Get Field Update By Id — response body — field updates field updates item

Referenced models: Get Field Update By Id — response body — field updates field updates item

Get Field Update By Id — response body — field updates field updates item

FieldTypePresenceDescription and constraints
$objectRootRepresents one field update action returned by the list API, including field configuration, update behavior, module context, and audit metadata.
Additional keys: not allowed
apply_assignment_thresholdbooleanOptionalWhether assignment-threshold rules (record count limits per user) should be enforced when updating the field. Only applicable when the target field is an Owner field and the org has assignment thresholds configured. When true, the system checks whether the new owner has reached their record limit before applying the update. Ignored for non-Owner fields.
associatedbooleanOptionalWhether this action is currently linked to any automation rule, approval process, or blueprint.
created_byModelOptionalExpand Get Field Update By Id — response body — field updates field updates item created by
User who created this field update action.
created_timestringOptionalDate-time when this field update action was created.
Maximum length: 255
deletablebooleanOptionalRepresents whether the current user can delete this field update action.
dependent_fieldsJSONOptional
dependent_fields (anyOf 1)arrayAlternativeDependent fields that must be set alongside the target field when dependency rules apply. Includes patterns such as Pipeline -> Stage and Layout -> Pipeline -> Stage (nested). Nested dependencies can be represented through dependent_fields within each item. Null when the target field has no dependency rules configured.
Maximum items: 10
dependent_fields (anyOf 1)[]ModelEach itemExpand Get Field Update By Id — response body — field updates field updates item dependent fields null item
dependent_fields (anyOf 2)nullAlternativeDependent fields that must be set alongside the target field when dependency rules apply. Includes patterns such as Pipeline -> Stage and Layout -> Pipeline -> Stage (nested). Nested dependencies can be represented through dependent_fields within each item. Null when the target field has no dependency rules configured.
Maximum items: 10
dependent_fields (anyOf 2)[]ModelEach itemExpand Get Field Update By Id — response body — field updates field updates item dependent fields null item
editablebooleanOptionalWhether the current user can edit this field update action.
feature_typestringOptionalAutomation feature where this field update action is used. Supports baseline features plus connected_workflows. No cadence support.
Automation feature where this field update action is used.
Known values: workflow, approval_process, blueprint_transition, blueprint_state, assignment_rules, kiosk, commandcenter_service, connected_workflows
Maximum length: 255
fieldModelRequired within parentExpand Get Field Update By Id — response body — field updates field updates item field
The target CRM field that this action updates.
idstringOptionalUnique identifier of the field update action.
Maximum length: 20
lock_statusModelOptionalExpand Get Field Update By Id — response body — field updates field updates item lock status
Indicates whether this field update action is locked for edit/delete.
modified_byModelOptionalExpand Get Field Update By Id — response body — field updates field updates item modified by
User who last modified this field update action.
modified_timestringOptionalDate-time when this field update action was last modified.
Maximum length: 255
moduleModelRequired within parentExpand Create Field Update — request body — body field updates item module
Primary CRM module on which this field update action is configured.
namestringRequired within parentDisplay name of the field update action.
Maximum length: 255
notifybooleanOptionalWhether to send an email notification to the new record owner when the Owner field is updated via this action. Only applicable when the target field is an Owner field. When true, the newly assigned owner receives an email informing them of the ownership change. Ignored for non-Owner fields.
parent_moduleJSONOptional
parent_module (anyOf 1)objectAlternativeParent module context when the field update is configured on a child module. Null when the field update is on a top-level module.
Additional keys: not allowed
parent_module (anyOf 1).api_namestringOptionalAPI name of the parent CRM module.
Maximum length: 255
parent_module (anyOf 1).idstringOptionalUnique identifier of the parent CRM module.
Maximum length: 20
parent_module (anyOf 2)nullAlternativeParent module context when the field update is configured on a child module. Null when the field update is on a top-level module.
Additional keys: not allowed
parent_module (anyOf 2).api_namestringOptionalAPI name of the parent CRM module.
Maximum length: 255
parent_module (anyOf 2).idstringOptionalUnique identifier of the parent CRM module.
Maximum length: 20
related_moduleModelOptionalExpand Get Field Update By Id — response body — field updates field updates item related module
Related module context when the automation is configured on related records; null when not applicable.
related_recordsJSONOptional
related_records (anyOf 1)arrayAlternativeList of related modules whose record ownership should also be transferred along with the parent record when the Owner field is updated. Only applicable when the target field is an Owner field. Common activity modules (Tasks, Calls, Events) are available for all modules. Additional related modules are available depending on the parent module: Accounts can also include Contacts and Deals; Contacts can also include Deals. Null when the target field is not an Owner field or when no related modules are selected for ownership transfer.
Maximum items: 5
related_records (anyOf 1)[]ModelEach itemExpand Get Field Update By Id — response body — field updates field updates item related records null item
related_records (anyOf 2)nullAlternativeList of related modules whose record ownership should also be transferred along with the parent record when the Owner field is updated. Only applicable when the target field is an Owner field. Common activity modules (Tasks, Calls, Events) are available for all modules. Additional related modules are available depending on the parent module: Accounts can also include Contacts and Deals; Contacts can also include Deals. Null when the target field is not an Owner field or when no related modules are selected for ownership transfer.
Maximum items: 5
related_records (anyOf 2)[]ModelEach itemExpand Get Field Update By Id — response body — field updates field updates item related records null item
sourcestringOptionalSource application that created or manages this action (e.g., crm).
Maximum length: 255
typestringRequired within parentResponse-only field update type. Create/update supports only static, while GET responses may include merge_field for pre-existing actions.
Type returned by the API for this field update. Create/update accepts only static; GET responses can include merge_field for pre-existing actions.
Known values: static, merge_field
Maximum length: 255
update_typeModelOptionalExpand Get Field Update By Id — response body — field updates field updates item update type
Specifies how the field value should be applied when the target field supports multiple update strategies (e.g., multi-select picklist, Owner). Null when the field type does not support multiple update strategies (e.g., text, single picklist).
valueJSONRequired within parentThe value configured for the field update. The shape depends on the target field type.
value (anyOf 1)stringAlternativeA plain text value. Used when the target field is a single-value field such as a text field (e.g., Deal_Name), picklist (e.g., Pipeline, Stage), number, date, or similar scalar field types. Example: "PostTest", "Qualification".
Maximum length: 255
value (anyOf 2)arrayAlternativeAn array of selected option values. Used when the target field is a multi-select picklist. Each element represents one selected option. Example: ["Option 1", "Option 2"].
Maximum items: 25
value (anyOf 2)[]stringEach itemOne selected option value for the multi-select field.
Maximum length: 255
value (anyOf 3)objectAlternativeA structured object value. Used when the target field requires composite data - for example, a Layout field (with id, name, display_label), an Owner/user-lookup field (with id, name), or other lookup-type fields that resolve to a resource with an identifier.
Additional keys: allowed
value (anyOf 4)booleanAlternativeA boolean value. Used when the target field is a checkbox or boolean-type field. true enables/checks the field, false disables/unchecks it.
value (anyOf 5)JSONAlternative
value (anyOf 5) (anyOf 1)numberAlternativeA numeric value. Used when the target field is a number, currency, decimal, or percentage field type. Example: 100, 25.5.
value (anyOf 5) (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
value (anyOf 6)nullAlternativeA null value. Used to clear/empty the target field - equivalent to choosing 'empty value' in the field update configuration.

Referenced models: Get Field Update By Id — response body — field updates field updates item created by, Get Field Update By Id — response body — field updates field updates item lock status, Get Field Update By Id — response body — field updates field updates item modified by, Create Field Update — request body — body field updates item module, Get Field Update By Id — response body — field updates field updates item dependent fields null item, Get Field Update By Id — response body — field updates field updates item field, Get Field Update By Id — response body — field updates field updates item update type, Get Field Update By Id — response body — field updates field updates item related module, Get Field Update By Id — response body — field updates field updates item related records null item

Get Field Update By Id — response body — field updates field updates item created by

FieldTypePresenceDescription and constraints
$objectRootUser who created the field update action, including display name and unique identifier.
Additional keys: not allowed
idstringOptionalUnique identifier of the user who created the resource.
Maximum length: 255
namestringOptionalDisplay name of the user who created the resource.
Maximum length: 255

Get Field Update By Id — response body — field updates field updates item dependent fields null item

FieldTypePresenceDescription and constraints
$objectRootA dependent field that must be included alongside the target field's value, used when the target field's valid options depend on another field (for example, Pipeline requires Stage). Supports nesting up to 3 levels.

Additional keys: not allowed
dependent_fieldsarrayOptionalNested dependent fields that must be set when the current dependent field itself has further dependencies.
Maximum items: 10
dependent_fields[]ModelEach itemExpand Get Field Update By Id — response body — field updates field updates item dependent fields null item dependent fields item
fieldModelRequired within parentExpand Get Field Update By Id — response body — field updates field updates item field
Specify the API name and ID of the dependent field to be updated.
valuestringRequired within parentContains value of the dependent field.
Maximum length: 255

Referenced models: Get Field Update By Id — response body — field updates field updates item dependent fields null item dependent fields item, Get Field Update By Id — response body — field updates field updates item field

Get Field Update By Id — response body — field updates field updates item dependent fields null item dependent fields item

FieldTypePresenceDescription and constraints
$objectRootSecond-level dependent field in a chained dependency. Example: Stage in a Pipeline -> Stage chain.
Additional keys: not allowed
dependent_fieldsarrayOptionalThird-level dependent fields for deeper dependency chains.
Maximum items: 10
dependent_fields[]ModelEach itemExpand Get Field Update By Id — response body — field updates field updates item dependent fields null item dependent fields item dependent fields item
fieldModelRequired within parentExpand Get Field Update By Id — response body — field updates field updates item field
Specify the API name and ID of the dependent field to be updated.
valuestringRequired within parentContains value of the dependent field.
Maximum length: 255

Referenced models: Get Field Update By Id — response body — field updates field updates item dependent fields null item dependent fields item dependent fields item, Get Field Update By Id — response body — field updates field updates item field

Get Field Update By Id — response body — field updates field updates item dependent fields null item dependent fields item dependent fields item

FieldTypePresenceDescription and constraints
$objectRootThird-level (deepest) dependent field in a chained dependency. No further nesting is supported beyond this level.
Additional keys: not allowed
fieldModelRequired within parentExpand Get Field Update By Id — response body — field updates field updates item field
Specify the API name and ID of the dependent field to be updated.
valuestringRequired within parentContains value of the dependent field.
Maximum length: 255

Referenced models: Get Field Update By Id — response body — field updates field updates item field

Get Field Update By Id — response body — field updates field updates item field

FieldTypePresenceDescription and constraints
$objectRootIdentifies the target field to update. Requires both id and api_name; if they refer to different fields, the request fails with AMBIGUITY_DURING_PROCESSING.

Additional keys: not allowed
api_namestringRequired within parentAPI name of the CRM field (e.g., Deal_Name, Pipeline, Owner, Layout, Multi_Select_1).
Maximum length: 255
data_typestringOptionalData type of the CRM field, for example text, picklist, or lookup.
Maximum length: 255
field_labelstringOptionalDisplay label of the CRM field, as shown in the CRM UI.
Maximum length: 255
idstringRequired within parentUnique identifier of the CRM field. Mandatory in create/update payloads.
Maximum length: 255
ui_typeJSONOptional
ui_type (anyOf 1)integerAlternativeInternal UI type code for the field. Present only in response; not required in requests.
Format: int32
ui_type (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$

Get Field Update By Id — response body — field updates field updates item lock status

FieldTypePresenceDescription and constraints
$objectRootIndicates whether a particular component is locked, affecting its editability and deletability.
Additional keys: not allowed
lockedbooleanOptionalTrue when the action is locked and cannot be edited or deleted.

Get Field Update By Id — response body — field updates field updates item modified by

FieldTypePresenceDescription and constraints
$objectRootUser who last modified the field update action, including display name and unique identifier.
Additional keys: not allowed
idstringOptionalUnique identifier of the user who last modified the resource.
Maximum length: 255
namestringOptionalDisplay name of the user who last modified the resource.
Maximum length: 255

Get Field Update By Id — response body — field updates field updates item related module

FieldTypePresenceDescription and constraints
$JSONRoot
$ (anyOf 1)objectAlternativeRelated module metadata for automation contexts that operate on related records. Null when no related module context applies.
Additional keys: not allowed
$ (anyOf 1).api_namestringOptionalCRM related-module API name used in automation configuration (e.g., Notes).
Maximum length: 255
$ (anyOf 1).idstringOptionalUnique identifier of the related CRM module corresponding to api_name.
Maximum length: 255
$ (anyOf 2)nullAlternativeRelated module metadata for automation contexts that operate on related records. Null when no related module context applies.
Additional keys: not allowed
$ (anyOf 2).api_namestringOptionalCRM related-module API name used in automation configuration (e.g., Notes).
Maximum length: 255
$ (anyOf 2).idstringOptionalUnique identifier of the related CRM module corresponding to api_name.
Maximum length: 255

Get Field Update By Id — response body — field updates field updates item related records null item

FieldTypePresenceDescription and constraints
$objectRootIdentifies a related module whose open records' ownership should be transferred alongside the parent record when the Owner field is updated. Available modules depend on the parent module context.
Additional keys: not allowed
api_namestringRequired within parentAPI name of the related module. Events, Calls, Tasks - open activity records, available for all modules. Contacts - available only when the parent module is Accounts. Deals - available when the parent module is Accounts or Contacts.
Known values: Events, Calls, Tasks, Contacts, Deals
Maximum length: 255
idstringOptionalUnique identifier of the related module. This is the module ID corresponding to the api_name.
Maximum length: 255

Get Field Update By Id — response body — field updates field updates item update type

FieldTypePresenceDescription and constraints
$JSONRoot
$ (anyOf 1)stringAlternativeSpecifies how the new value is applied to a multi-select picklist or Owner field: overwrite replaces the existing value, append adds to the existing entries. Omit or set to null for single-value fields.
Known values: overwrite, append
Maximum length: 255
$ (anyOf 2)nullAlternativeSpecifies how the new value is applied to a multi-select picklist or Owner field: overwrite replaces the existing value, append adds to the existing entries. Omit or set to null for single-value fields.
Known values: overwrite, append
Maximum length: 255

Get Field Updates — response body — field updates, info

FieldTypePresenceDescription and constraints
$objectRootSuccessful response for listing field update actions. Contains an array of field update definitions configured in the org along with pagination metadata.
Additional keys: not allowed
field_updatesarrayOptionalList of field update actions configured in the org.
Maximum items: 200
field_updates[]ModelEach itemExpand Get Field Update By Id — response body — field updates field updates item
infoModelOptionalExpand Get Field Updates — response body — field updates, info info

Referenced models: Get Field Update By Id — response body — field updates field updates item, Get Field Updates — response body — field updates, info info

Get Field Updates — response body — field updates, info info

FieldTypePresenceDescription and constraints
$objectRootPagination metadata for list responses. Use more_records to determine if additional pages are available.
Additional keys: not allowed
countJSONOptional
count (anyOf 1)integerAlternativeNumber of records returned in the current page.
Format: int32
count (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
more_recordsbooleanOptionalTrue when additional records are available on subsequent pages.
pageJSONOptional
page (anyOf 1)integerAlternativeCurrent page number (starts at 1).
Format: int32
page (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
per_pageJSONOptional
per_page (anyOf 1)integerAlternativeMaximum number of records returned per page (default 200).
Format: int32
per_page (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$

To delete multiple field update actions — response body — field updates field updates item

FieldTypePresenceDescription and constraints
$objectRootResult item for a field update ID deleted successfully in bulk delete.
Additional keys: not allowed
codestringRequired within parentResult code.
Known values: SUCCESS
detailsModelRequired within parentExpand To delete multiple field update actions — response body — field updates field updates item details
messagestringRequired within parentSuccess message.
Maximum length: 255
statusstringRequired within parentOperation status.
Known values: success

Referenced models: To delete multiple field update actions — response body — field updates field updates item details

To delete multiple field update actions — response body — field updates field updates item details

FieldTypePresenceDescription and constraints
$objectRootIdentifier details for a bulk-delete result item.
Additional keys: not allowed
idstringRequired within parentField update ID for which this result applies.
Maximum length: 20

To delete multiple field update actions — response body — field updates — Bulk Delete Mixed Response

FieldTypePresenceDescription and constraints
$objectRootBulk delete partial-success response. Contains mixed success and failure items for the requested field update IDs.
Additional keys: not allowed
field_updatesarrayRequired within parentPer-ID deletion results for the bulk request.
Maximum items: 10
field_updates[]JSONEach item
field_updates[] (anyOf 1)ModelAlternativeExpand To delete multiple field update actions — response body — field updates field updates item
field_updates[] (anyOf 2)ModelAlternativeExpand To delete multiple field update actions — response body — field_updates / field_updates / item / code: INVALID DATA, NOT ALLOWED, status: error

Referenced models: To delete multiple field update actions — response body — field_updates / field_updates / item / code: INVALID DATA, NOT ALLOWED, status: error, To delete multiple field update actions — response body — field updates field updates item

To delete multiple field update actions — response body — field updates — Bulk Delete Success Response

FieldTypePresenceDescription and constraints
$objectRootBulk delete success response where all requested field update IDs are deleted.
Additional keys: not allowed
field_updatesarrayRequired within parentDeletion result entries for each requested ID.
Maximum items: 10
field_updates[]ModelEach itemExpand To delete multiple field update actions — response body — field updates field updates item

Referenced models: To delete multiple field update actions — response body — field updates field updates item

To delete multiple field update actions — response body — field_updates / field_updates / item / code: INVALID DATA, NOT ALLOWED, status: error

FieldTypePresenceDescription and constraints
$objectRootResult item for a field update ID that failed during bulk delete. INVALID_DATA indicates the ID does not exist; NOT_ALLOWED indicates the field update is associated with a workflow rule, blueprint, or approval process.
Additional keys: not allowed
codestringRequired within parentFailure code.
Known values: INVALID_DATA, NOT_ALLOWED
detailsModelRequired within parentExpand To delete multiple field update actions — response body — field updates field updates item details
messagestringRequired within parentFailure message.
Maximum length: 255
statusstringRequired within parentOperation status.
Known values: error

Referenced models: To delete multiple field update actions — response body — field updates field updates item details

Update Field Update — response body

FieldTypePresenceDescription and constraints
$objectRootSuccess response payload returned after a field update action is modified.
Additional keys: not allowed
field_updatesarrayOptionalArray containing the updated field update action. Contains exactly one item.
Maximum items: 1
field_updates[]ModelEach itemExpand Create Field Update — response body — field updates item

Referenced models: Create Field Update — response body — field updates item

Report an issue with this page

Necessary

Required for sign-in, security, authorization, and remembering your choices.

Always active

Analytics

Helps us understand which product and documentation features are useful.

Performance diagnostics

Uses performance tracing and privacy-masked session replay to diagnose problems.

You can change these choices at any time from Cookie settings.