Short answer: You can create servicenow incident in ServiceNow by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the ServiceNow Create ServiceNow Incident action to a workflow, map its 6 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Short Description short_description | string | Required | Short Description. e.g. "Unable to login to application" |
Description description | string | Optional | Description |
Urgency urgency | options | Optional | Urgency. Options: 1 - High, 2 - Medium, 3 - Low |
Impact impact | options | Optional | Impact. Options: 1 - High, 2 - Medium, 3 - Low |
Assignment Group assignment_group | string | Optional | Assignment Group |
Category category | string | Optional | Category |
{"short_description": "Unable to login to application","description": "{{trigger.description}}","urgency": "{{trigger.urgency}}","impact": "{{trigger.impact}}","assignment_group": "{{trigger.assignment_group}}"}
{"result": {"state": "1","number": "INC0012345","sys_id": "abc123","priority": "3","short_description": "Unable to login"}}
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.