Short answer: Drop the "ServiceNow → List ServiceNow Incidents" 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 |
|---|---|---|---|
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 |
{"state": "{{trigger.state}}","limit": "{{trigger.limit}}","query": "active=true^priority=1"}
{"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.
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.