Freshdesk and Zendesk
Connect your helpdesk, Freshdesk or Zendesk, to bring support conversations into Productmind, where each one becomes a support case beside your customer meetings. You can import conversations by hand, and, where it is available, have every resolved ticket arrive on its own.
Key concepts
Importing by hand. You choose the conversations to bring in, in the import wizard. See Customer support.
Automated ingestion. When a ticket is resolved or closed in your helpdesk, the helpdesk sends it to Productmind, which imports it. It is controlled by one switch on the helpdesk's page. If you don't see that switch, automated ingestion is not enabled for your organization yet, even if the Freshdesk or Zendesk card on Integrations says 1 automation. Ask Productmind support to turn it on.
Ingestion filters. Rules that decide which automatically delivered conversations Productmind keeps, for example only tickets with a certain tag.
Read-only. Productmind never changes your tickets: no replies, no status changes, no tags. On Zendesk, it only creates and removes its own webhook and triggers.
Connecting your helpdesk
You can connect a helpdesk from Integrations, as below, or from the first step of the import wizard on Customer support.
To connect Freshdesk
You need an API key from your Freshdesk profile settings.
- In the sidebar, choose Integrations.
- Under Workspace integrations, choose Freshdesk.
- In Connect Freshdesk, enter:
- a Connection name, if you want one;
- your Freshdesk Domain, for example
acme.freshdesk.com; - your API Key.
- Choose Connect.
Productmind shows "Freshdesk connected successfully", and the Freshdesk card turns green.
To connect Zendesk
Zendesk connects through an OAuth client that you create in your own Zendesk account. Connect as a Zendesk admin: only an admin's connection lets Productmind set up automated ingestion for you.
- In the sidebar, choose Integrations.
- Under Workspace integrations, choose Zendesk. Connect Zendesk opens, and shows a callback URL. Choose Copy to copy it.
- In Zendesk Admin Center, add an OAuth client. Paste the callback URL into its redirect URLs exactly as shown, save it, and copy its unique identifier and secret.
- Back in Connect Zendesk, enter your Zendesk URL, for example
https://acme.zendesk.com, the Unique identifier and the Secret. - Choose Authorize, and approve access in Zendesk.
You return to Integrations, which shows "Zendesk connected successfully".
Productmind asks Zendesk for permission to read tickets, and to manage webhooks and triggers, so it can create its own delivery path. It never asks to change tickets.
The helpdesk's page at a glance
On Integrations, choose the Freshdesk or Zendesk card to open its page.
At the top are Import from Freshdesk (or Import from Zendesk) and Disconnect.
If automated ingestion is enabled for your organization, the page also has:
| Section | What it does |
|---|---|
| Automations | The one switch that turns automated ingestion on or off. |
| Set up in Freshdesk | Freshdesk only: the values and steps for the rule you build in Freshdesk. Appears while the automation is on. |
| Zendesk Ticket Events | Zendesk only: confirms that Productmind set up the delivery in your Zendesk account, or says it couldn't and offers Reconnect and Retry setup. Appears while the automation is on. |
| Automated ingestion | The ingestion filters. |
| Recent ingestion events | The last five conversations imported from this helpdesk, by hand or automatically, and what happened to each. |
Importing conversations by hand
To import conversations
- Open the helpdesk's page and choose Import from Freshdesk or Import from Zendesk. You can also start the import from the Customer support list: choose Create, then Import from Freshdesk or Import from Zendesk.
- If the helpdesk isn't connected yet, connect it in the Connect step.
- In Browse, choose which tickets to fetch, and select the conversations to import.
- Choose Next.
- In Preview, check how each conversation will be filed, and change it if you need to.
- Choose Next to start the import.
- When it finishes, choose Done.
The conversations appear under Customer support, or under Customer meetings for any you filed as a meeting. See Customer support for the whole wizard.
Whether conversations from your helpdesk are summarized by AI is a workspace setting, and it covers the ones you import by hand and the ones delivered automatically alike. See Support desk.
Setting up automated ingestion
Automated ingestion is being rolled out gradually. See the Availability section at the top of this page.
To turn on automated ingestion from Zendesk
- Open the Zendesk page.
- Under Automations, turn on the ticket automation.
Productmind creates a webhook named Productmind in your Zendesk account, and two triggers whose names start with Productmind: one fires when a ticket is solved, the other when it is closed. Productmind verifies every delivery against the signature Zendesk signs it with. Under Zendesk Ticket Events, the page confirms: "Productmind set this up in your Zendesk account". There is nothing to copy.
If the section says "Productmind couldn't set this up in your Zendesk account" instead, see The Zendesk page says Productmind couldn't set this up. There's no way to set up the delivery by hand in Zendesk: Zendesk signs every delivery with a secret only Productmind's own setup can read.
To turn it off, turn off the switch and choose Turn off. Productmind deletes the triggers it created, so Zendesk stops sending. Nothing already imported is removed, and turning it back on creates them again.
To turn on automated ingestion from Freshdesk
Freshdesk has no way for Productmind to create the rule itself, so you build it in Freshdesk. Webhook actions in Freshdesk automation rules need a Freshdesk Growth, Pro or Enterprise plan. On a lower plan, import by hand instead.
- Open the Freshdesk page.
- Under Automations, turn on the ticket automation. Set up in Freshdesk appears.
- Under Copy the webhook URL, copy the URL.
- Under Copy the secret, choose Generate secret, and copy the secret it shows.
- Under Copy the header name, copy the header name.
- In Freshdesk, go to Admin, Workflows, Automations, Ticket updates, and add a
rule:
- condition: the status changes to Resolved, and, if you want those too, Closed;
- action: Trigger webhook, request type
POST, with the URL from step 3; - content: JSON containing at least
ticket_idandticket_status; - a custom header, with the header name from step 5 and the secret from step 4.
Open your Freshdesk automations takes you to that page in Freshdesk.
When the first delivery arrives, the section shows Last delivery received with its date. Until then, it shows Waiting for the first delivery from Freshdesk.
Freshdesk does not sign its webhooks, so the secret is the only thing that proves a delivery came from your Freshdesk. Treat it like a password. If you lost it, open Manage secrets and choose Reveal secret on it. To replace it, choose Generate a new secret. To stop accepting an old one, open Manage secrets, choose Revoke secret on it, and confirm. A delivery that carries a revoked secret is rejected, so update the header in your Freshdesk rule first.
To choose which conversations get through
- Open the helpdesk's page, and go to Automated ingestion.
- Fill in the filters you need. Every field is optional, and leaving them all empty accepts every conversation the automation delivers.
- Choose Save filters.
The filters apply only to conversations that arrive automatically. A conversation you import by hand is never filtered out.
| Filter | Keeps |
|---|---|
| Statuses | resolved, closed, or both (empty). Only these two ever arrive. resolved alone turns away tickets that were closed without being resolved, such as spam and duplicates. For Zendesk, a Solved ticket counts as resolved. |
| Groups | Tickets in these helpdesk groups. Enter group IDs, separated by commas. |
| Tags and Tag match | Tickets with Any of these tags or All of these tags. Separate tags with commas. |
| Strategic accounts only | Conversations whose contact belongs to a strategic account. |
| Include unmatched requesters | Conversations whose requester matched no contact. On by default. |
| Minimum estimated ARR | Conversations from accounts with at least this estimated annual revenue. |
| Lifecycle states | Conversations from accounts in one lifecycle state, such as Customer or At risk: the account's Stage on Contacts. |
File conversations as chooses whether automatically delivered conversations become a Support case (the default) or a Customer meeting. It is also the starting type for each conversation in the import wizard, which you can change conversation by conversation.
The filters apply to this helpdesk only. Another connected helpdesk has its own.
How helpdesk integrations behave
What is imported.
- The ticket's description and its public replies, each attributed to the agent or the customer.
- Attachments, onto the conversation: images and documents up to 10 MB each, at most five per conversation and at most 50 files per import. Videos are never imported. A file that can't be fetched never stops the import.
- A link to the contact whose email matches the requester, if there is one.
What is never imported. Internal notes, and their attachments.
Each ticket is imported once. Importing a ticket again, by hand or automatically, updates the conversation it created instead of adding a second one. A ticket that is resolved and later closed arrives twice, and the second delivery updates the same conversation. If you reclassified a conversation by hand, later updates keep your choice.
Only the same account updates a conversation. Every Freshdesk or Zendesk account numbers its tickets from 1, so a ticket with the same number from another account is not imported, and Recent ingestion events says why. If you connect two accounts of the same helpdesk, a ticket whose number the other account already used isn't imported. If your helpdesk's address changes, for example after renaming your Freshdesk helpdesk URL or your Zendesk subdomain, conversations imported under the old address are no longer updated: contact Productmind support to move them to the new address.
Only resolved and closed tickets are delivered. A delivery for any other status is ignored, and nothing is recorded, not even in Recent ingestion events.
Conversations that arrive automatically are summarized when Summarize imported conversations is on in Support desk, the same as the ones you import by hand. A conversation is summarized when it first arrives, and again when it arrives with new replies; a delivery with nothing new isn't summarized again. Summaries use AI credits. With the setting off, open a conversation and choose Summarize this conversation (the circular arrows) to summarize it.
Recent ingestion events lists the last five conversations imported from this helpdesk, by hand or automatically, with the outcome of each. A row without a message says Manual import or Automated.
| Outcome | Means |
|---|---|
| Created | A new conversation was imported. |
| Updated | The ticket had been imported before, and its conversation was updated. |
| Filtered out | The delivery arrived, and a filter turned it away. The message says which. |
| Error | Something went wrong. The message says what. |
Disconnecting Zendesk removes the webhook and both triggers from your Zendesk account.
Permissions
| To | You need |
|---|---|
| Open the helpdesk's page, disconnect a helpdesk, turn automated ingestion on or off, change its filters | The Owner or Admin role |
| Connect a helpdesk from Integrations | The Owner or Admin role |
| Connect a helpdesk from the import wizard on Customer support | Customer meetings & support: Create |
| Import conversations by hand | Customer meetings & support: Create |
Troubleshooting
Nothing arrives automatically
No delivery has reached Productmind, so Recent ingestion events shows no automatic ones.
- Check that the ticket automation's switch is on. While it is off, the page says Nothing is being delivered.
- For Freshdesk, check that your rule fires when the status changes to Resolved or Closed: a rule on any other status is ignored without a trace. Then check the URL, the header name and the secret in the rule.
- For Zendesk, check that the two Productmind triggers still exist and are active in Zendesk.
Recent ingestion events is full of Filtered out
Deliveries are arriving, and your filters are turning them away. Loosen the filters, or leave them empty to accept everything.
The Zendesk page says Productmind couldn't set this up
Productmind couldn't create the webhook and triggers in your Zendesk account, usually because Zendesk was connected by someone who is not a Zendesk admin. Until it's set up, nothing arrives automatically, but importing by hand still works.
- Under Zendesk Ticket Events, choose Reconnect, and sign in to Zendesk as a Zendesk admin.
- Back on the Zendesk page, choose Retry setup.
When it works, the section confirms: "Productmind set this up in your Zendesk account". If Zendesk refuses again, check that the account you connected with is a Zendesk admin.
Zendesk authorization comes back with an error
The redirect URL in your Zendesk OAuth client must match the callback URL in Connect Zendesk exactly. Also check that API access is turned on for your Zendesk account, and that the secret was pasted in full.
An attachment is missing from an imported conversation
It may be larger than 10 MB, a video, past the five-file limit for a conversation, or past the 50-file limit for one import. Freshdesk's download links expire quickly: if the import wizard was open a long time, import the ticket again. If your Zendesk account requires authentication to download attachments, Productmind can't fetch them.
An automatically delivered conversation has no summary
- Check that Summarize imported conversations is on in Support desk. It applies to every conversation that arrives from then on.
- Check that your organization has AI credits left. Without them, conversations still arrive, but aren't summarized.
To summarize one now, open the conversation and choose Summarize this conversation.