Skip to main content

Check out Port for yourself 

ServiceNow

Port's ServiceNow integration allows you to model ServiceNow resources in your software catalog and ingest data into them.

Overview

This integration allows you to:

  • Map and organize your desired ServiceNow resources and their metadata in Port (see supported resources below).

Supported Resources

The resources that can be ingested from ServiceNow into Port are listed below.

  • User - (<your-servicenow-url>/api/now/table/sys_user_group)
  • Service Catalog - (<your-servicenow-url>/api/now/table/sc_catalog)
  • Incident - (<your-servicenow-url>/api/now/table/incident)

Setup

Choose one of the following installation methods:

Using this installation option means that the integration will be hosted by Port, with a customizable resync interval to ingest data into Port.

Live event support

Currently, live events are not supported for integrations hosted by Port.
Resyncs will be performed periodically (with a configurable interval), or manually triggered by you via Port's UI.

Therefore, real-time events (including GitOps) will not be ingested into Port immediately.
Support for live events is WIP and will be supported in the near future.

Self-hosted installation

Alternatively, you can install the integration using the Real-time (self-hosted) method to update Port in real time using webhooks.

Installation

To install, follow these steps:

  1. Go to the Data sources page of your portal.

  2. Click on the + Data source button in the top-right corner.

  3. Click on the relevant integration in the list.

  4. Under Select your installation method, choose Hosted by Port.

  5. Configure the integration settings and application settings as you wish (see below for details).

Application settings

Every integration hosted by Port has the following customizable application settings, which are configurable after installation:

  • Resync interval: The frequency at which Port will ingest data from the integration. There are various options available, ranging from every 1 hour to once a day.

  • Send raw data examples: A boolean toggle (enabled by default). If enabled, raw data examples will be sent from the integration to Port. These examples are used when testing your mapping configuration, they allow you to run your jq expressions against real data and see the results.

Integration settings

Every integration has its own tool-specific settings, under the Integration settings section.
Each of these settings has an ⓘ icon next to it, which you can hover over to see a description of the setting.

Port secrets

Some integration settings require sensitive pieces of data, such as tokens.
For these settings, Port secrets will be used, ensuring that your sensitive data is encrypted and secure.

When filling in such a setting, its value will be obscured (shown as ••••••••).
For each such setting, Port will automatically create a secret in your organization.

To see all secrets in your organization, follow these steps.

Port source IP addresses

When using this installation method, Port will make outbound calls to your 3rd-party applications from static IP addresses.
You may need to add these addresses to your allowlist, in order to allow Port to interact with the integrated service:

54.73.167.226  
63.33.143.237
54.76.185.219

Configuration

Port integrations use a YAML mapping block to ingest data from the third-party api into Port.

The mapping makes use of the JQ JSON processor to select, modify, concatenate, transform and perform other operations on existing fields and values from the integration API.

Examples

Examples of blueprints and the relevant integration configurations:

Group

Group blueprint
{
"identifier": "servicenowGroup",
"title": "Servicenow Group",
"icon": "Servicenow",
"schema": {
"properties": {
"description": {
"title": "Description",
"type": "string"
},
"isActive": {
"title": "Is active",
"type": "boolean"
},
"createdOn": {
"title": "Created On",
"type": "string",
"format": "date-time"
},
"createdBy": {
"title": "Created By",
"type": "string"
}
},
"required": []
},
"mirrorProperties": {},
"calculationProperties": {},
"aggregationProperties": {},
"relations": {}
}
Integration configuration
createMissingRelatedEntities: true
deleteDependentEntities: true
resources:
- kind: sys_user_group
selector:
query: "true"
port:
entity:
mappings:
identifier: .sys_id
title: .name
blueprint: '"servicenowGroup"'
properties:
description: .description
isActive: .active
createdOn: '.sys_created_on | (strptime("%Y-%m-%d %H:%M:%S") | strftime("%Y-%m-%dT%H:%M:%SZ"))'
createdBy: .sys_created_by

Service Catalog

Service catalog blueprint
{
"identifier": "servicenowCatalog",
"title": "Servicenow Catalog",
"icon": "Servicenow",
"schema": {
"properties": {
"description": {
"title": "Description",
"type": "string"
},
"isActive": {
"title": "Is Active",
"type": "boolean"
},
"createdOn": {
"title": "Created On",
"type": "string",
"format": "date-time"
},
"createdBy": {
"title": "Created By",
"type": "string"
}
},
"required": []
},
"mirrorProperties": {},
"calculationProperties": {},
"aggregationProperties": {},
"relations": {}
}
Integration configuration
createMissingRelatedEntities: true
deleteDependentEntities: true
resources:
- kind: sc_catalog
selector:
query: "true"
port:
entity:
mappings:
identifier: .sys_id
title: .title
blueprint: '"servicenowCatalog"'
properties:
description: .description
isActive: .active
createdOn: '.sys_created_on | (strptime("%Y-%m-%d %H:%M:%S") | strftime("%Y-%m-%dT%H:%M:%SZ"))'
createdBy: .sys_created_by

Incident

Incident blueprint
{
"identifier": "servicenowIncident",
"title": "Servicenow Incident",
"icon": "Servicenow",
"schema": {
"properties": {
"category": {
"title": "Category",
"type": "string"
},
"reopenCount": {
"title": "Reopen Count",
"type": "string"
},
"severity": {
"title": "Severity",
"type": "string"
},
"assignedTo": {
"title": "Assigned To",
"type": "string",
"format": "url"
},
"urgency": {
"title": "Urgency",
"type": "string"
},
"contactType": {
"title": "Contact Type",
"type": "string"
},
"createdOn": {
"title": "Created On",
"type": "string",
"format": "date-time"
},
"createdBy": {
"title": "Created By",
"type": "string"
},
"isActive": {
"title": "Is Active",
"type": "boolean"
},
"priority": {
"title": "Priority",
"type": "string"
}
},
"required": []
},
"mirrorProperties": {},
"calculationProperties": {},
"aggregationProperties": {},
"relations": {}
}
Integration configuration
createMissingRelatedEntities: true
deleteDependentEntities: true
resources:
- kind: incident
selector:
query: "true"
port:
entity:
mappings:
identifier: .number | tostring
title: .short_description
blueprint: '"servicenowIncident"'
properties:
category: .category
reopenCount: .reopen_count
severity: .severity
assignedTo: .assigned_to.link
urgency: .urgency
contactType: .contact_type
createdOn: '.sys_created_on | (strptime("%Y-%m-%d %H:%M:%S") | strftime("%Y-%m-%dT%H:%M:%SZ"))'
createdBy: .sys_created_by
isActive: .active
priority: .priority

Let's Test It

This section includes a sample response data from ServiceNow. In addition, it includes the entity created from the resync event based on the Ocean configuration provided in the previous section.

Payload

Here is an example of the payload structure from ServiceNow:

Group response data
{
"parent": "",
"manager": "",
"roles": "",
"sys_mod_count": "0",
"active": "true",
"description": "\n\t\tGroup for all people who have the Analytics Admin role\n\t",
"source": "",
"sys_updated_on": "2020-03-17 11:39:14",
"sys_tags": "",
"type": "",
"sys_id": "019ad92ec7230010393d265c95c260dd",
"sys_updated_by": "admin",
"cost_center": "",
"default_assignee": "",
"sys_created_on": "2020-03-17 11:39:14",
"name": "Analytics Settings Managers",
"exclude_manager": "false",
"email": "",
"include_members": "false",
"sys_created_by": "admin"
}
Service Catalog response data
{
"manager": {
"link": "https://dev229583.service-now.com/api/now/table/sys_user/6816f79cc0a8016401c5a33be04be441",
"value": "6816f79cc0a8016401c5a33be04be441"
},
"sys_mod_count": "0",
"active": "true",
"description": "Description for service catalog",
"desktop_continue_shopping": "",
"enable_wish_list": "false",
"sys_updated_on": "2023-12-14 15:30:54",
"sys_tags": "",
"title": "Test Service Catalog",
"sys_class_name": "sc_catalog",
"desktop_image": "",
"sys_id": "56e48e6a9743311083e6ff0de053af56",
"sys_package": {
"link": "https://dev229583.service-now.com/api/now/table/sys_package/global",
"value": "global"
},
"desktop_home_page": "",
"sys_update_name": "sc_catalog_56e48e6a9743311083e6ff0de053af56",
"sys_updated_by": "admin",
"sys_created_on": "2023-12-14 15:30:54",
"sys_name": "Test Service Catalog",
"sys_scope": {
"link": "https://dev229583.service-now.com/api/now/table/sys_scope/global",
"value": "global"
},
"editors": "",
"sys_created_by": "admin",
"sys_policy": ""
}
Incident response data
{
"parent": "",
"made_sla": "true",
"caused_by": "",
"watch_list": "",
"upon_reject": "cancel",
"sys_updated_on": "2016-12-14 02:46:44",
"child_incidents": "0",
"hold_reason": "",
"origin_table": "",
"task_effective_number": "INC0000060",
"approval_history": "",
"number": "INC0000060",
"resolved_by": {
"link": "https://dev229583.service-now.com/api/now/v1/table/sys_user/5137153cc611227c000bbd1bd8cd2007",
"value": "5137153cc611227c000bbd1bd8cd2007"
},
"sys_updated_by": "employee",
"opened_by": {
"link": "https://dev229583.service-now.com/api/now/v1/table/sys_user/681ccaf9c0a8016400b98a06818d57c7",
"value": "681ccaf9c0a8016400b98a06818d57c7"
},
"user_input": "",
"sys_created_on": "2016-12-12 15:19:57",
"sys_domain": {
"link": "https://dev229583.service-now.com/api/now/v1/table/sys_user_group/global",
"value": "global"
},
"state": "7",
"route_reason": "",
"sys_created_by": "employee",
"knowledge": "false",
"order": "",
"calendar_stc": "102197",
"closed_at": "2016-12-14 02:46:44",
"cmdb_ci": {
"link": "https://dev229583.service-now.com/api/now/v1/table/cmdb_ci/109562a3c611227500a7b7ff98cc0dc7",
"value": "109562a3c611227500a7b7ff98cc0dc7"
},
"delivery_plan": "",
"contract": "",
"impact": "2",
"active": "false",
"work_notes_list": "",
"business_service": {
"link": "https://dev229583.service-now.com/api/now/v1/table/cmdb_ci_service/27d32778c0a8000b00db970eeaa60f16",
"value": "27d32778c0a8000b00db970eeaa60f16"
},
"business_impact": "",
"priority": "3",
"sys_domain_path": "/",
"rfc": "",
"time_worked": "",
"expected_start": "",
"opened_at": "2016-12-12 15:19:57",
"business_duration": "1970-01-01 08:00:00",
"group_list": "",
"work_end": "",
"caller_id": {
"link": "https://dev229583.service-now.com/api/now/v1/table/sys_user/681ccaf9c0a8016400b98a06818d57c7",
"value": "681ccaf9c0a8016400b98a06818d57c7"
},
"reopened_time": "",
"resolved_at": "2016-12-13 21:43:14",
"approval_set": "",
"subcategory": "email",
"work_notes": "",
"universal_request": "",
"short_description": "Unable to connect to email",
"close_code": "Solved (Permanently)",
"correlation_display": "",
"delivery_task": "",
"work_start": "",
"assignment_group": {
"link": "https://dev229583.service-now.com/api/now/v1/table/sys_user_group/287ebd7da9fe198100f92cc8d1d2154e",
"value": "287ebd7da9fe198100f92cc8d1d2154e"
},
"additional_assignee_list": "",
"business_stc": "28800",
"cause": "",
"description": "I am unable to connect to the email server. It appears to be down.",
"origin_id": "",
"calendar_duration": "1970-01-02 04:23:17",
"close_notes": "This incident is resolved.",
"notify": "1",
"service_offering": "",
"sys_class_name": "incident",
"closed_by": {
"link": "https://dev229583.service-now.com/api/now/v1/table/sys_user/681ccaf9c0a8016400b98a06818d57c7",
"value": "681ccaf9c0a8016400b98a06818d57c7"
},
"follow_up": "",
"parent_incident": "",
"sys_id": "1c741bd70b2322007518478d83673af3",
"contact_type": "self-service",
"reopened_by": "",
"incident_state": "7",
"urgency": "2",
"problem_id": "",
"company": {
"link": "https://dev229583.service-now.com/api/now/v1/table/core_company/31bea3d53790200044e0bfc8bcbe5dec",
"value": "31bea3d53790200044e0bfc8bcbe5dec"
},
"reassignment_count": "2",
"activity_due": "2016-12-13 01:26:36",
"assigned_to": {
"link": "https://dev229583.service-now.com/api/now/v1/table/sys_user/5137153cc611227c000bbd1bd8cd2007",
"value": "5137153cc611227c000bbd1bd8cd2007"
},
"severity": "3",
"comments": "",
"approval": "not requested",
"sla_due": "",
"comments_and_work_notes": "",
"due_date": "",
"sys_mod_count": "15",
"reopen_count": "0",
"sys_tags": "",
"escalation": "0",
"upon_approval": "proceed",
"correlation_id": "",
"location": "",
"category": "inquiry"
}

Mapping Result

The combination of the sample payload and the Ocean configuration generates the following Port entity:

Group entity in Port
{
"identifier": "019ad92ec7230010393d265c95c260dd",
"title": "Analytics Settings Managers",
"icon": null,
"blueprint": "servicenowGroup",
"team": [],
"properties": {
"description": "\n\t\tGroup for all people who have the Analytics Admin role\n\t",
"isActive": true,
"createdOn": "2020-03-17T11:39:14Z",
"createdBy": "admin"
},
"relations": {},
"createdAt": "2023-12-18T08:37:21.637Z",
"createdBy": "hBx3VFZjqgLPEoQLp7POx5XaoB0cgsxW",
"updatedAt": "2023-12-18T08:37:21.637Z",
"updatedBy": "hBx3VFZjqgLPEoQLp7POx5XaoB0cgsxW"
}
Service catalog entity in Port
{
"identifier": "56e48e6a9743311083e6ff0de053af56",
"title": "Test Service Catalog",
"icon": null,
"blueprint": "servicenowCatalog",
"team": [],
"properties": {
"description": "Description for service catalog",
"isActive": true,
"createdOn": "2023-12-14T15:30:54Z",
"createdBy": "admin"
},
"relations": {},
"createdAt": "2023-12-18T08:37:28.087Z",
"createdBy": "hBx3VFZjqgLPEoQLp7POx5XaoB0cgsxW",
"updatedAt": "2023-12-18T08:37:28.087Z",
"updatedBy": "hBx3VFZjqgLPEoQLp7POx5XaoB0cgsxW"
}
Incident entity in Port
{
"identifier": "INC0000060",
"title": "Unable to connect to email",
"icon": null,
"blueprint": "servicenowIncident",
"team": [],
"properties": {
"category": "inquiry",
"reopenCount": "0",
"severity": "3",
"assignedTo": "https://dev229583.service-now.com/api/now/table/sys_user/5137153cc611227c000bbd1bd8cd2007",
"urgency": "2",
"contactType": "self-service",
"createdOn": "2016-12-12T15:19:57Z",
"createdBy": "employee",
"isActive": false,
"priority": "3"
},
"relations": {},
"createdAt": "2023-12-15T14:52:06.347Z",
"createdBy": "hBx3VFZjqgLPEoQLp7POx5XaoB0cgsxW",
"updatedAt": "2023-12-15T15:34:18.248Z",
"updatedBy": "hBx3VFZjqgLPEoQLp7POx5XaoB0cgsxW"
}

Relevant Guides

For relevant guides and examples, see the guides section.

Alternative installation via webhook

While the Ocean integration described above is the recommended installation method, you may prefer to use a webhook to ingest data from ServiceNow. If so, use the following instructions:

Note that when using the webhook installation method, data will be ingested into Port only when the webhook is triggered.

Webhook installation (click to expand)

In this example you are going to create a webhook integration between ServiceNow and Port, which will ingest ServiceNow change requests into Port. This integration will involve setting up a webhook to receive notifications from Servicenow whenever a change request is created or updated.

Import ServiceNow change request

Port configuration

Create the blueprint definition:

Servicenow change request blueprint
{
"identifier": "servicenowChangeRequest",
"title": "Servicenow Change Request",
"icon": "Servicenow",
"schema": {
"properties": {
"number": {
"title": "Change Number",
"type": "string"
},
"description": {
"title": "Description",
"type": "string"
},
"priority": {
"title": "Priority",
"type": "string"
},
"state": {
"icon": "DefaultProperty",
"title": "State",
"type": "string"
},
"createdOn": {
"title": "Created On",
"type": "string",
"format": "date-time"
},
"createdBy": {
"title": "Created By",
"type": "string"
},
"category": {
"type": "string",
"title": "Category"
},
"approval": {
"title": "Approval",
"icon": "DefaultProperty",
"type": "string",
"enum": [
"approved",
"not requested",
"requested",
"rejected"
],
"enumColors": {
"approved": "green",
"not requested": "turquoise",
"requested": "yellow",
"rejected": "pink"
}
},
"tags": {
"type": "string",
"title": "Tags"
}
},
"required": []
},
"mirrorProperties": {},
"calculationProperties": {},
"aggregationProperties": {},
"relations": {}
}

Create the following webhook configuration using Port UI

Servicenow webhook configuration
  1. Basic details tab - fill the following details:

    1. Title : Servicenow Mapper;
    2. Identifier : servicenow_mapper;
    3. Description : A webhook configuration to map Servicenow change requests to Port;
    4. Icon : Servicenow;
  2. Integration configuration tab - fill the following JQ mapping:

    [
    {
    "blueprint": "servicenowChangeRequest",
    "operation": "create",
    "filter": "true",
    "entity": {
    "identifier": ".body.sys_id | tostring",
    "title": ".body.short_description | tostring",
    "properties": {
    "number": ".body.number",
    "state": ".body.phase_state",
    "approval": ".body.approval",
    "category": ".body.category",
    "priority": ".body.priority",
    "description": ".body.description",
    "service": ".body.business_service",
    "tags": ".body.tags",
    "createdOn": ".body.sys_updated_on",
    "createdBy": ".body.opened_by"
    }
    }
    }
    ]
  3. Scroll down to Advanced settings, leave the form blank and click Save at the bottom of the page

Create a webhook in ServiceNow

  1. Log in to your ServiceNow instance
  2. Go to System Definition > Business Rules.
  3. Click New to create a business rule:
    • Name: Change Request Webhook
    • Table: Change Request [change_request]
    • Is Active, Advanced: Check both
  4. In the When to run tab, provide the following details:
    • Insert, Update: Check both
    • When: Async
    • Order: leave the default value of 100
  5. In the Advanced tab, add the following script:
ServiceNow configuration code (click to expand)
(function executeRule(current, previous /*null when async*/) {

gs.info('Triggering outbound REST API call for Change Request ID: ' + current.number);

if (current == null){
gs.error('Current record is null. Exiting the Business Rule.');
return;
}

// Prepare the REST message
var restMessage = new sn_ws.RESTMessageV2();
restMessage.setHttpMethod('POST');
restMessage.setEndpoint('https://ingest.getport.io/<WEBHOOK_KEY>');
restMessage.setRequestHeader('Content-Type', 'application/json');

// Construct the payload with additional fields
var payload = {
"sys_id": current.sys_id.toString(),
"number": current.number.toString(),
"state": current.state.toString(),
"short_description": current.short_description.toString(),
"description": current.description.toString(),
"sys_updated_by": current.sys_updated_by.toString(),
"sys_updated_on": current.sys_updated_on.toString(),
"approval": current.approval.toString(),

"priority": current.priority ? current.priority.toString() : '',
"phase": current.phase ? current.phase.toString() : '',
"business_service": current.business_service ? current.business_service.toString() : '',
"phase_state": current.phase_state ? current.phase_state.toString() : '',
"category": current.category ? current.category.toString() : '',
"tags": current.u_external_tag ? current.sys_tags.toString() : '',

"impact": current.impact ? current.impact.toString() : '',
"urgency": current.urgency ? current.urgency.toString() : '',
"risk": current.risk ? current.risk.toString() : '',
"assignment_group": current.assignment_group ? current.assignment_group.toString() : '',
"opened_by": current.opened_by ? current.opened_by.toString() : '',
"sys_domain": current.sys_domain ? current.sys_domain.toString() : ''
};

// Set the request body with the payload
restMessage.setRequestBody(JSON.stringify(payload));

// Execute the outbound REST call
try {
var response = restMessage.execute(); // Use async to avoid blocking
gs.info('Business Rule executed for Change Request: ' + current.number.toString());
gs.info('Response Status Code: ' + response.getStatusCode());
gs.info('Response Body: ' + response.getBody());
} catch (error) {
gs.error('Error in outbound REST call: ' + error.message);
}

})(current, previous);
  1. Save and activate the Business Rule.

Done! any change that happens to your change requests in ServiceNow will trigger a webhook event to the webhook URL provided by Port. Port will parse the events according to the mapping and update the catalog entities accordingly.

Let's Test It

This section includes a sample webhook event sent from ServiceNow when a change request is created or updated. In addition, it includes the entity created from the event based on the webhook configuration provided in the previous section.

Payload

Here is an example of the payload structure sent to the webhook URL when a ServiceNow change request is created or updated:

Webhook event payload
{
"body": {
"sys_id": "8a76536683f5de104665c730ceaad3bd",
"number": "CHG0030040",
"state": "3",
"short_description": "Automated change request from GitLab CI/CD",
"description": "needs approval",
"sys_updated_by": "admin",
"sys_updated_on": "2024-11-14 10:57:08",
"approval": "approved",
"priority": "2",
"phase": "requested",
"business_service": "getport-labs/awesome-projec",
"phase_state": "open",
"category": "Network",
"tags": "r_QWB886MmmkIBRGD5",
"impact": "3",
"urgency": "3",
"risk": "3",
"assignment_group": "287ebd7da9fe198100f92cc8d1d2154e",
"opened_by": "6816f79cc0a8016401c5a33be04be441",
"sys_domain": "global"
},
"queryParams": {}
}

Mapping Result

The combination of the sample payload and the webhook configuration generates the following Port entity:

{
"identifier": "8a76536683f5de104665c730ceaad3bd",
"title": "Automated change request from GitLab CI/CD",
"blueprint": "servicenowChangeRequest",
"properties": {
"number": "CHG0030040",
"state": "open",
"approval": "approved",
"category": "Network",
"priority": "2",
"description": "needs approval",
"service": "getport-labs/awesome-projec",
"tags": "r_QWB886MmmkIBRGD5",
"createdOn": "2024-11-14 10:57:08",
"createdBy": "6816f79cc0a8016401c5a33be04be441"
},
"relations": {},
"filter": true
}