- Introduction
-
Getting Started
- Creating an Account in Hevo
- Subscribing to Hevo via AWS Marketplace
- Subscribing to Hevo via Snowflake Marketplace
- Connection Options
- Familiarizing with the UI
- Creating your First Pipeline
- Data Loss Prevention and Recovery
- Upgrading Pipeline from Standard to Edge
-
Data Ingestion
- Types of Data Synchronization
- Ingestion Modes and Query Modes for Database Sources
- Ingestion and Loading Frequency
- Data Ingestion Statuses
- Deferred Data Ingestion
- Handling of Primary Keys
- Handling of Updates
- Handling of Deletes
- Hevo-generated Metadata
- Best Practices to Avoid Reaching Source API Rate Limits
-
Edge
- Data Ingestion
- Core Concepts
-
Pipelines
- Familiarizing with the Pipelines UI
- Creating an Edge Pipeline
- Working with Edge Pipelines
- Pipeline Job History
- Pipeline Overview
- Needs Attention
- Object and Schema Management
- Activity Log
-
Sources
- Connect AI
- PostgreSQL
- Oracle
- MySQL
- SQL Server
- Troubleshooting Database Sources
- CockroachDB
- MongoDB
- SharePoint
- Salesforce Bulk API V2
- Ordergroove
- BambooHR
- Stripe
- NetSuite SuiteAnalytics
- Shopify
- Slack
- ClickUp
- Monday.com
- Pipedrive
- Workable
- Fathom
- HubSpot
- Salesforce Marketing Cloud
- Google Analytics 4
- Google Ads
- Facebook Ads
- Microsoft Ads
- LinkedIn Ads
- Xero
- Instagram Business
- Amazon Selling Partner
- TikTok Ads
- StackAdapt
- Amazon Ads
- Pinterest Organic
- Zendesk Support
- Snapchat Ads
- TikTok Organic
- Google Search Console
- Klaviyo v2
- Braintree Payments
- Facebook Pages
- Tempo
- PayPal
- Auth0
- Pinterest Ads
- Apple Search Ads
- Permit.io
- Amplitude Analytics
- Customer.io
- Paddle
- Jira Cloud
- Fullstory
- GitHub
- WorkOS
- ActiveCampaign
- Campaign Monitor
- Infobip
- Mailgun Send
- Metaplane
- Notion
- Recharge
- sevdesk
- Statuspage
- Teamwork.com
- Workday RaaS
- Yotpo
- TikTok Shop Partner Center
- Linear
- Microsoft Dynamics 365 Business Central
- Checkout.com
- Pylon
- Increase
- Microsoft Teams
- Rollbar
- Toggl Track
- QuickBooks Online
- Zoho Desk
- Livestorm
- Attentive
- SendGrid
- Bitly
- Shortcut
- Buzzsprout
- Persona
- Mailjet
- Open Exchange Rates
- PagerDuty
- CircleCI
- SonarQube
- Chargebee
- Freshdesk
- Bing Webmaster Tools
- Rundeck
- Cal.com
- Mixpanel
- Matomo
- Walmart Marketplace
- Xray
- Reddit Ads
- Zoho Recruit
- Freshchat
- Zoho Books
- Marketo
- LaunchDarkly
- Outreach
- Airtable
- Attio
- Okta
- Zendesk Chat
- Bigin by Zoho CRM
- Naming Conventions for Source Data Entities
- Destinations
- Transformations
- Alerts
- Activate
- Custom Connectors
-
Data Loading
- Loading Data in a Database Destination
- Loading Data to a Data Warehouse
- Optimizing Data Loading for a Destination Warehouse
- Deduplicating Data in a Data Warehouse Destination
- Manually Triggering the Loading of Events
- Scheduling Data Load for a Destination
- Loading Events in Batches
- Data Loading Statuses
- Data Spike Alerts
- Name Sanitization
- Table and Column Name Compression
- Parsing Nested JSON Fields in Events
-
Pipelines
- Data Flow in a Pipeline
- Familiarizing with the Pipelines UI
- Working with Pipelines
- Managing Objects in Pipelines
- Pipeline Jobs
-
Transformations
-
Python Code-Based Transformations
- Supported Python Modules and Functions
-
Transformation Methods in the Event Class
- Create an Event
- Retrieve the Event Name
- Rename an Event
- Retrieve the Properties of an Event
- Modify the Properties for an Event
- Fetch the Primary Keys of an Event
- Modify the Primary Keys of an Event
- Fetch the Data Type of a Field
- Check if the Field is a String
- Check if the Field is a Number
- Check if the Field is Boolean
- Check if the Field is a Date
- Check if the Field is a Time Value
- Check if the Field is a Timestamp
-
TimeUtils
- Convert Date String to Required Format
- Convert Date to Required Format
- Convert Datetime String to Required Format
- Convert Epoch Time to a Date
- Convert Epoch Time to a Datetime
- Convert Epoch to Required Format
- Convert Epoch to a Time
- Get Time Difference
- Parse Date String to Date
- Parse Date String to Datetime Format
- Parse Date String to Time
- Utils
- Examples of Python Code-based Transformations
-
Drag and Drop Transformations
- Special Keywords
-
Transformation Blocks and Properties
- Add a Field
- Change Datetime Field Values
- Change Field Values
- Drop Events
- Drop Fields
- Find & Replace
- Flatten JSON
- Format Date to String
- Format Number to String
- Hash Fields
- If-Else
- Mask Fields
- Modify Text Casing
- Parse Date from String
- Parse JSON from String
- Parse Number from String
- Rename Events
- Rename Fields
- Round-off Decimal Fields
- Split Fields
- Examples of Drag and Drop Transformations
- Effect of Transformations on the Destination Table Structure
- Transformation Reference
- Transformation FAQs
-
Python Code-Based Transformations
-
Schema Mapper
- Using Schema Mapper
- Mapping Statuses
- Auto Mapping Event Types
- Manually Mapping Event Types
- Modifying Schema Mapping for Event Types
- Schema Mapper Actions
- Fixing Unmapped Fields
- Resolving Incompatible Schema Mappings
- Resizing String Columns in the Destination
- Changing the Data Type of a Destination Table Column
- Schema Mapper Compatibility Table
- Limits on the Number of Destination Columns
- File Log
- Troubleshooting Failed Events in a Pipeline
- Mismatch in Events Count in Source and Destination
- Audit Tables
- Activity Log
-
Pipeline FAQs
- Can multiple Sources connect to one Destination?
- What happens if I re-create a deleted Pipeline?
- Why is there a delay in my Pipeline?
- Can I change the Destination post-Pipeline creation?
- Why is my billable Events high with Delta Timestamp mode?
- Can I drop multiple Destination tables in a Pipeline at once?
- How does Run Now affect scheduled ingestion frequency?
- Will pausing some objects increase the ingestion speed?
- Can I see the historical load progress?
- Why is my Historical Load Progress still at 0%?
- Why is historical data not getting ingested?
- How do I set a field as a primary key?
- How do I ensure that records are loaded only once?
- Why can't I see my Pipelines after logging in?
- Events Usage
-
Sources
- Free Sources
-
Databases and File Systems
- Data Warehouses
-
Databases
- Connecting to a Local Database
- Amazon DocumentDB
- Amazon DynamoDB
- Elasticsearch
-
MongoDB
- Generic MongoDB
- MongoDB Atlas
- Support for Multiple Data Types for the _id Field
- Example - Merge Collections Feature
-
Troubleshooting MongoDB
-
Errors During Pipeline Creation
- Error 1001 - Incorrect credentials
- Error 1005 - Connection timeout
- Error 1006 - Invalid database hostname
- Error 1007 - SSH connection failed
- Error 1008 - Database unreachable
- Error 1011 - Insufficient access
- Error 1028 - Primary/Master host needed for OpLog
- Error 1029 - Version not supported for Change Streams
- SSL 1009 - SSL Connection Failure
- Troubleshooting MongoDB Change Streams Connection
- Troubleshooting MongoDB OpLog Connection
-
Errors During Pipeline Creation
- SQL Server
-
MySQL
- Amazon Aurora MySQL
- Amazon RDS MySQL
- Azure MySQL
- Generic MySQL
- Google Cloud MySQL
- MariaDB MySQL
-
Troubleshooting MySQL
-
Errors During Pipeline Creation
- Error 1003 - Connection to host failed
- Error 1006 - Connection to host failed
- Error 1007 - SSH connection failed
- Error 1011 - Access denied
- Error 1012 - Replication access denied
- Error 1017 - Connection to host failed
- Error 1026 - Failed to connect to database
- Error 1027 - Unsupported BinLog format
- Failed to determine binlog filename/position
- Schema 'xyz' is not tracked via bin logs
- Errors Post-Pipeline Creation
-
Errors During Pipeline Creation
- MySQL FAQs
- Oracle
-
PostgreSQL
- Amazon Aurora PostgreSQL
- Amazon RDS PostgreSQL
- Azure PostgreSQL
- Generic PostgreSQL
- Google Cloud PostgreSQL
- Heroku PostgreSQL
- Upgrading Pipelines with PostgreSQL Sources to Use the pgoutput Plugin
-
Troubleshooting PostgreSQL
-
Errors during Pipeline creation
- Error 1003 - Authentication failure
- Error 1006 - Connection settings errors
- Error 1011 - Access role issue for logical replication
- Error 1012 - Access role issue for logical replication
- Error 1014 - Database does not exist
- Error 1017 - Connection settings errors
- Error 1023 - No pg_hba.conf entry
- Error 1024 - Number of requested standby connections
- Errors Post-Pipeline Creation
-
Errors during Pipeline creation
-
PostgreSQL FAQs
- Can I track updates to existing records in PostgreSQL?
- How can I migrate a Pipeline created with one PostgreSQL Source variant to another variant?
- How can I prevent data loss when migrating or upgrading my PostgreSQL database?
- Why do FLOAT4 and FLOAT8 values in PostgreSQL show additional decimal places when loaded to BigQuery?
- Why is data not being ingested from PostgreSQL Source objects?
- Troubleshooting Database Sources
- Database Source FAQs
- File Storage
- Engineering Analytics
- Finance & Accounting Analytics
-
Marketing Analytics
- ActiveCampaign
- AdRoll
- Amazon Ads
- Apple Search Ads
- AppsFlyer
- CleverTap
- Criteo
- Drip
- Facebook Ads
- Facebook Page Insights
- Firebase Analytics
- Freshsales
- Google Ads
- Google Analytics 4
- Google Analytics 360
- Google Play Console
- Google Search Console
- HubSpot
- Instagram Business
- Klaviyo v2
- Lemlist
- LinkedIn Ads
- Mailchimp
- Mailshake
- Marketo
- Microsoft Ads
- Onfleet
- Outbrain
- Pardot
- Pinterest Ads
- Pipedrive
- Recharge
- Segment
- SendGrid Webhook
- SendGrid
- Salesforce Marketing Cloud
- Snapchat Ads
- SurveyMonkey
- Taboola
- TikTok Ads
- Twitter Ads
- Typeform
- YouTube Analytics
- Product Analytics
- Sales & Support Analytics
- Source FAQs
-
Destinations
- Familiarizing with the Destinations UI
- Cloud Storage-Based
- Databases
-
Data Warehouses
- Amazon Redshift
- Amazon Redshift Serverless
- Azure Synapse Analytics
- Databricks
-
Google BigQuery
- Clustering in BigQuery
- Partitioning in BigQuery
- Structure of Data in the Google BigQuery Data Warehouse
- Loading Data to a Google BigQuery Data Warehouse
- Near Real-time Data Loading using Streaming
- Modifying BigQuery Destinations to Use Service Account Authentication
- Troubleshooting Google BigQuery
- Google BigQuery FAQs
- Hevo Managed Google BigQuery
- Snowflake
- Troubleshooting Data Warehouse Destinations
-
Destination FAQs
- Can I change the primary key in my Destination table?
- Can I change the Destination table name after creating the Pipeline?
- How can I change or delete the Destination table prefix?
- Why does my Destination have deleted Source records?
- How do I filter deleted Events from the Destination?
- Does a data load regenerate deleted Hevo metadata columns?
- How do I filter out specific fields before loading data?
- Transform
- Alerts
- Account Management
- Activate
- Glossary
-
Releases-
2026 Releases
- Release 2.53 (August 24 – September 21, 2026)
- Release 2.52 (July 27 – August 24, 2026)
- Release 2.51 (Jun 29 – July 27 , 2026)
- Release 2.50 (Jun 01–29, 2026)
- Release 2.49 (May 04-Jun 01, 2026)
- Release 2.48 (Apr 06-May 04, 2026)
- Release 2.47 (Mar 09-Apr 06, 2026)
- Release 2.46 (Feb 09-Mar 09, 2026)
- Release 2.45 (Jan 12-Feb 09, 2026)
-
2025 Releases
- Release 2.44 (Dec 01, 2025-Jan 12, 2026)
- Release 2.43 (Nov 03-Dec 01, 2025)
- Release 2.42 (Oct 06-Nov 03, 2025)
- Release 2.41 (Sep 08-Oct 06, 2025)
- Release 2.40 (Aug 11-Sep 08, 2025)
- Release 2.39 (Jul 07-Aug 11, 2025)
- Release 2.38 (Jun 09-Jul 07, 2025)
- Release 2.37 (May 12-Jun 09, 2025)
- Release 2.36 (Apr 14-May 12, 2025)
- Release 2.35 (Mar 17-Apr 14, 2025)
- Release 2.34 (Feb 17-Mar 17, 2025)
- Release 2.33 (Jan 20-Feb 17, 2025)
-
2024 Releases
- Release 2.32 (Dec 16 2024-Jan 20, 2025)
- Release 2.31 (Nov 18-Dec 16, 2024)
- Release 2.30 (Oct 21-Nov 18, 2024)
- Release 2.29 (Sep 30-Oct 22, 2024)
- Release 2.28 (Sep 02-30, 2024)
- Release 2.27 (Aug 05-Sep 02, 2024)
- Release 2.26 (Jul 08-Aug 05, 2024)
- Release 2.25 (Jun 10-Jul 08, 2024)
- Release 2.24 (May 06-Jun 10, 2024)
- Release 2.23 (Apr 08-May 06, 2024)
- Release 2.22 (Mar 11-Apr 08, 2024)
- Release 2.21 (Feb 12-Mar 11, 2024)
- Release 2.20 (Jan 15-Feb 12, 2024)
-
2023 Releases
- Release 2.19 (Dec 04, 2023-Jan 15, 2024)
- Release Version 2.18
- Release Version 2.17
- Release Version 2.16 (with breaking changes)
- Release Version 2.15 (with breaking changes)
- Release Version 2.14
- Release Version 2.13
- Release Version 2.12
- Release Version 2.11
- Release Version 2.10
- Release Version 2.09
- Release Version 2.08
- Release Version 2.07
- Release Version 2.06
-
2022 Releases
- Release Version 2.05
- Release Version 2.04
- Release Version 2.03
- Release Version 2.02
- Release Version 2.01
- Release Version 2.00
- Release Version 1.99
- Release Version 1.98
- Release Version 1.97
- Release Version 1.96
- Release Version 1.95
- Release Version 1.93 & 1.94
- Release Version 1.92
- Release Version 1.91
- Release Version 1.90
- Release Version 1.89
- Release Version 1.88
- Release Version 1.87
- Release Version 1.86
- Release Version 1.84 & 1.85
- Release Version 1.83
- Release Version 1.82
- Release Version 1.81
- Release Version 1.80 (Jan-24-2022)
- Release Version 1.79 (Jan-03-2022)
-
2021 Releases
- Release Version 1.78 (Dec-20-2021)
- Release Version 1.77 (Dec-06-2021)
- Release Version 1.76 (Nov-22-2021)
- Release Version 1.75 (Nov-09-2021)
- Release Version 1.74 (Oct-25-2021)
- Release Version 1.73 (Oct-04-2021)
- Release Version 1.72 (Sep-20-2021)
- Release Version 1.71 (Sep-09-2021)
- Release Version 1.70 (Aug-23-2021)
- Release Version 1.69 (Aug-09-2021)
- Release Version 1.68 (Jul-26-2021)
- Release Version 1.67 (Jul-12-2021)
- Release Version 1.66 (Jun-28-2021)
- Release Version 1.65 (Jun-14-2021)
- Release Version 1.64 (Jun-01-2021)
- Release Version 1.63 (May-19-2021)
- Release Version 1.62 (May-05-2021)
- Release Version 1.61 (Apr-20-2021)
- Release Version 1.60 (Apr-06-2021)
- Release Version 1.59 (Mar-23-2021)
- Release Version 1.58 (Mar-09-2021)
- Release Version 1.57 (Feb-22-2021)
- Release Version 1.56 (Feb-09-2021)
- Release Version 1.55 (Jan-25-2021)
- Release Version 1.54 (Jan-12-2021)
-
2020 Releases
- Release Version 1.53 (Dec-22-2020)
- Release Version 1.52 (Dec-03-2020)
- Release Version 1.51 (Nov-10-2020)
- Release Version 1.50 (Oct-19-2020)
- Release Version 1.49 (Sep-28-2020)
- Release Version 1.48 (Sep-01-2020)
- Release Version 1.47 (Aug-06-2020)
- Release Version 1.46 (Jul-21-2020)
- Release Version 1.45 (Jul-02-2020)
- Release Version 1.44 (Jun-11-2020)
- Release Version 1.43 (May-15-2020)
- Release Version 1.42 (Apr-30-2020)
- Release Version 1.41 (Apr-2020)
- Release Version 1.40 (Mar-2020)
- Release Version 1.39 (Feb-2020)
- Release Version 1.38 (Jan-2020)
-
2026 Releases
- Early Access New
Freshdesk (Edge)
Freshdesk is a customer support platform from Freshworks. Support teams use it to manage tickets from multiple channels, maintain a knowledge base, and measure customer satisfaction.
Hevo uses the Freshdesk API to replicate the tickets, conversations, contacts, companies, agents, automation rules, surveys, knowledge base, and discussions of your Freshdesk account to the Destination of your choice. To ingest data, you must provide Hevo with the API key of a Freshdesk agent and the subdomain of your Freshdesk account.
Supported Features
| Feature Name | Supported |
|---|---|
| Capture deletes | Yes |
| History mode | No |
| Custom data (user-configured tables & fields) | Yes, the custom fields of tickets, contacts, and companies |
| Data blocking (skip objects and fields) | Yes |
| Resync (objects and Pipelines) | Yes |
| API configurable | Yes |
Prerequisites
-
An active Freshdesk account from which data is to be ingested.
-
The API key of a Freshdesk agent. To ingest data for all the objects, use the API key of an agent with the Account Administrator or Administrator role. Read Obtain the API Key.
Obtain the API Key
Hevo connects to your Freshdesk account using the API key of an agent. Hevo can read only the data that the agent can access, and some objects, such as Agent, Automation, Role, SLA Policy, and Ticket Field, can be read only by an administrator. If the agent cannot access an object, Hevo marks the object as inaccessible and continues to ingest data for the other objects. Hence, to ingest data for all the objects, use the API key of an agent with the Account Administrator or Administrator role.
Perform the following steps to obtain the API key:
-
Log in to your Freshdesk account as an administrator.
-
Click your profile picture in the top-right corner of the page, and then click Profile settings.

-
In the right pane, click View API Key.

-
Select the I’m not a robot check box, and complete the verification if prompted.
-
Click the copy icon next to the Freshdesk API key, and save the key securely like any other password.

Read How to find your API key for more information.
If the API key is reset, or the agent is deleted from your Freshdesk account, Hevo cannot connect to your account, and the Pipeline fails. To resume data ingestion, modify the Source configuration with a valid API key.
Configure Freshdesk as a Source in your Pipeline
Perform the following steps to configure your Freshdesk Source:
-
Click Pipelines in the Navigation Bar.
-
Click + Create Pipeline in the Pipelines List View.
-
On the Select Source Type page, select Freshdesk.
-
On the Select Destination Type page, select the type of Destination you want to use.
-
On the Select Pipeline Type page, click Edge, and then click Continue.

Note: This page appears only if both the Source and the Destination type you selected are supported in Edge. Otherwise, the Configure Source page appears.
-
On the Configure Source page, specify the following:

-
Source Name: A unique name for your Source, not exceeding 255 characters. For example, Freshdesk Source.
-
In the Connect to Freshdesk section:
-
Subdomain: The part of your Freshdesk URL before .freshdesk.com. For example, if your Freshdesk URL is https://acme.freshdesk.com, enter acme.
-
API Key: The API key that you copied from your Freshdesk account.
-
-
-
Click Test & Continue to test the connection to your Freshdesk Source. Hevo uses the API key to read the details of the agent to whom the key belongs. Once the test is successful, you can proceed to set up your Destination.
Data Replication
Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline.
The first run of the Pipeline ingests all the data of the selected objects. In the subsequent runs, as per the sync frequency, Hevo ingests data as follows:
| Ingestion | Objects |
|---|---|
| New and updated records, based on the time each record was last updated | Contact |
| All the records, in each run | All other objects |
Hevo ingests all the tickets of your Freshdesk account, however old, including the deleted tickets and the tickets marked as spam. In the first run, Hevo ingests the conversations of all the tickets. In the subsequent runs, Hevo ingests the conversations of only the tickets updated since the previous run. Hevo reads the conversations of each ticket with a separate API request.
You can resync any object.
Freshdesk limits the number of API requests that your account can make in a minute, based on your Freshdesk plan. Trial accounts can make 50 requests per minute. The limit applies to your whole account, so the requests made by other apps that use the Freshdesk API also count toward it. If the limit is exceeded, Hevo waits and retries the request. Read Rate Limit.
Note: You can create a Pipeline with this Source only using the Merge load mode. The Append mode is not supported for this Source.
Schema and Primary Keys
Hevo uses the following schema to upload the records in the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.
Data Model
The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:
| Object | Description |
|---|---|
| Advanced Survey | Contains the customer satisfaction (CSAT) surveys created with the new survey builder, including the title, language, and state of each survey. |
| Advanced Survey Answer | Contains the answers given to each question in a response to an advanced survey. |
| Advanced Survey Question | Contains the questions in each advanced survey, including the question text, type, and display settings. This object has a child object, Advanced Survey Question Rating, which contains the rating options of each question, with their value and label. |
| Advanced Survey Response | Contains the responses to each advanced survey, including the ticket, contact, agent, and group that each response relates to. |
| Agent | Contains the agents of your helpdesk, including their availability, type, ticket scope, and signature. |
| Agent Group | Contains the groups that each agent belongs to. |
| Agent Role | Contains the roles assigned to each agent. |
| Automation | Contains the automation rules of your helpdesk, including the rule type, status, position, and the number of tickets affected. |
| Automation Action | Contains the actions that each automation rule performs, such as sending an email, adding a note, or calling a webhook. |
| Automation Condition | Contains the conditions that decide when each automation rule runs. |
| Automation Event | Contains the events that trigger each automation rule, such as a change in a ticket property. |
| Automation Performer Member | Contains the agents set as performers of each automation rule. |
| Business Hour | Contains the business hours of your helpdesk, including the time zone and the working hours of each day. |
| Company | Contains the companies that your contacts belong to, including the description, notes, industry, account tier, and renewal date. Each custom field of your companies is stored in a separate column, named custom_<field name>. |
| Company Domain | Contains the email domains of each company. |
| Contact | Contains your customers, including their name, email address, phone number, company, language, and time zone, and whether each contact is blocked or deleted. Each custom field of your contacts is stored in a separate column, named custom_<field name>. |
| Conversation | Contains the replies and notes on each ticket, including the body, sender, source, and whether the entry is private or incoming. |
| Conversation Attachment | Contains the files attached to each conversation, including the name, size, and content type. |
| Conversation BCC Email | Contains the email addresses in the BCC field of each conversation. |
| Conversation CC Email | Contains the email addresses in the CC field of each conversation. |
| Conversation To Email | Contains the email addresses that each conversation was sent to. |
| Discussion Category | Contains the categories of the discussion forums in your support portal. |
| Discussion Comment | Contains the comments posted on each discussion topic. |
| Discussion Forum | Contains the forums in each discussion category, including the forum type, visibility, and the number of topics and posts. |
| Discussion Topic | Contains the topics in each discussion forum, including the title, hits, votes, and reply details. |
| Email Config | Contains the support email addresses of your helpdesk, including the reply email address and the group and product that each address is linked to. |
| Group | Contains the agent groups of your helpdesk, including the business hours and automatic ticket assignment settings of each group. |
| Priority Lookup | Contains the ticket priorities of your helpdesk, with the ID and name of each priority. |
| Product | Contains the products configured in your helpdesk. |
| Role | Contains the agent roles of your helpdesk. |
| Satisfaction Rating | Contains the satisfaction ratings that your customers gave, including the feedback and the ticket, agent, and group that each rating relates to. |
| Satisfaction Rating Value | Contains the rating given to each survey question in a satisfaction rating. |
| SLA Policy | Contains the service level agreement (SLA) policies of your helpdesk, including the status and position of each policy. This object has the following child objects: - SLA Policy Applicable To: The companies, groups, sources, products, and ticket types that each policy applies to. - SLA Policy Target: The response, next response, and resolution targets of each policy, for each ticket priority. - SLA Policy Escalation Response, SLA Policy Escalation Next Response, and SLA Policy Escalation Resolution: The agents to whom a ticket is escalated when the target is missed, with the escalation time. - SLA Policy Escalation Reminder Response, SLA Policy Escalation Reminder Next Response, and SLA Policy Escalation Reminder Resolution: The agents who are reminded before the target is due, with the reminder time. |
| Solution Article | Contains the articles of your knowledge base, including the title, status, tags, and feedback counts of each article. |
| Solution Category | Contains the categories of your knowledge base, in each language. |
| Solution Folder | Contains the folders in each knowledge base category, including the visibility and the number of articles. |
| Source Lookup | Contains the ticket sources (channels) of your helpdesk, with the ID and name of each source. |
| Status Lookup | Contains the ticket statuses of your helpdesk, including the custom statuses, with the labels shown to agents and customers. |
| Survey | Contains the classic customer satisfaction surveys of your helpdesk. |
| Survey Question | Contains the questions in each classic survey, including the label and the accepted ratings. |
| Ticket Field | Contains the ticket fields of your helpdesk, including the default and custom fields, their type, and their visibility settings for agents and customers. |
| Ticket History | Contains the tickets of your helpdesk with their details, including the subject, status, priority, source, requester, assigned agent and group, due dates, and whether each ticket is deleted or marked as spam. Each custom field of your tickets is stored in a separate column, named custom_<field name>. This object has the following child objects: - Ticket CC Email, Ticket Forward Email, Ticket Reply CC Email, and Ticket To Email: The email addresses in the CC, forward, reply CC, and To fields of each ticket. - Ticket Tag: The tags of each ticket. |
| Time Entries | Contains the time that agents logged against each ticket, including the time spent and whether it is billable. |
Additional Information
Read the detailed Hevo documentation for the following related topics:
Handling of Deletes
Hevo captures the deletes of the Freshdesk objects as follows:
| Deletes Captured | Objects |
|---|---|
| In each run, by comparing the data | All objects, except Contact. Hevo ingests all the records of these objects in each run, and marks the records that are no longer returned by Freshdesk as deleted by setting the value of the metadata column __hevo__marked_deleted to True. For example, a company that you delete in Freshdesk is marked as deleted in the next run. |
| Through the source data |
Contact and Ticket History. Hevo also ingests the contacts and tickets that are deleted in Freshdesk, and the value of the deleted column of these records is set to True. A contact that you permanently delete in Freshdesk is no longer returned by Freshdesk and remains in the Destination. |
Source Considerations
-
If the agent whose API key you use does not have access to an object, for example, because the agent’s role or your Freshdesk plan does not include it, Hevo marks the object as inaccessible and continues to ingest data for the other objects.
-
Hevo ingests all the tickets in each run, with 100 tickets per API request, and reads the conversations of each updated ticket with a separate API request. As a result, the number of API requests in each run increases with the number of tickets.
-
Hevo creates a table in the Destination only for the objects that have data. For example, if you do not use the Freshdesk forums, the Discussion Category, Discussion Forum, Discussion Topic, and Discussion Comment tables are not created.
Limitations
- Hevo supports only the Freshdesk domains, such as acme.freshdesk.com, and not custom domains.
Revision History
Refer to the following table for the list of key updates made to this page:
| Date | Release | Description of Change |
|---|---|---|
| Nov-05-2026 | 2.54 | New document. |