ActionServiceNowUpdated September 2026

How do I update a ServiceNow incident?

Short answer: You can update servicenow incident in ServiceNow by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the ServiceNow Update ServiceNow Incident action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Update ServiceNow Incident in ServiceNow — start free All 3 ServiceNow actions

Update ServiceNow Incident in ServiceNow — start free

Inputs

The fields this action accepts.

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

Sample request

{
  "sys_id": "{{trigger.sys_id}}",
  "state": "{{trigger.state}}",
  "work_notes": "{{trigger.work_notes}}",
  "close_notes": "{{trigger.close_notes}}"
}

Returns

{
  "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.

Triggered by

Apps that pair well as the trigger for Update ServiceNow Incident.

Any of these apps can fire this action as part of a workflow.

Google Sheets → ServiceNow

2 Google Sheets triggers

HubSpot → ServiceNow

18 HubSpot triggers

FAQ

Questions about Update ServiceNow Incident.

What does the Update ServiceNow Incident action do in ServiceNow?

Updates fields — state, assignee, work_notes (internal), comments (user-visible). For "monitoring auto-resolved → close ticket" or "AI-summarised investigation → log as work note" workflows.

What inputs does Update ServiceNow Incident require?

Required: Incident Sys ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if ServiceNow returns an error?

The run history shows the failed step with its input and the error message ServiceNow returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Update ServiceNow Incident support batch operations?

Run Update ServiceNow Incident inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within ServiceNow's rate limits.

More actions

Other ServiceNow actions.

Action

Create ServiceNow Incident

Files a new incident with short description, description, priority, urgency, impact, assignment group. The standard hook for "external monitoring detected → file ticket for IT" enterprise workflows.

Action

List ServiceNow Incidents

Paginated incidents with sysparm_query filter. For "current open critical incidents" dashboards and for compliance auditing workflows.

Update ServiceNow Incident in ServiceNow — start free