Short answer: Drop the "ServiceNow → Update ServiceNow Incident" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Incident Sys ID sys_id | string | Required | Incident Sys ID |
State state | options | Optional | State. Options: New, In Progress, On Hold, Resolved, Closed |
Work Notes work_notes | string | Optional | Work Notes |
Close Notes close_notes | string | Optional | Close Notes |
{"sys_id": "{{trigger.sys_id}}","state": "{{trigger.state}}","work_notes": "{{trigger.work_notes}}","close_notes": "{{trigger.close_notes}}"}
{"result": {"state": "6","number": "INC0012345","sys_id": "abc123","resolved_at": "2026-04-11 14:00:00"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.