ActionFreshserviceUpdated September 2026

How do I create a Freshservice ticket?

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.

Create Freshservice Ticket in Freshservice — start free All 7 Freshservice actions

Create Freshservice Ticket in Freshservice — 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
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

Sample request

{
  "subject": "e.g. Laptop not working",
  "description": "{{trigger.description}}",
  "email": "user@company.com",
  "priority": "{{trigger.priority}}",
  "status": "{{trigger.status}}"
}

Returns

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

Triggered by

Apps that pair well as the trigger for Create Freshservice Ticket.

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

Google Sheets → Freshservice

2 Google Sheets triggers

HubSpot → Freshservice

18 HubSpot triggers

FAQ

Questions about Create Freshservice Ticket.

What does the Create Freshservice Ticket action do in Freshservice?

Files a new IT ticket with subject, description, priority, requester, group. For "monitoring alert → auto-file ticket for the on-call team" or "user submitted via portal → create ticket" workflows.

What inputs does Create Freshservice Ticket require?

Required: Subject, Description, Requester Email. 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 Freshservice returns an error?

The run history shows the failed step with its input and the error message Freshservice 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 Create Freshservice Ticket support batch operations?

Run Create Freshservice Ticket 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 Freshservice's rate limits.

More actions