Servicenow SDK

ServiceNow SDK

The ServiceNow SDK brings modern developer workflows to the Now Platform: build applications as source code, version them with git, and ship them using the tools you already know. It pairs with ServiceNow Fluent, a TypeScript-based DSL for defining application metadata in code, and supports JavaScript modules and third-party libraries alongside it.

Getting Started

New to the ServiceNow SDK and Fluent? Install the SDK, initialize a project, and build your first Fluent application by following the Getting Started guide.

Ready to bring Fluent into your team's development lifecycle? See the SDLC guide for recommended source control, environment, and release practices.

AI Skills

This repository contains agent skills for creating, editing, and deploying ServiceNow Fluent applications. Rather than guessing at Fluent syntax or platform behavior, an AI coding assistant with these skills installed will consult the SDK's own documentation and your live instance before writing code, so the changes it makes follow real Fluent conventions and match what's actually deployed. Concretely, this lets an agent:

• Orient itself in a Fluent project automatically. When it detects a now.config.json, it walks through the SDK's quickstart and fluent-language documentation first, so it understands project structure, metadata types, and conventions before editing anything.
• Look up authoritative Fluent guidance on demand. explain reads directly from the documentation shipped inside the installed @servicenow/sdk package itself, so the agent is always referencing docs that match the exact SDK version in your project rather than relying on outdated training data or docs that have drifted from your version. It can search and read topics on metadata types (Table, BusinessRule, Acl, Flow, ScriptInclude, ClientScript, UiPolicy, etc.), workflows (build, transform, deploy, auth), and conventions (naming, structure, scoping, file-layout).
• Query your live instance. Using query, it can check whether a record already exists, look up a sys_id, inspect table/column schema, or fetch choice and role/scope info — grounding generated code in your actual instance data rather than assumptions.
• Avoid unsafe changes. It knows platform-specific gotchas, such as never deleting a Table()/BusinessRule()/Record() definition from a .now.ts file without confirming with you first, since deletions may need to propagate as an upgrade-time delete via keys.ts.