Skip to main content
Use the @bijection/connectors/servicenow entrypoint to declare ServiceNow resources.

​
Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

​
Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

​
Configuration changes through IRE

​
submitted: Single-item IRE submission

The following example matches configuration standard.
The function references identify application policy queries. Implement those policies in your application; the references alone grant no authority.

​
Configuration: standard

Case: servicenow/configurationChanges/submitted/standard. Connection and resource configuration are declared by this exact case. Credential kind: servicenow. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Commands
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Captured or custom table

​
observed: Record observations and retained pagination

The following example matches configuration standard.

​
Configuration: standard

Case: servicenow/table/observed/standard. Connection and resource configuration are declared by this exact case. Credential kind: servicenow. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Configuration: updates

Case: servicenow/table/observed/updates. Connection and resource configuration are declared by this exact case. Credential kind: servicenow. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Commands
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Incidents

​
observed: Record observations

The following example matches configuration standard.

​
Configuration: standard

Case: servicenow/incidents/observed/standard. Connection and resource configuration are declared by this exact case. Credential kind: servicenow. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Configuration items

​
observed: Record observations

The following example matches configuration standard.

​
Configuration: standard

Case: servicenow/configurationItems/observed/standard. Connection and resource configuration are declared by this exact case. Credential kind: servicenow. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Configuration item relationships

​
observed: Record observations

The following example matches configuration standard.

​
Configuration: standard

Case: servicenow/ciRelationships/observed/standard. Connection and resource configuration are declared by this exact case. Credential kind: servicenow. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Change requests

​
observed: Record observations

The following example matches configuration standard.

​
Configuration: standard

Case: servicenow/changeRequests/observed/standard. Connection and resource configuration are declared by this exact case. Credential kind: servicenow. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Users

​
observed: Record observations

The following example matches configuration standard.

​
Configuration: standard

Case: servicenow/users/observed/standard. Connection and resource configuration are declared by this exact case. Credential kind: servicenow. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Groups

​
observed: Record observations

The following example matches configuration standard.

​
Configuration: standard

Case: servicenow/groups/observed/standard. Connection and resource configuration are declared by this exact case. Credential kind: servicenow. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Provider guidance

The resource family provides incidents, selected tables and CI classes, CI relationships, change requests, users and groups. table.observed({ table, schema, access, discovery?, updates?, create?, workNotes?, webhooks? }) is the shared implementation. Named resources select their fixed table and accept the same schema and policy options. Generated source.metadata factories select fields from captured instance dictionaries instead of repeating validators. Bind { baseUrl: "https://your-instance.service-now.com" } with a private servicenow credential. API requests use the explicit v1 Table API. Account installation queries the provider’s authenticated current principal; no record or hostname is substituted for an asserted reset epoch. A known clone or restore requires explicit source rebaselining. servicenow.account() provides the same principal lookup for native account enrollment, including client credentials. Records are observations with no conditional version, population coverage, deletion inference or complete history. Acquisition follows the retained Link header and reconstructs the fixed table request with its bounded offset. A short or empty ACL-filtered page with a next relation continues. Overlapping timestamp-window discovery, periodic full rediscovery and the independent known-record verification sweep repair current state. A timestamp is a discovery optimization; it never decides whether returned content changed. Records with omitted selected fields refuse; unreadable point reads remain unresolved. Every selected reference is its raw sys_id. Nullable empty values, booleans and exact text decimals are decoded under the selected schema. Reads and commands share native credential custody, current authority, finite work budgets and Retry-After backoff. API access by the integration principal does not grant Bijection application users access. Install the application’s read policy and command governing rules. Permission loss is not a deletion, and retained historical data needs its own authorized disclosure policy. Updates select exact non-system text attributes. Creates select their argument fields and retain the returned sys_id. Work notes are a separate journal command. All three use single-attempt, unconditional delivery. A possible send with a lost answer stays unknown; a later matching record does not attribute the request. Confirmed writes do not patch source tables. Subsequent acquisition publishes the observed record. Local checks cannot fence concurrent ServiceNow writers. Resolver, close and approval workflows require an explicitly authored tenant contract; raw state labels do not generate business commands. configurationChanges.submitted({ className, fields, governingRule }) sends one CI item through IRE. Binding additionally supplies dataSource. The class and exact text attributes are declared in code; the request cannot select an arbitrary class. Native calls retain the provider receipt. A partial/error response or lost reply stays unknown, and a successful delivery does not assert that every proposed attribute won ServiceNow’s reconciliation rules. CI acquisition remains authoritative for published state. With webhooks: true, configure the existing native listener with a separate signing credential. It expects an HMAC-SHA256 Base64 digest in x-bijection-signature, a stable deliveryId and the record’s sys_id. The operator can install refresh_hint.js in ServiceNow and invoke it from existing delivery automation. Its key argument is Base64-encoded, as required by GlideCertificateEncryption.generateMac. Retain the same delivery identity on retry. The helper sends once and logs neither body nor credentials. The signature establishes a refresh hint, not an authoritative event or a complete change feed. Periodic reconciliation remains active. Metadata capture reads selected sys_db_object, sys_dictionary, sys_dictionary_override and sys_choice records under the capture credential. It resolves bounded inheritance, checks complete selected requirements at push, and retains private response digests. Metadata visibility is not a proof of record visibility or permission to write. Journals and unsupported field types remain inspectable but cannot be selected as scalar columns. Choice codes remain open strings, including integer-backed choices; locale labels are captured separately. Empty text is preserved. Missing selected fields refuse. Nullable empty dates, numbers and references use explicit absence normalization. Final full pages require terminal count or Link evidence and do not establish population coverage. Continuations preserve instance, table, query, projection and page-size confinement. Scheduled discovery defaults to every five minutes. The first pass reads the whole table. Later passes use a frozen half-open UTC sys_updated_on window, ordered by sys_updated_on, then sys_id. The defaults are:
Raw and named resources accept discovery; captured metadata factories accept it alongside sync: { every }. The host freezes bounds at admission, retains page traversal separately, and advances its source-owned completed watermark only in the final successful publication transaction. Retries and restarts keep the original window and provider continuation. Failed, cancelled or incomplete walks cannot advance it. Credential, connection or implementation replacement requires a fresh full baseline. No connector-owned scheduler or state is used. The lower bound includes the overlap before the last completed upper bound; the upper bound excludes the host’s settling delay and rounds down to a whole second. UTC GlideDateTime construction avoids dependence on the principal’s session timezone. Overlap is 1..86400 seconds, settling delay 0..3600 seconds, and full rediscovery is mandatory every minute to thirty days. Full passes have no timestamp predicate, including the initial baseline, so empty, old or suppressed timestamps do not hide records forever. Their deadline is measured from the last successful full pass’s start and cannot be postponed by incremental passes or hints. Known-key verification still runs independently every 24 hours. Neither a window nor a full traversal establishes a provider snapshot, deletion, version, complete membership or complete change history. Provider/host clock skew beyond the configured overlap, ACL filtering and moving records may omit rows; periodic full rediscovery and point verification remain necessary. Provider documentation: Package fixtures and native contract cases establish testability. Hosted ServiceNow behavior, workload throughput, instance clones, tenant business rules and provider-side script execution require explicitly requested qualification; no live support is asserted by these declarations.

​
Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

​
Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.