Short answer: Drop the "Freshdesk → Create 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 |
|---|---|---|---|
Subject subject | string | Required | Subject of the ticket |
Description description | string | Required | HTML content of the ticket |
Requester Email email | string | Required | Email of the requester |
Priority priority | options | Optional | Priority of the ticket |
Status status | options | Optional | Status of the ticket |
Group group_id | dynamic-options | Optional | Group to assign the ticket to |
Assign To Agent responder_id | dynamic-options | Optional | Agent to assign the ticket to |
Type type | dynamic-options | Optional | Categorize the ticket (values configured per Freshdesk account) |
Tags tags | array | Optional | List of tags to apply to the ticket. Each tag is a separate string. |
{"subject": "e.g. Login issue","description": "{{trigger.description}}","email": "user@example.com","priority": "{{trigger.priority}}","status": "{{trigger.status}}"}
{"id": 1,"status": 2,"subject": "Login issue","group_id": null,"priority": 1,"created_at": "2024-01-01T00:00:00Z","requester_id": 123456,"responder_id": null}
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.