Freshdesk
by Freshworks
Freshdesk holds tickets with SLA status, contacts and companies, agents, customer satisfaction ratings and time entries. In a Lake, support leaders can tie that history to orders, payments and product issues, and see which customers and problems consume the most agent time and which fixes would remove the most tickets.
- Category
- Support & Feedback
- Type
- Help desk
- Interface
- REST API
- Built with
- Connect Any API
- Credentials
- API key, Username and password
- Write back
- tickets, contacts and companies
02Data
What you can sync.
- Tickets
- Contacts
- Companies
- Agents
- Satisfaction ratings
- Time entries
Let an AI Mind read Freshdesk tickets with the rest of your data and answer what customers ask about most.
Need more? Name any other Freshdesk data the API returns, and the AI adds it to the connector.
03Credentials
Credentials you will need.
- An API key
- A username and password
Freshdesk uses an API key or a username and password. You add the credentials once, when the AI asks for them, and it tells you where to create them in Freshworks if you need help.
04Questions
Questions you can answer.
Once Freshdesk data is in your Lake, ask an AI Mind in plain words or build the answer in DataPrism BI.
- Which companies generate the most tickets per account, and how much agent time do they consume?
- What share of tickets breach their first response or resolution SLA, by group?
- How do satisfaction ratings differ by agent and ticket type?
- Which ticket tags grew most after the last product release?
05How it works
How it works in DataMind.
-
Pick Freshdesk.
Open Lake, pick Freshdesk in the source picker and name the connection. Connect Any API opens with a ready prompt that points the AI at the Freshdesk API docs.
-
Answer a few questions.
The AI reads the Freshdesk documentation, then asks which credentials you will use, which data to sync (for example tickets and contacts), whether you want a one-time load or a recurring sync, and which accounts or filters apply.
-
Your data lands in Lake.
It builds the connector, tests it and shows you sample rows. Then Freshdesk data loads into your Lake on your schedule, ready for the Warehouse, DataPrism BI and AI Minds.
06Write back
Write data back to Freshdesk.
Send tickets, contacts and companies from your Lake and Warehouse to Freshdesk, on a schedule or when you run it. The AI reads the Freshdesk API docs, asks you a few questions and builds the destination with you.
Write to Any API
What you can send.
- Tickets
- Contacts
- Companies
A sync can create Freshdesk records from your rows and update the ones it finds by a key you choose.
Keep Freshdesk tickets current from the Warehouse, so every reply starts from the same customer facts.
Credentials
Credentials for writes.
- A username and password
Freshdesk takes a username and password for writes. You add the credentials once, when the AI asks for them, and it tells you where to create them in Freshworks if you need help.
-
Add Freshdesk in Writeback.
Open Writeback, click Add destination, choose Write to Any API and name the destination. Then tell the AI it sends to Freshdesk and point it at the Freshdesk API docs.
-
Answer a few questions.
The AI reads the Freshdesk documentation, then asks which credentials you will use, which Freshdesk objects to fill (for example tickets and contacts) and whether to create or update records.
-
Preview, test, then send.
Choose a Lake table, a Warehouse table or your own SQL, map the fields and preview the requests. Send one test record, approve the first run, and the sync keeps Freshdesk current on your schedule.
07Pairs
Works well with Freshdesk.
Sources teams join with Freshdesk in the Warehouse, each one connected the same way.