ServiceNow Webex Integration Guide

Architecture Overview

Implementation Steps

// Example message template for incident notifications
var message = 'Incident Alert: ' + current.number + '\n' +
              'Priority: ' + current.priority.getDisplayValue() + '\n' +
              'Description: ' + current.short_description + '\n' +
              'Assigned to: ' + current.assignment_group.getDisplayValue() + '\n' +
              'Link: ' + gs.getProperty('glide.servlet.uri') + 'incident.do?sys_id=' + current.sys_id;

// Script to update record with meeting URL after creation
var gr = new GlideRecord('problem');
if (gr.get(inputs.record_sys_id)) {
    gr.setValue('u_webex_meeting_url', outputs.meeting_url);
    gr.setValue('u_meeting_id', outputs.meeting_id);
    gr.update();
    gs.info('Updated problem ' + gr.number + ' with Webex meeting URL');
}

(function process(request, response) {
    var payload = JSON.parse(request.body.dataString);
    
    if (payload.data && payload.data.text && payload.data.text.indexOf('/incident') === 0) {
        var incidentNum = payload.data.text.split(' ')[1];
        var gr = new GlideRecord('incident');
        gr.addQuery('number', incidentNum);
        gr.query();
        
        if (gr.next()) {
            var responseMsg = 'Incident: ' + gr.number + '\nState: ' + gr.state.getDisplayValue() + '\nAssigned: ' + gr.assigned_to.getDisplayValue();
            // Send response back to Webex space
            sendWebexMessage(payload.data.roomId, responseMsg);
        }
    }
    
    response.setStatus(200);
})(request, response);

// Enhanced message formatting with mentions and HTML
var messageHtml = '<h3>🚨 Critical Incident Alert</h3>' +
                 '<p><strong>Incident:</strong> ' + current.number + '</p>' +
                 '<p><strong>Priority:</strong> <span style="color:red">' + current.priority.getDisplayValue() + '</span></p>' +
                 '<p><strong>Description:</strong> ' + current.short_description + '</p>' +
                 '<p><a href="' + gs.getProperty('glide.servlet.uri') + 'incident.do?sys_id=' + current.sys_id + '">View in ServiceNow</a></p>';

// Include person ID for @mentions in critical situations
var mentionPersonId = gs.getProperty('webex.oncall.person.id');

// Health check script for monitoring Webex connectivity
try {
    var r = new sn_ws.RESTMessageV2('Webex Health Check', 'GET');
    r.setEndpoint('https://webexapis.com/v1/people/me');
    r.setRequestHeader('Authorization', 'Bearer ' + credential_token);
    var response = r.execute();
    
    if (response.getStatusCode() != 200) {
        gs.error('Webex API health check failed: ' + response.getStatusCode());
        // Trigger fallback notification mechanism
    } else {
        gs.info('Webex integration health check passed');
    }
} catch (ex) {
    gs.error('Webex health check exception: ' + ex.getMessage());
}

Common Use Cases

Troubleshooting

Pro Tips

• →Implement message deduplication logic in your Flow Designer workflows to prevent spam when multiple business rules trigger simultaneously on the same record. Use a custom table to track recent notifications with a combination of record sys_id and space ID as unique keys, with automatic cleanup of entries older than 10 minutes.
• →Configure separate Webex spaces for different incident priorities and service categories to reduce noise and ensure appropriate team members receive relevant notifications. Create space naming conventions that include environment identifiers (DEV/TEST/PROD) to prevent confusion during multi-environment deployments and testing activities.
• →Leverage ServiceNow's scheduled jobs to create daily or weekly summary reports sent to management Webex spaces, including metrics like SLA performance, ticket volumes, and team productivity statistics. Use the Webex adaptive card format for rich, interactive reports that allow managers to drill down into specific data points directly from the collaboration space.
• →Implement proper error handling and fallback mechanisms in your Integration Hub flows by adding parallel paths that send email notifications when Webex API calls fail. This ensures critical communications reach their intended recipients even during Webex service outages or network connectivity issues between ServiceNow and Cisco's infrastructure.
• →Create custom ServiceNow UI actions that allow agents to manually trigger Webex notifications or meeting creation for exceptional cases that don't fit automated workflow patterns. Include validation logic to prevent duplicate notifications and provide visual feedback to users about the success or failure of manual Webex integration actions.
• →Use ServiceNow's Connection & Credential Alias rotation capabilities to implement bot token refresh procedures, even though Webex bot tokens don't expire, to maintain security best practices and prepare for potential token compromise scenarios. Document the token rotation process and assign backup administrators who can regenerate credentials during primary administrator absence.

Known Limitations

• —Webex APIs enforce rate limiting of 300 requests per minute per application, which can be exceeded during high-incident periods or when processing bulk operations. ServiceNow administrators should implement queuing mechanisms and consider using multiple bot applications for high-volume environments to distribute load across different rate limit buckets.
• —The Integration Hub Webex Teams spoke requires Professional licensing and cannot be used with the base IntegrationHub Starter license included in most ServiceNow subscriptions. Organizations must purchase additional licensing to access the full spoke functionality, with alternative custom REST message implementations possible but requiring additional development effort.
• —Webex webhook deliveries to ServiceNow instances behind corporate firewalls require network infrastructure changes to allow inbound connections from Cisco's cloud IP ranges. Many organizations' security policies prohibit direct internet access to ServiceNow instances, limiting bidirectional integration capabilities and requiring MID Server implementations or DMZ proxy configurations.
• —Message formatting and adaptive card features have varying support across different Webex client versions and platforms, with mobile clients often displaying simplified versions of rich content. Testing should include verification across desktop, web, and mobile Webex applications to ensure consistent user experience across all platforms used by your organization.
• —Bot applications in Webex cannot automatically join spaces and must be manually added by space moderators, creating administrative overhead for dynamic space creation workflows. Organizations with frequent space turnover or project-based collaboration patterns may find the manual bot management requirements cumbersome compared to other collaboration platforms with automatic bot provisioning capabilities.

Frequently Asked Questions