ActionServiceNowUpdated September 2026
How do I list ServiceNow incidents?
Short answer: You can list servicenow incidents in ServiceNow by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the ServiceNow List ServiceNow Incidents action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 |
|---|---|---|---|
State state | options | Optional | State. Options: All, New, In Progress, Resolved, Closed |
Limit limit | number | Optional | Limit |
Encoded Query query | string | Optional | ServiceNow encoded query string |
Sample request
{"state": "{{trigger.state}}","limit": "{{trigger.limit}}","query": "active=true^priority=1"}
Returns
{"result": [{"state": "1","number": "INC0012345","sys_id": "abc123","priority": "3","opened_at": "2026-04-11 10:00:00","short_description": "Login issue"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for List ServiceNow Incidents.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about List ServiceNow Incidents.
What does the List ServiceNow Incidents action do in ServiceNow?
Paginated incidents with sysparm_query filter. For "current open critical incidents" dashboards and for compliance auditing workflows.
What inputs does List ServiceNow Incidents require?
List ServiceNow Incidents has no required inputs. Sensible defaults are applied if you leave fields blank.
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 List ServiceNow Incidents support batch operations?
Run List ServiceNow Incidents 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.
ActionUpdate ServiceNow Incident
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.