Overview
A client-mode connector for a curated ITSM / OT slice of the ServiceNow Table API and Event Management Connectors underhttps://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:- Register an OAuth application on the ServiceNow instance (System OAuth → Application Registry).
- Obtain an
access_token. - Set connector
BASE_ADDRESStohttps://{instance}.service-now.com. - Pass
access_tokenon the MQTT request payload so headers resolve:Authorization: Bearer {value.json.access_token}
- Store the token in Hub secrets /
GET SECRET. Never commit real credentials.
- Create an integration user with roles for Table API / Event Management as needed (e.g.
itil,rest_service, EM connector roles). - Prefer
WITH USERNAME "integration.user"andWITH PASSWORD GET SECRET "SERVICENOW_PASSWORD"onREST_API_CONFIG(remove Bearer header lines if using config Basic).
Example payloads
Create incident from alarm:Deploy notes
- Deploy
ServiceNowRestApi.lotonly (-addRoute). Do not deployhub-metadata.lotas a connector — it exists for Hub /-listTemplates(ADD METADATA+WITH IMAGEbase64). - Hub category: REST API Connectors.
- Doc link: https://docs.coreflux.org/latest/lot-language/routes/rest-api-apps/servicenow

