ServiceNow
Manage ServiceNow incidents and arbitrary table records via the Table API.
About
ServiceNow ships in the w6w first-party pack. It declares 9 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.servicenow- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- Customer Support · DevOps & Infrastructure
Overview
ServiceNow runs a company’s IT service management on tables of records, and this app gives a workflow direct access to two levels of that: a dedicated set of actions for incidents — the day-to-day case of opening, reading, listing and updating them — and a generic set that reaches any other table by name.
That second, generic group is what makes this app cover far more than incidents alone: problems, change requests, configuration items, users, groups and any custom table an instance has added all go through the same create, read, list, update and delete actions, just pointed at a different table name. Fields that an instance customises for itself — categories, states, close codes — are collected as an open set of name-and-value pairs rather than a fixed dropdown, since a hard-coded list would misdescribe an instance that’s changed its own configuration.
Binary attachments and the dynamic dropdowns ServiceNow’s own interface uses to populate pickers aren’t part of this app; it takes table and field names as plain values instead, which keeps the surface simple and predictable across very differently configured instances.
Build with ServiceNow
Three routes to the same 9 actions. The Workflow tab is generated from ServiceNow's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Update Incident
incident-update Update fields on an existing incident (PATCH — only fields sent are changed).
List Table Records
table-record-get-many List records from an arbitrary table, optionally filtered with an encoded query.
Update Table Record
table-record-update Update fields on a record in an arbitrary table (PATCH — only fields sent are changed).
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying ServiceNow's real ids.
{
"manifestVersion": "2",
"name": "servicenow-example",
"steps": [
{
"id": "incident-create",
"uses": {
"app": "io.w6w.servicenow",
"action": "incident-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"shortDescription": "<shortDescription>"
}
}
]
}Here are some of the things you can do
-
Create Incident
performincident-create -
Get Incident
readincident-get -
List Incidents
searchincident-get-many -
Update Incident
performincident-update -
Create Table Record
performtable-record-create
+4 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for ServiceNow, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to ServiceNow. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "incident-create",
payload: {
shortDescription: "<value>",
// description: "<value>",
// urgency: "<value>",
// impact: "<value>",
// category: "<value>",
// subcategory: "<value>",
// assignmentGroup: "<value>",
// assignedTo: "<value>",
// callerId: "<value>",
// contactType: "<value>",
// additionalFields: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action incident-create --payload '{"shortDescription":"<value>"}'Give an AI agent ServiceNow — without giving it ServiceNow's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.servicenow#incident-create",
"input": {
"shortDescription": "<shortDescription>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's ServiceNow connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
ServiceNow's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. ServiceNow itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
ServiceNow declares its own checks, so its health is a property of the app rather than something the host guesses at.
ServiceNow platform status
API quota headroom
Instance reachable
Unauthenticated request to this connection's ServiceNow instance. A 401 passes — it proves the instance is serving; credential validity is the `auth:*` check's job.