ServiceNow

This page records how composerID publishes into ServiceNow: the vendor’s API posture, the publish target and field mapping, and the documentation each claim rests on. It is for anyone evaluating the connection or building against it. ServiceNow is the one destination where the journey can both start and finish: the Triage diagnostic runs as a Service Portal / Employee Center widget in the requester’s existing session, and composerID publishes the decision back into the same instance. Writes go through the Import Set API with a transform map that coalesces on correlation_id (the task table’s standard field for external-system identifiers) so a replayed publish updates the existing record instead of creating a duplicate. Catalog requests go through the Service Catalog API, never raw Table API inserts.

Category: ITSM / Service Management. Coverage status: Specification mapped. Vendor documentation: public developer portal.

Integration path

How composerID connects to this destination, at a glance.

Step	Detail
Authentication	OAuth 2.0 or basic auth against a dedicated integration user flagged web-service-access-only, with a scoped least-privilege role plus snc_platform_rest_api_access.
composerID publishes	Record (via Import Set): POST /api/now/import/{staging_table} → transform map
Intent ID lands on	`record` `correlation_id`, written into the destination record
Back-sync	Webhooks and polling: some lifecycle events are pushed, the rest are read on a schedule.

Vendor documentation

Table API (REST)

Import Set API (REST)

Service Catalog API (REST)

Updating records using coalesce

API posture

Aspect	Detail
Authentication	OAuth 2.0 or basic auth against a dedicated integration user flagged web-service-access-only, with a scoped least-privilege role plus snc_platform_rest_api_access. Inbound client-credentials grant requires enabling it on the instance (Washington DC and later).
Style	REST, JSON or XML (Table API, Import Set API, Service Catalog API)
Base URL	https://{instance}.service-now.com/api
Webhooks	None native. Outbound events are customer-built Business Rules calling RESTMessageV2 asynchronously: at-most-once delivery, so reconciliation polling on sys_updated_on is the correctness mechanism, not a fallback.
Events posture	Webhooks and polling
Rate limits	Per-instance inbound REST rate limits and concurrency semaphores (instance-configurable); asynchronous outbound waits are capped at 30 seconds (glide.http.outbound.max_timeout).
Objects	task (correlation_id), sc_request, sc_req_item, sn_hr_core_case, import set staging tables

Publish target and field mapping

Each object below pairs the canonical intent fields with the destination’s own fields and operations. The mapping is indicative until it is confirmed against a tenant at onboarding.

Record (via Import Set)

Idempotent create-or-update

Mapping	Detail
Canonical to destination	role_title, description, requested_for, cost_center, dates
Target	POST /api/now/import/{staging_table} → transform map
Requirement	Required
Notes	The transform map coalesces on correlation_id: a replayed publish updates the existing record, never duplicates it

Intent ID correlation

Carry the Intent ID

Mapping	Detail
Canonical to destination	intent_id, intent_version
Target	correlation_id on the target task record
Requirement	Required
Notes	Standard task-table field for external-system identifiers (string, max 100); index it in the tenant for reconciliation reads

Catalog request

Order a catalog item

Mapping	Detail
Canonical to destination	catalog_item, variables{}
Target	POST /api/sn_sc/servicecatalog/items/{sys_id}/order_now
Requirement	Tenant required
Notes	Catalog variables live in sc_item_option / sc_item_option_mtom: never insert sc_req_item rows directly via the Table API

Record read-back

Read for reconciliation

Mapping	Detail
Canonical to destination	state, assignment_group, sys_updated_on
Target	GET /api/now/table/{table}?sysparm_query=correlation_id={intent_id}
Requirement	Required
Notes	Poll-first: outbound Business Rules are at-most-once, so drift detection reads back by correlation_id

Each ServiceNow instance is a separate tenant with its own tables, ACLs and transform maps. A scoped custom table extending task changes the customer’s App Engine licensing position under ServiceNow’s Custom Table Guide: verify the entitlement (paid Store apps carry their own tables’ entitlement) before committing to a table design. ACLs fail silently on field reads: a publish can 201 while individual fields were dropped, which preflight must catch.

Next steps

How composerID connects

The five ways composerID reaches a destination, and the minimum a destination must offer.

Publishing

Plan, preflight and publish: how a decision becomes a valid record in a destination.

All destinations

Every destination composerID documents, with its category and coverage status.

⌘I

Get started

Concepts

Guides

Destinations

Upstream connectors

API reference

Endpoints

Manuscript API (Triage)

Manuscript endpoints

Resources

Integration path

Vendor documentation

Table API (REST)

Import Set API (REST)

Service Catalog API (REST)

Updating records using coalesce

API posture

Publish target and field mapping

Next steps

How composerID connects

Publishing

All destinations

​Integration path

​Vendor documentation

Table API (REST)

Import Set API (REST)

Service Catalog API (REST)

Updating records using coalesce

​API posture

​Publish target and field mapping

​Next steps

How composerID connects

Publishing

All destinations

Integration path

Vendor documentation

API posture

Publish target and field mapping

Next steps