# Freshdesk

{% hint style="info" %}
Available on the STARTER plan and above.
{% endhint %}

Freshdesk is a popular ticketing system that allows users to create and manage tickets.&#x20;

Using this integration, you will be able to;&#x20;

* Create tickets&#x20;
* Get ticket status

## Connecting your Freshdesk account

There are two ways through which you can connect your Freshdesk account with WotNot;

* **Through App Market:** Goto App Market > Freshdesk > Add Account&#x20;
* **Using the 'Freshdesk' action block:** On the action block, click on 'Add Account'&#x20;

Fields required to connect a Freshdesk account:

* **Name:** A name you would like to give for this Freshdesk account.
* **Helpdesk URL**: Subdomain URL of your Freshdesk account like, [https://yourdomain.freshdesk.com](https://yourdomain.freshdesk.com/)
* **API key**: API key of your Freshdesk account. [You can find it here](https://support.freshdesk.com/en/support/solutions/articles/215517-how-to-find-your-api-key)

<figure><img src="https://360969599-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsrMxU8nO3RjusUiYuXBB%2Fuploads%2FyntpH8JJqL2ub8BEV3ch%2FCleanShot%202025-03-12%20at%2012.19.58.png?alt=media&#x26;token=e941ba50-1fcf-4224-b6ca-2c0f376920e0" alt=""><figcaption></figcaption></figure>

## Create tickets

To create a ticket using the Fresdesk action block, follow these steps:

1. Connect/Choose the freshdesk account
2. Choose "Create ticket" as action
3. Map the Freshdesk fields with the variables
4. Save the ticket ID into a variable (Used to acknowledge the user that their ticket is created)

<figure><img src="https://360969599-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsrMxU8nO3RjusUiYuXBB%2Fuploads%2FcBLMlXJnJkjyreNJKcLG%2FCleanShot%202025-03-12%20at%2012.12.28.png?alt=media&#x26;token=896ef2b1-fe33-4dde-b368-321890823eb8" alt=""><figcaption></figcaption></figure>

**Mandatory fields to create a ticket: Subject & Email**

{% hint style="info" %}
The system auto-populates fields from 'Freshdesk fields'. If you do not see your field, refresh the page and try again.
{% endhint %}

## Get ticket status:&#x20;

To fetch the ticket status using the Freshdesk integration, follow these steps:&#x20;

1. Connect/Choose the freshdesk account
2. Choose "Get ticket status" as action
3. Choose the variable containing the ticket number (Before this action block executes, make sure you collect and store the ticket number in a variable)
4. Map the freshdesk fields you want to store into variables&#x20;

<figure><img src="https://360969599-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsrMxU8nO3RjusUiYuXBB%2Fuploads%2FwqX9WrykQs9uxVfUWAd5%2FCleanShot%202025-03-12%20at%2012.17.12.png?alt=media&#x26;token=c1d0603a-3714-49cb-b555-a6fd6e373710" alt=""><figcaption></figcaption></figure>

Freshdesk sends the following list of fields as response when trying to fetching the status of a ticket.

```markup
// Fields received from Freshdesk when fetching ticket status
cc_emails/fwd_emails/reply_cc_emails/ticket_cc_emails: ["test@wotnot.io"]
email_config_id
group_id
priority: "Urgent"
requester_id: 84005322544, // visitor's unique Freshdesk ID
responder_id: null, // Freshdesk agent's ID
source: "Portal"
company_id
status: "Open"
subject: "Need support to fix this..."
product_id
id
type: "Question"
due_by/fr_due_by
description_text: "Some details on the issue .."
created_at: "2022-02-10T07:12:39Z"
updated_at: "2022-02-10T07:12:39Z"
tags
```

After saving the required fields into a variable, you can use them in a 'Send Message' block to show the user the ticket's status like:

```
Ticket status of #ID# is #STATUS#

Please wait to hear back from us.
```

## Next steps&#x20;

For each Freshdesk action block, you will notice two ports coming out:

**SUCCESS** — when the Freshdesk API gives a successful, the chat flow will proceed here.

**FAILURE** — when the Freshdesk API does not give a response, the chat flow will proceed here.

You can view the logs of each Freshdesk execution from the App market > Freshdesk > Logs
