How Custom Field Sync Works Between Zendesk and ServiceNow
When syncing custom fields between Zendesk and ServiceNow, the process relies on a bidirectional mechanism that moves data in both directions automatically.
Syncing custom fields between Zendesk and ServiceNow relies on a bidirectional mechanism that moves data automatically in both directions.
Tools like Exalate manage this through two scripts:
- Outgoing sync copies issue.customFields.fieldName to replica.customFields.fieldName.
- Incoming sync maps replica.customFields.fieldName.value to ServiceNow’s internal fields.
Changes trigger synchronization immediately, keeping both platforms updated in real time.
Status updates, such as “resolved” changing to “solved,” propagate across both systems after a reload.
This structure guarantees no manual transfers are needed.
Each platform reflects accurate, current data, maintaining a reliable single source of truth throughout the workflow. Field mappings can be configured manually using Unito’s cog icon to match custom field options between the two platforms.
The integration is built to meet ISO 27001, SOC 2 Type II, GDPR, and other compliance standards, ensuring that all synced custom field data remains secure and protected throughout the process.
Elastic scalability supports growing workloads, providing cloud-native scalability to handle peaks without manual intervention.
How Zendesk Custom Fields Map to ServiceNow Fields
Mapping Zendesk custom fields to ServiceNow requires identifying each field by its unique ID, then writing scripts that move data between the two platforms. Admins locate field IDs in Admin Center under Objects and Rules > Tickets > Fields. Scripts then reference these IDs directly. This process benefits from real-time visibility to monitor sync status and errors.
Key mapping methods include:
- Direct assignment: `issue.customFields.”T Applications”.value = replica.product_name`
- Dictionary mapping: `def productMap = [“Buoy” : “Buoy”]` translates values between systems
- REST API delivery: JSON format sends field data using `”custom_fields”:[{“id”: “360046171833”, “value”: ” “}]`
Data types must match for sync to work correctly. Dropdown fields may fail to populate in older versions of Exalate for Zendesk, requiring an upgrade to resolve the issue.
When configuring field synchronization, it is important to note that read-only and lookup fields cannot be mapped to custom fields in PagerDuty, and the same restriction applies when evaluating non-editable field types across similar integration workflows.
What Gets Updated: and How Fast?
Syncing Zendesk and ServiceNow moves specific fields in both directions, and knowing which fields update — and how quickly — helps teams set accurate expectations.
These four field types update during a sync:
- Short descriptions and body content transfer from Zendesk to ServiceNow incident fields.
- Status changes, like resolved tickets, propagate across both platforms instantly.
- Custom fields populate using internal names and ID-value pairs through the API.
- Comments, notes, and attachments sync bidirectionally, updating ticket history in real time.
Most updates reflect immediately after an agent makes a change.
Some default syncs run every 24 hours at 3 AM.
The integration uses a Business Rule to trigger data transmission automatically when a new incident is created in ServiceNow.
For teams using Zapier to manage the integration, polling triggers check for new data every 15 minutes on the Free plan.
Organizations leveraging APIs are 24% more likely to achieve profitability.
How Scripted Field Mapping Handles the Sync Logic
Behind every successful Zendesk-ServiceNow sync is a layer of scripted logic that handles what automatic mapping cannot.
Custom fields require manual scripting because automatic mapping consistently fails to populate them correctly.
Scripts operate differently depending on direction:
- Incoming (Zendesk side): Pulls values using `replica.custom_fields.field_name.value` and these scripts should enforce data governance to maintain consistency across systems.
- Outbound (ServiceNow side): Constructs a `custom_fields` array containing ID and value pairs
ServiceNow business rules trigger these scripts on incident creation or updates, sending JSON payloads via RESTMessageV2.
Fields like category and subcategory get explicitly mapped this way.
Data types must also match; otherwise, scripts convert incompatible formats before syncing completes. Editing a ServiceNow field’s data type after mapping is created can cause syncing issues due to a type mismatch with the paired custom field.
Which Tools Sync Zendesk and ServiceNow Without Custom Code?
Several no-code tools eliminate the need for custom scripting when syncing Zendesk and ServiceNow. Each option handles bidirectional data flow through visual interfaces designed for non-technical users.
- Unito completes setup in 15 minutes and syncs all ServiceNow record types with real-time field updates. This approach benefits from cloud-native architecture that reduces maintenance for integrations.
- Getint configures one-way or bidirectional sync in 5 minutes with auto-mapping for fields, attachments, and comments.
- ZigiOps automates real-time synchronization while reducing manual entry errors across teams. ZigiOps supports authentication via basic credentials or OAuth and recommends creating a dedicated user account for audit trails and troubleshooting.
- Zapier connects ServiceNow triggers to Zendesk actions, eliminating duplicate record management without coding skills.
When evaluating these tools for enterprise use, security and compliance standards are an important consideration. Unito maintains SOC 2 Type 2 compliance alongside adherence to GDPR and CCPA regulations.
