Skip to content
Recued
Menu
← Back to recipes

Resolve a ServiceNow incident

by recued-core v1

Approval-gated ServiceNow incident resolution workflow for one incident. It reads the incident for context, then calls recued-core.servicenow.incident.resolve with explicit state, close code, close notes, and optional work notes. It does not delete records, revoke access, mutate CMDB records, or call arbitrary ServiceNow APIs.

How it works 4 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (4 steps)
incident_sys_id trim
Trim whitespace from setting incident sys id
incident_before ?
resolve ?
card to_summary
Format results as a summary card
Settings 7 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

state setting = 6
close code setting = Solved (Permanently)
servicenow setting =
work notes setting = Resolved by Recued governed workflow.
close notes setting =
resolved by setting =
incident sys id setting =

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Read your Servicenow connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

servicenow servicenowitsmincidentresolveservice-deskapprovalpack:servicenow

Details

4 steps 7 configurable settings recipe_id: resolve-servicenow-incident