ServiceNow Zoom Integration Guide

Architecture Overview

Implementation Steps

// Example data pill mapping for Zoom meeting creation
// Topic: {{trigger.current.short_description}}
// Agenda: Priority {{trigger.current.priority}} incident: {{trigger.current.description}}
// Start Time: {{trigger.current.sys_created_on.add(5, 'minutes')}}
// Duration: 60
// Password: {{trigger.current.number}}

// Update Record action field mappings
// u_zoom_meeting_id: {{action[Create_Meeting].result.id}}
// u_zoom_join_url: {{action[Create_Meeting].result.join_url}}
// u_zoom_meeting_password: {{action[Create_Meeting].result.password}}
// work_notes: Zoom meeting created: {{action[Create_Meeting].result.join_url}}

// Test script to verify Zoom meeting creation
var gr = new GlideRecord('incident');
gr.addQuery('number', 'INC0000123'); // Replace with test incident number
gr.query();
if (gr.next()) {
    gs.info('Zoom Meeting ID: ' + gr.u_zoom_meeting_id);
    gs.info('Join URL: ' + gr.u_zoom_join_url);
    gs.info('Meeting Password: ' + gr.u_zoom_meeting_password);
}

// Error handling script for Flow Designer
if (action.Create_Meeting.result.error) {
    var errorMsg = 'Zoom meeting creation failed for incident ' + trigger.current.number;
    errorMsg += ': ' + action.Create_Meeting.result.error_message;
    gs.error(errorMsg);
    // Update incident work notes with error information
    trigger.current.work_notes = 'Zoom meeting creation failed. Please create meeting manually.';
}

Common Use Cases

Troubleshooting

Pro Tips

• →Implement custom business logic in Flow Designer to dynamically set meeting durations based on incident priority levels - for example, P1 incidents get 2-hour meetings while P3 incidents get 30-minute meetings, ensuring appropriate time allocation for resolution activities.
• →Create a scheduled Flow Designer flow that runs daily to clean up completed Zoom meetings by calling the Delete Meeting API for incidents that have been resolved for more than 7 days, helping maintain your Zoom account's meeting storage limits and reducing clutter.
• →Configure meeting recording settings in your Zoom spoke actions to automatically record sessions for compliance purposes, then use additional Flow Designer actions to download and attach recordings to ServiceNow records for audit trails and knowledge capture.
• →Set up custom notification templates that include not just the meeting URL but also relevant ServiceNow record context, assigned team information, and escalation contacts, making the meeting invitation serve as a comprehensive incident briefing document.
• →Implement error retry logic using Flow Designer's built-in retry capabilities with exponential backoff for Zoom API calls, particularly during high-traffic periods when rate limiting might cause temporary failures.
• →Create dashboard widgets and reports to track meeting creation metrics, including success rates, most common failure reasons, and integration usage patterns across different service management processes for continuous improvement insights.

Known Limitations

• —Zoom's API rate limit of 100 requests per second per account can become a constraint in large organizations with high incident volumes, potentially causing meeting creation delays during major outage events when multiple incidents trigger simultaneously. Consider implementing queuing mechanisms or staggered execution for bulk operations.
• —The Integration Hub Zoom spoke only supports basic meeting creation and management functions - advanced features like breakout room configuration, polling setup, or custom branding require direct REST API calls using custom scripting outside of the pre-built spoke actions. Meeting capacity is also limited by your Zoom license tier and concurrent meeting allowances.
• —OAuth token refresh automation is not built into the spoke actions, requiring manual token refresh or custom refresh logic implementation when tokens expire after extended periods of inactivity. Additionally, the integration requires the ServiceNow instance to maintain outbound internet connectivity, which may not be suitable for air-gapped or highly restricted network environments.

Frequently Asked Questions