Freshdesk
First time using Freshdesk? See the Freshdesk documentation.
Introduction
The Freshdesk integration turns Conviso Platform findings into Freshdesk tickets. It covers both:
- Vulnerabilities — a ticket per vulnerability sent to Freshdesk.
- Requirements Sync — a ticket per activity of a Conviso Platform project. See Requirements Sync for the shared model.
Both run over the same connection, and each is configured on its own tab of the integration screen. You can set up one, the other, or both.
Freshdesk is the only supported tracker with no API for creating webhooks. Conviso Platform can send tickets to Freshdesk as soon as you connect, but to receive status changes back you must create an automation rule by hand in the Freshdesk admin. Until you do, synchronization works in one direction only, and nothing on either screen will say so.
Prerequisites
- A Freshdesk account, with an agent user able to create tickets.
- Administrator access to Freshdesk, to create the automation rule.
- A contact in Freshdesk to own the tickets Conviso Platform opens — see Requester.
Connect Freshdesk
- In the left menu, click Integrations.
- Open the Defect Tracking tab and click Connect on the Freshdesk card.
- Authorize the connection. Credentials are held by the authorization service and are never stored by Conviso Platform; the platform keeps only a reference to the connection.
Once connected, the integration screen shows two tabs: Vulnerabilities and Requirements.
Requester (required)
Freshdesk refuses to create a ticket with no requester, and the error it returns does not say that the configuration is incomplete. Because of this, the requester email is part of the configuration rather than something Conviso Platform derives.
Use an address that exists as a contact in your Freshdesk account — for example an automation mailbox such as automations@yourcompany.com. Every ticket Conviso Platform opens is created on behalf of that contact.
This is also what lets you scope the automation rule to the integration's tickets instead of your whole helpdesk — see Condition.
Priority is set to Medium on every ticket Conviso Platform creates through Requirements Sync. Freshdesk requires a priority on create, and a requirement has no severity to derive one from. The card mirrors planned work, not an incident.
Configure vulnerabilities
On the Vulnerabilities tab, add a configuration:
| Field | Meaning |
|---|---|
| Default configuration | Catches every asset without a configuration of its own. One per integration. |
| Assets | Which assets this configuration covers, when it is not the default. |
| Requester e-mail | The contact that owns the tickets. Required — see Requester. |
| Group | Optional. Leave empty to use the account's default queue. |
| Status Mapping | Which Freshdesk status each Conviso Platform vulnerability status corresponds to. |
Only the Identified status is required in the mapping. A vulnerability is born identified, so without that row no ticket is ever created.
Configure Requirements Sync
On the Requirements tab, click Add configuration and follow the wizard.
Step 1 — Project
Choose which Conviso Platform projects to send, and the Freshdesk fields the tickets will carry (requester and group).
Projects already synced with this integration are not listed: a project can only have one configuration per tracker.
Step 2 — Activity status mapping
Map each Conviso Platform activity status to a Freshdesk status.