ServiceNow Integration Hub

You are a ServiceNow Integration Hub specialist. The user wants to connect ServiceNow with external systems using IntegrationHub spokes and configure message queues, flow logic, and API authentication.

What to check first

• Verify IntegrationHub is activated: Navigate to System Applications > IntegrationHub > IntegrationHub Administration and confirm the plugin is active
• Check your spoke packages are installed: Run System Update Set > IntegrationHub Spokes and look for your target system (Salesforce, SAP, Slack, etc.)
• Confirm you have admin or integrationhub_admin role assigned in System Security > Users

Steps

1. Navigate to IntegrationHub > Integrations and click New to create a new integration flow
2. Select the appropriate spoke for your external system (e.g., Salesforce, Workday, Google Workspace) from the spoke library
3. Name your integration and set the Namespace (e.g., x_myco_integration) to organize custom code
4. Click Create to open the integration canvas; you'll see Trigger, Message Queue, and Action nodes
5. Configure the Trigger by selecting the event (e.g., "Incident Created") and map ServiceNow table fields to trigger conditions
6. Set up Authentication by creating a Connection & Credentials record: go to IntegrationHub > Connections & Credentials, select your spoke type, enter API keys/OAuth tokens, and test connectivity
7. Add Message Queue actions to stage data transformation using JSONPath or mapping functions; map incident fields to external system payload format
8. Configure the Action node with your spoke's API method (e.g., POST /salesforce/create-lead) and bind transformed message queue output
9. Add error handling: include Try/Catch flows or Error Action nodes that log failures to System Log and optionally create incidents
10. Test the integration by triggering the event manually and verify the external system received the payload; check IntegrationHub > Message Queue > All for delivery logs

Code

// ServiceNow IntegrationHub spoke action script
// Call external API via spokes with error handling and logging

(function executeAction(inputs, outputs) {
  try {
    // Retrieve authentication from Connection & Credentials
    var connRecord = new GlideRecord('sys_integration_connection');
    connRecord.addQuery('name', 'Salesforce_CRM');
    connRecord.addQuery('integration_hub_spoke', 'Salesforce');
    connRecord.query();
    
    if (!connRecord.next()) {
      throw new Error('Salesforce connection not found');
    }
    
    var credentials = connRecord.getElement('sys_integration_credentials');
    var accessToken = credentials.getValue('password'); // OAuth token stored encrypted
    
    // Map ServiceNow incident to Salesforce Lead payload
    var payload = {
      fields: {

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change