Gladly Lite
Gladly is a customer service platform.
Features
| Feature Name | Supported | Notes |
|---|---|---|
| Capture deletes | check | PUBLIC_ANSWER,TASK, TASK_COMMENT, TEAM, and TEAM_AGENT. |
| History mode | ||
| Custom data | ||
| Data blocking | check | |
| Column hashing | check | |
| Re-sync | check | |
| API configurable | check | API configuration |
| Priority-first sync | ||
| Fivetran data models | ||
| Private networking | ||
| Authorization via API | check |
Setup guide
Follow our step-by-step Gladly setup guide to connect Gladly with your destination using Fivetran connectors.
Sync overview
To capture new records, we incrementally sync the following tables and their child tables:
AGENT_AVAILABILITY_EVENTAGENT_DURATION_REPORTAGENT_STATUS_EVENTAGENT_TIMESTAMPS_REPORTCONTACT_EVENTCONTACT_EXPORT_REPORT_V_3CONTACT_TIMESTAMP_REPORTCONVERSATION_EXPORT_REPORTCUSTOMER_EVENTGLAD_APP_ANSWER_SEARCH_REPORTGLAD_APP_ANSWER_USAGE_REPORTGLAD_APP_CONTACT_POINT_REPORTHELP_CENTER_ANSWER_USAGE_REPORTPAYMENT_REQUEST_EVENTQUICK_ACTION_USAGE_REPORTTASK_EVENTTASK_EXPORT_REPORTTASK_SUMMARY_REPORTTASK_TIMESTAMPS_REPORTWORK_SESSION_REPORT
Schema information
This schema applies to all Gladly connectors.
Explore Gladly schema ERD
Sync limitations
- We do not capture the
job_file_namecolumn of theAGENTandTOPICtables. You can deselect the column while querying the data for these tables in your destination. - We utilize Gladly's Export API to extract data. This endpoint lets us retrieve data only for the past 14 days. If you want to sync historical data older than 14 days, contact the Glady support team to regenerate the files for the dates you need.