Connect Freshdesk so Coworker can see your support queues and customer conversations. Either credential works on its own: per-agent keys, a workspace admin key, or both.
What Coworker can do with Freshdesk
Read tickets, conversations, groups and companies your credentials can reach
Produce two views of support activity: one report per support group (queue motion — created, resolved, escalated, who handled what) and one per customer company (what this account raised and where it stands)
Take supported write actions in Freshdesk when a task explicitly requires it
Reports never make a ticket visible beyond the agents Freshdesk itself would show it to.
Before you start
You need your Freshdesk domain and an API key
Admins connecting for the workspace need an admin-level API key
Connect as an admin
Open Data Sources from the admin settings in Coworker and select Freshdesk.
Enter your Freshdesk domain and a workspace admin API key.
Save. This widens extraction coverage across the helpdesk.
Connect as a member
Go to the Work page and click Data Sources.
Select Freshdesk and paste your own agent API key.
Good to know
The workspace key and individual keys are pooled together, never treated as mutually exclusive. Coverage grows with each connected agent.
An API key inherits its agent's role and ticket scope. An ordinary agent's key sees only assigned or group tickets — that is expected, not an error.
The admin key widens what Coworker can extract, but it does not override Freshdesk-derived access policies.
The Freshdesk domain is part of every credential and must match.