Skip to main content
Technical Preview

Overview

A client-mode connector for a curated ITSM / OT slice of the ServiceNow Table API and Event Management Connectors under https://YOUR_INSTANCE.service-now.com: BASE_ADDRESS is https://{instance}.service-now.com (no trailing slash; endpoints already include /api/...). Topics use itsm/servicenow/<object>/<verb>.
Catalog wording places em/inbound_event under /api/now/. Public Event Management Connectors documentation uses /api/sn_em_connector/em/inbound_event?source={sourceName} (for example genericJson). Configure a push connector / event rule on the instance before posting events.
Prefer Hub secrets for tokens and passwords. This template has not been verified against a live ServiceNow instance. Status remains blocked until an authenticated live smoke succeeds.

Basic Syntax

Events

Auth

OAuth 2.0 Bearer — default in the template:
  1. Register an OAuth application on the ServiceNow instance (System OAuth → Application Registry).
  2. Obtain an access_token.
  3. Set connector BASE_ADDRESS to https://{instance}.service-now.com.
  4. Pass access_token on the MQTT request payload so headers resolve:
    • Authorization: Bearer {value.json.access_token}
  5. Store the token in Hub secrets / GET SECRET. Never commit real credentials.
Basic (username / password):
  1. Create an integration user with roles for Table API / Event Management as needed (e.g. itil, rest_service, EM connector roles).
  2. Prefer WITH USERNAME "integration.user" and WITH PASSWORD GET SECRET "SERVICENOW_PASSWORD" on REST_API_CONFIG (remove Bearer header lines if using config Basic).

Example payloads

Create incident from alarm:
EM inbound event:
PATCH CMDB CI:
List sc_task:

Deploy notes

Last modified on October 21, 2026