Skip to main content

​
Prerequisites

Before continuing, you should have already completed the following for this connector:
1

Configure the Connector

Enable the connector and set up its connector profile in your project. See Managing Connectors.
https://stackone-logos.com/api/servicenow/filled/png

Connector Profile

ServiceNow - Basic Auth
https://stackone-logos.com/api/servicenow/filled/png

Connector Profile

ServiceNow - API Key
2

Link an Account

Connect an account using StackOne Hub or Auth Link.
https://stackone-logos.com/api/servicenow/filled/png

Link Account

ServiceNow - Basic Auth
https://stackone-logos.com/api/servicenow/filled/png

Link Account

ServiceNow - API Key

ServiceNow does not expose a native webhook subscription API. This connector synthesises one by installing a Business Rule (sys_script) per event you subscribe to — each rule runs after the matching row operation and POSTs a standardised JSON envelope to the StackOne Native Webhook URL via sn_ws.RESTMessageV2. When you subscribe through the StackOne dashboard, this happens automatically on account connection.

1

Select event subscriptions in the dashboard

The connector ships 18 event handlers — one per (table, operation) pair — across 6 ServiceNow tables.

  • Incident: Incident Created, Incident Updated, Incident Deleted (table incident)
  • Problem: Problem Created, Problem Updated, Problem Deleted (table problem)
  • Change Request: Change Request Created, Change Request Updated, Change Request Deleted (table change_request)
  • Knowledge Article: Knowledge Article Created, Knowledge Article Updated, Knowledge Article Deleted (table kb_knowledge)
  • User: User Created, User Updated, User Deleted (table sys_user)
  • Group: Group Created, Group Updated, Group Deleted (table sys_user_group)
2

Connect the ServiceNow account

On account connection, the connector iterates over the events you subscribed to and installs one Business Rule per event. Each rule is scoped to a single operation (Insert / Update / Delete checkbox on the When to run tab) — for example, subscribing to Incident Created and Incident Deleted installs two Business Rules on the incident table, one with only Insert enabled and one with only Delete enabled.

3

Verify delivery

Trigger a matching row change in ServiceNow (e.g. create a test incident) and confirm the event reaches your downstream consumer.

  • Optional: POST {"test": true} to the Native Webhook URL — the Active Check handler returns 200 if the receiver is reachable.
  • Confirm the Business Rules appear under System Definition > Business Rules with names of the form StackOne Webhook - <event> (e.g. StackOne Webhook - incident_created).
4

Unsubscribe

Removing an event subscription in the dashboard deletes the corresponding Business Rule from your instance. Disconnecting the account removes all StackOne-installed Business Rules.

​
Install via the Create Webhook action (advanced)

For one-off subscriptions outside the dashboard event-config flow, call the create_webhook action directly. It installs a single Business Rule on the table you specify. Note: only the six tables with dedicated event handlers (incident, problem, change_request, kb_knowledge, sys_user, sys_user_group) are routed to a handler — webhooks on any other table will POST envelopes that the connector drops, since there is no longer a generic fallback handler.

1

Retrieve StackOne Native Webhook URL (only if overriding)

The action uses the connector’s Native Webhook URL by default. Copy it from the connector profile in the StackOne dashboard only if you need to override endpoint_url.

2

Call Create Webhook

Invoke Create Webhook with the table name. Defaults: on_insert=true, on_update=true, on_delete=false — override as needed. Save the sys_id returned in the response: it is required to delete the subscription later.

  • table_name (required): the ServiceNow table to watch (e.g. incident).
  • endpoint_url (optional): override the destination URL. Leave blank to use the Native Webhook URL.
  • on_insert / on_update / on_delete (optional booleans): which operations should fire the webhook. Set only one to true to mimic a per-operation event subscription.
  • name (optional): human-readable name. Defaults to StackOne Webhook - <table>.
3

List or remove

Call List Webhooks to see every StackOne-managed Business Rule on the instance (identified by a [stackone-webhook] marker in the description). Call Delete Webhook with the sys_id to remove one.

​
Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.