Flitch

Freshdesk

Connect Freshdesk to build dashboards on tickets, contacts, companies, and agents.

Read only access to your Freshdesk help-desk data. No writes back to Freshdesk.

Freshdesk uses an API key plus your account subdomain (not OAuth). You supply both when you connect: the part before .freshdesk.com and a read-only API key from your profile.

Objects

ObjectFields
TicketsSupport tickets with status, priority, and timestamps
ContactsRequesters and customers
CompaniesCompanies your contacts belong to
AgentsHelp-desk agents in your account
GroupsAgent groups

Scopes

Freshdesk's v2 API does not use OAuth scopes. Access is governed by the permissions of the agent whose API key you use. Flitch only reads; it never creates, updates, or closes tickets.

Connect

Find your API key in Freshdesk

In Freshdesk, click your profile picture → Profile settings. Your API key is in the right sidebar. Note your subdomain too (the part before .freshdesk.com).

Open Data

In app.flitch.io, open the Data page.

Add Freshdesk

Top right, click Add, pick Freshdesk.

Enter subdomain and key

Enter your subdomain, paste the API key, then connect.

Pick objects and save

Tick the objects you want (Tickets, Contacts, Companies, Agents, Groups). Set a name. Save.

Each object becomes a dataset.

Refresh

Refresh is off by default. Every dashboard load runs a live query against Freshdesk. Enable refresh to schedule a background refresh and serve from cache between runs. See Refresh.

Disconnect

  • In Flitch: open the connection from the Data page and delete it. Key removed, cache cleared.
  • In Freshdesk: reset your API key in Profile settings to immediately cut off access.

Troubleshooting

Authentication failed. The API key was reset, or the subdomain is wrong. Confirm both and reconnect.

Wrong subdomain. The subdomain is the part before .freshdesk.com in your help-desk URL, not your email domain.

Rate limited. Freshdesk enforces a per-account request limit (plan dependent). Heavy refreshes can hit it. Enable refresh to serve from cache between scheduled runs.

On this page