servicenow-workflow-studio

ServiceNow Workflow Studio (Flow Designer as code)

Flow Designer is ServiceNow's low-code automation surface. The Fluent @servicenow/sdk/automation API expresses the same flows/subflows/actions as TypeScript source, so they live in a repo and ship through the SDK lifecycle. This skill is about authoring that code and mapping it back to the UI — it defers build/deploy to servicenow-sdk-lifecycle.

When to use

• Writing a Flow(...), Subflow(...), or ScriptAction(...) in Fluent.
• Choosing/configuring a trigger (record or application).
• Adding flow logic: if / elseIf / else / forEach / waitForCondition / endFlow.
• Wiring data pills between a trigger, action outputs, and downstream inputs.
• Introspecting a deployed flow's structure (mermaid graph, metadata) via MCP.

When NOT to use

• Building/deploying/testing the containing app → servicenow-sdk-lifecycle.
• Scoped-app anatomy / App Engine Studio → servicenow-app-engine.
• Reading the raw samples → servicenow-sdk-docs.
• Ad-hoc live record CRUD → servicenow-table-api.

Canonical samples (cross-reference — never copy in)

Every construct below has a worked example bundled in the sibling skill:

• Flows, subflows, triggers, flow logic, data pills: servicenow-sdk-docs → assets/samples/flow-sample/ and references/flow-sample.md.
• Script actions (sysevent_script_action): servicenow-sdk-docs → assets/samples/scriptaction-sample/ and references/scriptaction-sample.md.

Open those when you need a full, real file; the references here teach the shape and rules so you can compose new ones.

The shape of a flow

import { action, Flow, wfa, trigger } from '@servicenow/sdk/automation'

export const myFlow = Flow(
  { $id: Now.ID['my_flow'], name: 'My Flow', description: '...' },
  wfa.trigger(trigger.record.created, { $id: Now.ID['trg'] }, { table: 'incident', condition: 'active=true' }),
  (params) => {
    wfa.action(action.core.log, { $id: Now.ID['log'] }, { log_level: 'info', log_message: '...' })
    // flow logic, more actions, data pills ...
  },
)

Three positional arguments: metadata ($id/name/description), a trigger (wfa.trigger), and the body (params) => { ... }. params.trigger.* exposes trigger outputs to the body.