servicenow-api

Build scoped ServiceNow applications as metadata-as-code — the scope/`x_` prefix/now.config.json anatomy, how Fluent artifacts assemble into a whole app (table + business rule + ACL + menu + catalog), and how that reconciles with App Engine Studio / Application Studio. Use when the agent must design a scoped app's structure, map an App Engine Studio artifact to its Fluent API and sample, assemble a multi-artifact app, or package/publish a scoped app. Do NOT use for the now-sdk build/deploy/ATF lifecycle mechanics (use servicenow-sdk-lifecycle), for authoring Flow Designer flows/subflows (use servicenow-workflow-studio), for the raw bundled Fluent samples (use servicenow-sdk-docs), or for ad-hoc record CRUD against a live instance (use servicenow-table-api).

ITSM change-management operations on the ServiceNow Change API via the servicenow-api MCP server — the full change-request lifecycle: query changes, tasks, schedules, CIs, models and standard-change templates; create/update changes and change-tasks; run risk calculation and conflict checks; approve; and delete. Use when the agent must open a normal/standard change, drive it through CAB (conflict check → approve), or inspect change schedules and impacted services. Do NOT use for incidents (servicenow-incident-management), CMDB CI data (servicenow-cmdb), or generic table CRUD (servicenow-table-api); prefer those.

ServiceNow release-engineering surface — CI/CD app install/scan/rollback, DevOps change-control & artifact registration, update-set create/preview/commit/back-out, source-control apply/import, plugin activate/rollback, and ATF test-suite runs via the servicenow-api MCP server. Use when the agent must deploy or roll back a scoped app, publish/install from an app repo, run a code/instance scan, move changes with update sets, pull remote source-control changes, activate a plugin, or execute an Automated Test Framework suite. This is where the dev-tooling skill servicenow-sdk-lifecycle defers for remote deploy/publish/test. Do NOT use for generic record CRUD (servicenow-table-api), data ingest/attachments/batch (servicenow-import-attachment-batch), or flow rendering & email (servicenow-platform-utilities).

ITOM CMDB operations on the ServiceNow CMDB + CI Lifecycle Management APIs via the servicenow-api MCP server — query configuration items by class, read a CI with its attributes and relations, create/update/patch CI instances, manage CI relationships, and drive the CI lifecycle (status, actions, leases, operators). Use when the agent must inspect or maintain the CMDB graph or govern a CI's lifecycle state. Do NOT use for incidents (servicenow-incident-management), change requests (servicenow-change-management), or generic non-CMDB table CRUD (servicenow-table-api); prefer those.

ServiceNow HR Service Delivery and Project Portfolio Management surface — fetch an employee HR profile and insert PPM cost plans and project tasks via the servicenow-api MCP server. Use when the agent must read a worker's HR profile or seed project financials (cost plans) and project task breakdowns through the dedicated HR/PPM endpoints. Do NOT use for generic table CRUD (servicenow-table-api), release/CI-CD (servicenow-cicd-devops), data ingest/attachments (servicenow-import-attachment-batch), or email/flows/metricbase (servicenow-platform-utilities).

ServiceNow data-ingest, file, and batched-REST surface — push rows through Import Sets (single & bulk), upload/get/delete record attachments, and bundle many REST calls into one batch request via the servicenow-api MCP server. Use when the agent must load external data through a transform-mapped import set, attach or fetch a file on a record, or minimize round-trips by batching multiple operations. Do NOT use for direct table CRUD without a transform map (servicenow-table-api), release/CI-CD or update-set promotion (servicenow-cicd-devops), or HR/PPM inserts (servicenow-hr-ppm).

ITSM incident operations on the ServiceNow Incident API via the servicenow-api MCP server — list, read, and create incident records with the domain-typed tool (not raw table calls). Use when the agent must triage active incidents, fetch one incident by sys_id, or open a new incident with fields like short_description, urgency, impact, and caller_id. Do NOT use for generic record CRUD on arbitrary tables (use servicenow-table-api), change requests (servicenow-change-management), CMDB CIs (servicenow-cmdb), or knowledge articles (servicenow-knowledge); prefer those.

ServiceNow Integrated Risk Management / GRC — the ServiceNow equivalent of RSA Archer (GRC) and OneTrust (privacy). Covers Risk Management, Policy & Compliance, Audit Management, Vendor / Third-Party Risk (TPRM), and Privacy Management. Use when the agent must list open risks, roll up compliance by control state, list open audit findings, work the vendor-risk assessment queue, or handle privacy data-subject / processing-activity records. IRM/GRC has no dedicated REST family, so it is driven table-first via servicenow_table_api / servicenow_aggregate / servicenow_custom_api against scoped sn_risk_* / sn_compliance_* / sn_audit_* / sn_vdr_* tables that vary by instance and plugin version. Do NOT use for generic table CRUD (use servicenow-table-api), security incidents/vulnerabilities (servicenow-secops), or the technology portfolio (servicenow-trm); prefer those.

Read access to the ServiceNow Knowledge Management (KSM) API via the servicenow-api MCP server — search/list knowledge articles, fetch a single article, pull article attachments, and get featured or most-viewed articles. Use when the agent must find or retrieve published knowledge-base content to answer a question, cite a KB article, or surface self-service documentation. Do NOT use for generic table CRUD (servicenow-table-api), incidents (servicenow-incident-management), change (servicenow-change-management), or CMDB (servicenow-cmdb); this skill is read-only KB retrieval.

ServiceNow PRODUCT documentation (concepts, not code) for the Now Platform build/automation and security/risk suites the fleet unifies: Flow Designer / Workflow Studio (no-code automation), App Engine Studio / Application Studio (low-code app building), Integrated Risk Management (IRM/GRC — risk, policy & compliance, audit, vendor/TPRM, privacy), and Security Operations (SecOps — Security Incident Response, Vulnerability Response, Threat Intelligence). Use when the agent needs to understand what these products are, their core concepts, component/table vocabulary, and how they fit together on the Now Platform. Read reference/flow-designer.md, app-engine-studio.md, irm-grc.md, or secops.md, and OVERVIEW.md first for the cross-cutting map. Do NOT use for ServiceNow SDK / Fluent (now-sdk) TypeScript syntax or the metadata-as-code toolchain — use servicenow-sdk-docs for code. Do NOT use for Table API CRUD (servicenow-table-api) or execution-oriented IRM/SecOps MCP table skills.

ServiceNow cross-domain platform helpers — send notification email, render deployed Flow Designer flows to Mermaid and read flow metadata, fetch data-classification and application metadata, list activity subscriptions, and push MetricBase time-series via the servicenow-api MCP server. Use when the agent needs a grab-bag platform utility: email a user, visualize or introspect a live flow, look up an app or its data classification, or write a metric point. Do NOT use for table CRUD (servicenow-table-api), release/CI-CD or update sets (servicenow-cicd-devops), data ingest/attachments/batch (servicenow-import-attachment-batch), or HR/PPM (servicenow-hr-ppm).

Automation skill to generate or update the `servicenow-sdk-docs` documentation skill by fetching and processing the ServiceNow SDK and Examples repositories. It combines READMEs, extracts code samples, harvests the SDK CLI/auth docs, and creates a self-contained, portable documentation skill.

A comprehensive, self-contained collection of ServiceNow SDK (Fluent API) examples and core documentation. Use this when the agent needs to reference how to use the ServiceNow SDK for various components like Tables, REST APIs, UI Actions, Script Includes, etc. All source code is bundled within the skill for portability.

The procedural spine for building ServiceNow applications as code with the `now-sdk` (`@servicenow/sdk`) CLI — the ordered lifecycle from init → auth → author Fluent → dependencies → build/transform → deploy/install → source-control → ATF, plus a "CLI vs MCP tool" decision table. Use when the agent must scaffold, authenticate, build, transform, deploy, install, version, source-control, or ATF-test a scoped app locally, or orchestrate the same steps against a remote instance via the servicenow-api MCP server. Do NOT use for authoring Flow Designer flows/subflows/actions (use servicenow-workflow-studio), for scoped-app metadata anatomy and App Engine Studio reconciliation (use servicenow-app-engine), for the bundled Fluent code samples (use servicenow-sdk-docs), or for plain table CRUD against a live instance (use servicenow-table-api).

ServiceNow Security Operations (SecOps) — Security Incident Response (SIR), Vulnerability Response (VR), and Threat Intelligence (TI). Use when the agent must triage security incidents by priority, list vulnerable items by risk/state, or work threat-intel observables. SecOps areas expose only limited REST, so the reliable path is table-first via servicenow_table_api / servicenow_aggregate / servicenow_custom_api against scoped sn_si_* (SIR), sn_vul_* (VR), and sn_ti_* (TI) tables that vary by instance and plugin version. Do NOT use for regular ITSM incidents (use servicenow-incident-management), generic table CRUD (servicenow-table-api), risk/GRC (servicenow-irm-grc), or CMDB CIs (servicenow-cmdb); prefer those.

Foundational ServiceNow data access — generic Table API CRUD, Aggregate/stats roll-ups, and raw REST escape-hatch via the servicenow-api MCP server. Use when the agent must read, insert, update, patch, delete, count, or aggregate records in ANY ServiceNow table (including scoped app tables with no dedicated API), or call a REST endpoint the typed tools do not cover. Teaches encoded-query (sysparm_query) syntax, field/pagination controls, and group-by aggregation. Do NOT use for a domain that has its own skill (incidents → servicenow-incident-management, change → servicenow-change-management, CMDB → servicenow-cmdb, TRM/APM → servicenow-trm, risk/GRC → servicenow-irm-grc, security → servicenow-secops); prefer those.

ServiceNow Telecom (TSM/TSOM) TM Forum Open APIs — drives service qualification (TMF645), product inventory (TMF637), account (TMF666/629), and any other TM Forum Open API (TMF622 product ordering, TMF641 service ordering, TMF642 alarm management) exposed by Store-installed scoped telecom apps. Use when the agent must run a service qualification, list product inventory, fetch an account, or call a raw TMF endpoint. It uses the domain-typed tools servicenow_service_qualification / servicenow_product_inventory / servicenow_account, and servicenow_custom_api api_request for other TMF endpoints whose scoped-app path depends on which TMF plugins are installed (discover-first). Do NOT use for generic table CRUD (use servicenow-table-api), CMDB CIs (servicenow-cmdb), or ITSM incidents (servicenow-incident-management); prefer those.

ServiceNow Technology Reference Model / Application Portfolio Management (APM) — manage the technology & software portfolio, software-product lifecycle (Approved / Emerging / Retirement / End-of-life), technical debt, and architecture-standard compliance. Use when the agent must inventory the tech/software portfolio, roll up records by lifecycle stage, deep-dive a technology by sys_id, or set a technology's lifecycle/approval state. APM/TRM has no dedicated REST family, so it is driven table-first via servicenow_table_api / servicenow_aggregate / servicenow_custom_api against scoped tables that vary by instance and plugin version. Do NOT use for generic table CRUD (use servicenow-table-api), CMDB configuration items (servicenow-cmdb), risk/GRC (servicenow-irm-grc), or security (servicenow-secops); prefer those.

Author ServiceNow Flow Designer flows, subflows, and actions as code with the Fluent `@servicenow/sdk/automation` API (`Flow`, `Subflow`, `wfa.trigger`, `wfa.action`, `wfa.flowLogic`, `wfa.dataPill`), plus how each Fluent construct maps to the Flow Designer UI. Use when the agent must write or explain a flow, subflow, trigger, flow-logic branch/loop, data pill, or script action in code, or introspect a deployed flow's graph via the servicenow-api MCP server. Do NOT use for the build/deploy/ATF lifecycle of the app that contains the flow (use servicenow-sdk-lifecycle), for scoped-app metadata anatomy (use servicenow-app-engine), for the raw bundled flow samples (use servicenow-sdk-docs), or for record CRUD against a live instance (use servicenow-table-api).