Short answer: Drop the "Freshdesk → Update Ticket" 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 |
|---|---|---|---|
Ticket ID ticket_id | string | Required | The numeric ID of the ticket to update |
Subject subject | string | Optional | New subject for the ticket |
Description description | string | Optional | Updated HTML description |
Priority priority | options | Optional | Priority. Options: Low, Medium, High, Urgent |
Status status | options | Optional | Status. Options: Open, Pending, Resolved, Closed |
Group group_id | dynamic-options | Optional | Group. (select from available options) |
Assign To Agent responder_id | dynamic-options | Optional | Assign To Agent. (select from available options) |
{"ticket_id": "e.g. 123","subject": "e.g. Quick update","description": "{{trigger.description}}","priority": "{{trigger.priority}}","status": "{{trigger.status}}"}
{"id": 123,"status": 4,"subject": "Updated subject","priority": 3,"updated_at": "2024-01-02T00:00:00Z"}
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.