ServiceNow Zendesk Integration Guide

Architecture Overview

Implementation Steps

var transform = new GlideTransform('Zendesk_Ticket_to_Incident');
transform.setSource(current);
transform.setTarget('incident');
var target = transform.transform();
if (target.isValid()) {
  target.setValue('assignment_group', getAssignmentGroup(current.zendesk_group_id));
  target.setValue('caller_id', lookupServiceNowUser(current.requester_id));
  target.update();
}

(function process(request, response) {
  var payload = request.body.data;
  var signature = request.getHeader('X-Zendesk-Webhook-Signature');
  
  if (!validateSignature(payload, signature)) {
    response.setStatus(401);
    return;
  }
  
  var ticketData = JSON.parse(payload);
  var gr = new GlideRecord('incident');
  if (gr.get('x_zendesk_ticket_id', ticketData.id)) {
    updateIncidentFromTicket(gr, ticketData);
  } else {
    createIncidentFromTicket(ticketData);
  }
  
  response.setStatus(200);
})(request, response);

var escalationRules = new GlideRecord('x_escalation_rules');
escalationRules.addQuery('priority', current.priority);
escalationRules.addQuery('category', current.category);
escalationRules.query();

if (escalationRules.next()) {
  current.assignment_group = escalationRules.assignment_group;
  current.escalated_from_zendesk = true;
  current.work_notes = 'Automatically escalated from Zendesk due to: ' + escalationRules.escalation_reason;
}

var testIntegration = new sn_ih.IntegrationAction('Zendesk', 'Get Ticket');
testIntegration.setParameter('connection_alias', 'Zendesk_Production');
testIntegration.setParameter('ticket_id', '12345');

var result = testIntegration.execute();
if (result.haveError()) {
  gs.error('Zendesk integration test failed: ' + result.getErrorMessage());
} else {
  gs.info('Integration test successful. Ticket data: ' + result.getResponseBody());
}

Common Use Cases

Troubleshooting

Pro Tips

• →Implement field-level change tracking by storing JSON snapshots of previous ticket states in custom ServiceNow tables, enabling delta synchronization that only updates changed fields rather than full record overwrites. This approach significantly reduces API calls and prevents unnecessary webhook triggers while maintaining complete audit trails of field-level changes across both platforms.
• →Use ServiceNow's Domain Separation feature when managing multiple Zendesk instances or customer environments by creating separate connection aliases and flow workflows for each domain. This approach ensures proper data isolation while leveraging shared spoke actions and transform map logic across multiple Zendesk tenants in MSP scenarios.
• →Configure intelligent assignment group routing by creating lookup tables that map Zendesk group IDs to ServiceNow assignment groups based on skills, time zones, and escalation policies. Include fallback logic that considers current group capacity and member availability to prevent incidents from being assigned to overloaded or offline teams.
• →Implement custom SLA alignment by creating ServiceNow business rules that calculate equivalent SLA response times based on Zendesk's customer tier mappings and support hours. This ensures ServiceNow incident SLAs reflect the original customer commitments made in Zendesk while accommodating different escalation team capabilities and schedules.
• →Create comprehensive integration health monitoring using ServiceNow's Integration Hub dashboards combined with custom scheduled jobs that verify webhook connectivity, test API authentication, and validate recent sync operations. Set up automated email notifications for integration failures that include specific error details and recommended remediation steps for faster resolution.
• →Leverage ServiceNow's REST Message versioning to maintain multiple Zendesk API endpoint configurations for different environments or API versions, enabling seamless testing and rollback capabilities during Zendesk platform updates. Include custom headers and authentication methods that can be easily switched without modifying core integration logic.

Known Limitations

• —Zendesk's API rate limits of 700 requests per minute for Professional plans and 2000 for Enterprise plans can bottleneck high-volume synchronization scenarios, requiring careful batching and retry logic to prevent timeout failures during peak support periods. The Integration Hub spoke includes basic retry mechanisms but may require custom flow logic for complex bulk operations.
• —Real-time bidirectional synchronization can create data consistency challenges when both platforms are updated simultaneously, potentially leading to conflicting field values that require manual resolution. ServiceNow's eventual consistency model may show temporary discrepancies during high-frequency update scenarios.
• —The Zendesk spoke's transform map capabilities are limited compared to custom scripting approaches, particularly for complex data manipulations like concatenating multiple Zendesk fields into single ServiceNow fields or implementing custom business logic during field mapping. Advanced transformations may require custom scripted actions.
• —Zendesk's webhook delivery doesn't guarantee ordering or exactly-once delivery, requiring ServiceNow implementations to handle duplicate webhook payloads and out-of-sequence updates gracefully. This is particularly challenging for status change workflows where the order of operations affects final incident states.
• —Integration Hub Professional license limitations restrict the number of concurrent action executions and may throttle high-volume integrations during peak periods, requiring careful flow design and potentially upgrading to Integration Hub Enterprise for large-scale implementations with thousands of daily ticket interactions.

Frequently Asked Questions