Appearance
Freshdesk
Manage support tickets, contacts, and agents with the Freshdesk API.
| Detail | Value |
|---|---|
| Category | Support |
| Base URL | https://{domain}.freshdesk.com/api/v2 |
| Authentication | Bearer Token |
| Endpoints | 6 |
| Connector key | freshdesk |
Using Freshdesk in a workflow
- Go to Connections and click New Connection.
- Pick Freshdesk from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /tickets | List all tickets |
POST /tickets | Create a ticket |
GET /tickets/{id} | Get a ticket |
PUT /tickets/{id} | Update a ticket |
GET /contacts | List contacts |
GET /agents | List agents |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /tickets
List all tickets
| Detail | Value |
|---|---|
| Operation ID | support.listTickets |
| Method | GET |
| Path | /tickets |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
page | query | integer | No |
per_page | query | integer | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Freshdesk connection from the Connection dropdown.
- In the Operation dropdown, select
support.listTickets. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Freshdesk API reference.
POST /tickets
Create a ticket
| Detail | Value |
|---|---|
| Operation ID | support.createTicket |
| Method | POST |
| Path | /tickets |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
subject | string |
description | string |
email | string |
priority | integer |
status | integer |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Freshdesk connection from the Connection dropdown.
- In the Operation dropdown, select
support.createTicket. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Freshdesk API reference.
GET /tickets/{id}
Get a ticket
| Detail | Value |
|---|---|
| Operation ID | support.getTicket |
| Method | GET |
| Path | /tickets/{id} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
id | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Freshdesk connection from the Connection dropdown.
- In the Operation dropdown, select
support.getTicket. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Freshdesk API reference.
PUT /tickets/{id}
Update a ticket
| Detail | Value |
|---|---|
| Operation ID | support.updateTicket |
| Method | PUT |
| Path | /tickets/{id} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
id | path | string | Yes |
Request Body
| Field | Type |
|---|---|
status | integer |
priority | integer |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Freshdesk connection from the Connection dropdown.
- In the Operation dropdown, select
support.updateTicket. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Freshdesk API reference.
GET /contacts
List contacts
| Detail | Value |
|---|---|
| Operation ID | support.listContacts |
| Method | GET |
| Path | /contacts |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
page | query | integer | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Freshdesk connection from the Connection dropdown.
- In the Operation dropdown, select
support.listContacts. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Freshdesk API reference.
GET /agents
List agents
| Detail | Value |
|---|---|
| Operation ID | support.listAgents |
| Method | GET |
| Path | /agents |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Freshdesk connection from the Connection dropdown.
- In the Operation dropdown, select
support.listAgents. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Freshdesk API reference.