ServiceNow Zapier Integration Guide

Architecture Overview

Implementation Steps

(function process(request, response) {
    try {
        var body = request.body.data;
        var incident = new GlideRecord('incident');
        incident.initialize();
        incident.short_description = body.title || 'Incident from Zapier';
        incident.description = body.description || '';
        incident.caller_id = body.caller_sys_id || '';
        incident.urgency = body.urgency || '3';
        incident.impact = body.impact || '3';
        var sys_id = incident.insert();
        
        if (sys_id) {
            response.setStatus(201);
            response.setBody({success: true, sys_id: sys_id, number: incident.number.toString()});
        } else {
            response.setStatus(400);
            response.setBody({success: false, error: 'Failed to create incident'});
        }
    } catch (error) {
        response.setStatus(500);
        response.setBody({success: false, error: error.toString()});
    }
})(request, response);

var request = new sn_ws.RESTMessageV2('Zapier Webhook Sender', 'send_notification');
request.setEndpoint('https://hooks.zapier.com/hooks/catch/YOUR_WEBHOOK_ID/');
request.setRequestHeader('Content-Type', 'application/json');

var payload = {
    incident_number: current.number.toString(),
    state: current.state.getDisplayValue(),
    assigned_to: current.assigned_to.getDisplayValue(),
    short_description: current.short_description.toString(),
    sys_id: current.sys_id.toString()
};

request.setRequestBody(JSON.stringify(payload));
var response = request.execute();

if (response.getStatusCode() == 200) {
    gs.info('Zapier webhook sent successfully for incident: ' + current.number);
} else {
    gs.error('Failed to send Zapier webhook. Status: ' + response.getStatusCode() + ' Body: ' + response.getBody());
}

(function executeRule(current, previous /*null when async*/) {
    try {
        var request = new sn_ws.RESTMessageV2('Zapier Webhook Sender', 'send_notification');
        request.setEndpoint('https://hooks.zapier.com/hooks/catch/YOUR_WEBHOOK_ID/');
        
        var payload = {
            event_type: 'incident_updated',
            incident_number: current.number.toString(),
            state: current.state.getDisplayValue(),
            previous_state: previous ? previous.state.getDisplayValue() : '',
            assigned_to: current.assigned_to.getDisplayValue(),
            updated_by: current.sys_updated_by.toString(),
            update_timestamp: current.sys_updated_on.toString()
        };
        
        request.setRequestBody(JSON.stringify(payload));
        var response = request.execute();
        
        if (response.getStatusCode() != 200) {
            gs.error('Zapier webhook failed for incident ' + current.number + ': ' + response.getBody());
        }
    } catch (error) {
        gs.error('Error sending Zapier webhook: ' + error.toString());
    }
})(current, previous);

Common Use Cases

Troubleshooting

Pro Tips

• →Implement custom logging tables in ServiceNow to track all Zapier integration events including successful record creations, failed webhook deliveries, and data transformation errors, enabling better troubleshooting and performance monitoring. Create a dedicated 'Integration Logs' table with fields for timestamp, direction (inbound/outbound), external system, record type, success status, and error details for comprehensive audit trails.
• →Use ServiceNow's Transform Maps feature for complex data mapping scenarios where Zapier's built-in field mapping isn't sufficient, particularly when integrating with systems that have vastly different data structures or require extensive data cleansing. This approach provides more robust error handling and allows for advanced data validation rules that execute server-side in ServiceNow.
• →Configure Zapier webhook URLs with authentication tokens or API keys when possible to prevent unauthorized webhook submissions to your ServiceNow instance, and implement IP address filtering in ServiceNow to only accept webhooks from verified Zapier IP ranges. Store webhook authentication secrets in ServiceNow's encrypted credential store for additional security.
• →Leverage ServiceNow's Event Management module to create custom events for Zapier integration milestones, enabling automated notifications to administrators when integration volumes exceed thresholds or error rates spike above acceptable levels. This proactive monitoring prevents small issues from becoming major integration failures.
• →Implement batch processing capabilities in your ServiceNow Scripted REST APIs to handle high-volume scenarios where Zapier needs to send multiple records in a single webhook call, reducing API call overhead and improving overall integration performance. Use GlideRecord batch operations and proper transaction handling to ensure data consistency.
• →Create reusable REST message templates and Scripted REST API resources that can be easily cloned and customized for different Zapier integration scenarios, following consistent naming conventions and error handling patterns to reduce development time and improve maintainability across multiple integrations.

Known Limitations

• —Zapier's ServiceNow connector does not support attachment file transfers, requiring separate file handling workflows through ServiceNow's Attachment API or third-party file storage services like Google Drive or Dropbox as intermediaries. Complex file-based integrations may require custom ServiceNow applications or direct API development.
• —The integration is limited by ServiceNow's standard REST API rate limits of 5,000 requests per hour per user, which can be restrictive for high-volume automated workflows or bulk data synchronization scenarios. Organizations requiring higher throughput should consider Integration Hub Professional licenses or direct database integration approaches.
• —Zapier's webhook delivery is not guaranteed and follows an eventual consistency model with automatic retries, meaning time-sensitive integrations may experience delays of several minutes during Zapier system maintenance or high load periods. Critical real-time integrations should implement direct API calls or ServiceNow's native integration capabilities.
• —Complex ServiceNow workflows involving multiple approval stages, advanced business rule logic, or custom UI policies may not translate effectively through Zapier's simplified trigger-action model, requiring careful workflow design or hybrid integration approaches that combine Zapier automation with ServiceNow's native orchestration capabilities.
• —ServiceNow reference field lookups through Zapier require explicit sys_id values rather than display names, necessitating additional lookup steps or data transformation logic to resolve human-readable values to ServiceNow's internal identifiers, which can complicate integration workflows and increase task consumption.

Frequently Asked Questions