Connecting ServiceNow

What you need

1. Your instance name (the subdomain — acme for acme.service-now.com)
2. The table to watch — incident is the common case, but plenty of teams use sn_si_incident or a custom u_ table; there's no default, so pick the one your process actually uses
3. A local integration account (username & password) or an OAuth/API-key bearer token
4. Optionally, the field that carries your trigger label — defaults to category

No native webhook UI

Unlike Jira, ServiceNow has no built-in outbound-webhook screen. Configure a Business Rule + Outbound REST Message on your chosen table that POSTs {"number": current.number} to this connector's webhook URL whenever a record is inserted or updated — copy the URL from the connector's own card once it's created.

No native labels

ServiceNow has no first-class tag list the way Jira does. The trigger label is matched against one field you choose instead — category by default, since many ServiceNow processes already triage by it. If your process uses a different field, point label_field at it.

What gets written back

One entry in the record's work notes (internal-only) once the pipeline finishes — root cause, the PR link, and whether CI passed. Never written to the customer-visible comments field.

Set it up

1. Connectors → Add connector → ServiceNow
2. Enter the instance, table, and (optionally) label field and trigger label
3. Click Test connection — it confirms the credential and that the table is actually readable
4. Copy the webhook URL and wire up the Business Rule described above