Skip to content

Zoho: Create Field Update

Zoho fieldUpdates.createFieldUpdates: arguments, response, policy and SDK examples.

← Field updates operations · Get started

Operation zoho.createfieldupdates

Provider route: POST /crm/v8/settings/automation/field_updates. Alter supplies the connection’s credentials and routing.

Install @alter-ai/sdk @alter-ai/zoho with npm, or alter-sdk-zoho with pip. Supply your connected customer’s grant ID and the arguments described below.

import { App } from "@alter-ai/sdk";
import { ZohoIntegration } from "@alter-ai/zoho";
async function execute(input: Parameters<ZohoIntegration["fieldUpdates"]["createFieldUpdates"]>[0]) {
const app = new App({ apiKey: process.env.ALTER_API_KEY! });
try {
const provider = new ZohoIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! });
const call = await provider.fieldUpdates.createFieldUpdates(input);
const result = await call.wait();
return result.bodyJson();
} finally {
await app.close();
}
}
import os
from alter_sdk import App
from alter_sdk_zoho import ZohoIntegration
async def execute(arguments):
async with App(api_key=os.environ["ALTER_API_KEY"]) as app:
provider = ZohoIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]})
call = await provider.field_updates.create_field_updates(arguments)
result = await call.wait()
return result.body_json()
FieldTypePresenceDescription and constraints
$objectRootAdditional keys: not allowed
bodyModelOptionalExpand Create Field Update — request body — body

Referenced models: Create Field Update — request body — body

Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.

FieldTypePresenceDescription and constraints
$ModelRootExpand Create Field Update — response body

Referenced models: Create Field Update — response body

10 more schemas are linked from the tables above, on the schema pages.

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 — 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 — 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 — 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 — 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

SDK function policy ID: zoho.createfieldupdates. Catalog operation: createFieldUpdates. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.

Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.

Official provider source

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.