> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/integrations/integrations-ticketing/sync-freshservice-ticket-comments-into-siit.md).

# Sync Freshservice messages

When a ticket you escalated to Freshservice gets a new reply or note, have it appear automatically on the linked Siit request.

When a Siit request is escalated to Freshservice, the two tickets are linked. With a one-time setup in Freshservice, every new comment on the Freshservice ticket is also posted to the linked Siit request in real time. Your agents keep working in Siit and still see what the Freshservice team replies, without switching tools.

You set this up with a single rule in Freshservice's Workflow Automator that notifies Siit whenever a comment is added.

### Before you start

* **The Freshservice integration connected in Siit** (`Settings → Integrations → Freshservice`).
* **Your Siit webhook details.** You need two values from Siit: a **Callback URL** and a **signature key** for the comment event. Once your Freshservice integration is connected, contact your Siit account manager to get them.

### Step 1 — Create a ticket workflow

1. In Freshservice, go to **Admin → Workflow Automator**.
2. Create a new **ticket workflow** and give it a clear name, for example *Send ticket comments to Siit*.

   <figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-c6bbfb7a04e6dd715732170cf13eb88b3062e9d1%2FCleanShot-2026-07-20-at-22-48-15-2x-png.png?alt=media" alt=""><figcaption></figcaption></figure>

### Step 2 — Add the comment trigger

1. Add an **Event** trigger.
2. Set **These events can be performed by** to **Anyone**.
3. Choose the event **Note added is of type → Any**. This fires whenever a reply or note is added to a ticket.

   <figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-44658cdec88596edc399f48459cc9985e7d0bcc6%2FCleanShot-2026-07-20-at-22-50-05-2x-png.png?alt=media" alt=""><figcaption></figcaption></figure>

### Step 3 — Add the webhook action

1. Add an **Action** after the event and select **Trigger Webhook**. Drag it onto the canvas and connect it to the event so it runs when a comment is added.
2. Configure the action:
   * **Perform these actions on:** Ticket
   * **Request type:** POST
   * **Callback URL:** paste the Callback URL Siit gave you
   * **Credentials:** Inline Credential
   * **Authentication type:** No Auth
3. Turn on **Custom headers** and add these two:

| Header    | Value                                 |
| --------- | ------------------------------------- |
| event     | comment\_create                       |
| signature | paste the signature key Siit gave you |

```
  4. Under **Encoding**, select **JSON** and **Advanced**, then set **Content** to:
```

```
{"ticket_id": "{{ticket.id_numeric}}"}
```

5. **Save and activate** the workflow. A saved-but-inactive workflow won't send anything.

<figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-01310825019f264c177545c1830597d9ad35f0f5%2FCleanShot-2026-07-20-at-22-50-50-2x-png.png?alt=media" alt=""><figcaption></figcaption></figure>

### Step 4 — Test it

1. Open a Freshservice ticket that is linked to a Siit request and add a comment.
2. Check the linked Siit request. The comment should appear on the timeline within a few moments.

### Frequently asked questions

**Comments aren't showing up in Siit.**

Confirm the workflow is **published, saved, and activated**. Editing a workflow doesn't always publish the change.

**Still nothing after activating.**

Re-check the **Callback URL** and the **signature** header against the values Siit gave you. Paste them again and watch for extra spaces or line breaks.

**It worked, then stopped.**

Make sure this workflow uses its own comment signature key, not a key from another Freshservice webhook you may have set up.

**Just connected and it isn't working yet.**

Give it a few minutes after the integration is connected, then try again. If it persists, contact your Siit account manager.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.siit.io/guides/integrations/integrations-ticketing/sync-freshservice-ticket-comments-into-siit.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.