Short answer: You can create freshservice ticket in Freshservice by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Freshservice Create Freshservice Ticket action to a workflow, map its 9 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 |
|---|---|---|---|
Subject subject | string | Required | Subject. Example: Laptop not working |
Description description | string | Required | HTML content describing the issue |
Requester Email email | string | Required | Email of the person raising the ticket |
Priority priority | options | Optional | Priority. Options: Low, Medium, High, Urgent |
Status status | options | Optional | Status. Options: Open, Pending, Resolved, Closed |
Source source | options | Optional | How the ticket was created |
Category category | string | Optional | Ticket category (e.g. Hardware, Software, Network) |
Sub-Category sub_category | string | Optional | Ticket sub-category |
Type type | options | Optional | Type of service request |
{"subject": "e.g. Laptop not working","description": "{{trigger.description}}","email": "user@company.com","priority": "{{trigger.priority}}","status": "{{trigger.status}}"}
{"ticket": {"id": 1,"type": "Incident","source": 2,"status": 2,"subject": "Laptop not working","priority": 1,"requester_id": 123}}
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.