Freshdesk

Bring Freshdesk support tickets into DataOS

This guide brings your Freshdesk support tickets (each customer request your team handles in Freshdesk) into DataOS.

freshdesk.com
REST API
Support & ticketing

What you need

A Freshdesk agent API key, plus your Freshdesk subdomain

Who can get it

Any Freshdesk agent (the key comes from their own profile)

Where data lands

A governed table in your DataOS lakehouse

Connection type

REST API

How the connection works

Source
Freshdesk
DataOS connector
Keeps it up to date
DataOS lakehouse
Governed data product

The connector uses your Freshdesk key to ask for tickets that were created or changed since its last visit, and adds them to the table in DataOS. It reads at a gentle pace, 40 tickets' worth of requests per minute, to stay under Freshdesk's limits.

What's next

Ready to bring this data into DataOS?

See it in a demo

Watch the data land in DataOS as a governed data product. Book a demo

Read the DataOS docs

How connectors, data products and governance fit together. dataos.info

Connect another source