Weld
Start free

Freshdesk to Apache Iceberg integration

Connect Freshdesk to Apache Iceberg and automatically sync your customer support data. Weld extracts Tickets, Contacts, Agents, and Groups from Freshdesk, loads them into Apache Iceberg, and lets you transform the data using SQL or dbt, no custom scripts required.

Start for freeView setup guide
4.8 on G2
FreshdeskSource
WeldWeld
Apache IcebergWarehouse
Weld · New sync
FreshdeskSourceFreshdeskConnected
Tables to sync
  • agent26 cols
  • ticket28 cols
  • group12 cols
  • satisfaction_rating10 cols
  • ticket_conversation24 cols
  • email_config11 cols
  • Extract
  • Load
  • Keep in sync
Apache IcebergDestinationApache IcebergReady
freshdesk schema
  • freshdesk.agentSynced
  • freshdesk.ticketSyncing
  • freshdesk.groupSynced
  • freshdesk.satisfaction_ratingSynced
  • freshdesk.ticket_conversationSynced
  • freshdesk.email_configSynced
Freshdesk tables
59
fields, typed
535
relationships kept
26
agent context included
MCP

Trusted by data and AI teams

  • Flatpay
  • Holafly
  • eComplete
  • Dishoom
  • Danish Endurance
  • Female Invest
  • Son of a Tailor
  • Onomondo
  • Medik8
  • Pas Normal Studios
How it works

How to set up Freshdesk to Apache Iceberg in Weld.
In the app, with the API or an agent.

Setup guideAPI guideMCP docs
Weld · New Freshdesk sync
FreshdeskNew connectionFreshdeskAuthorised
Connection namefreshdesk
AuthorizeOpens Freshdesk to grant read access
Use cases

Why sync Freshdesk to Apache Iceberg?
Ready for analysis.

Centralizing your Freshdesk data in Apache Iceberg lets you join it with other data sources for cross-platform analytics and deeper insights.

Build reliable dashboards and reports by querying Freshdesk data directly in Apache Iceberg using SQL or your preferred BI tool.

  • Support metrics and SLA tracking

    Monitor ticket volume, resolution times, and satisfaction scores from Freshdesk in Apache Iceberg. Correlate support data with product and customer data.

  • Centralized data warehouse

    Bring Freshdesk data into Apache Iceberg alongside other sources to create a single source of truth for your organization.

  • Automated reporting

    Replace manual exports and spreadsheet-based reporting with automated pipelines from Freshdesk to Apache Iceberg. Connect BI tools like Looker, Metabase, or Power BI.

Schema

What data can you sync?
Every Freshdesk table, keys intact.

Weld syncs the following data objects from Freshdesk into Apache Iceberg. The exact tables and fields depend on your Freshdesk configuration and the permissions granted during setup.

Open the schema explorer
All 59 tables
  • agent
  • ticket
  • group
  • satisfaction_rating
  • ticket_conversation
  • email_config
  • product
  • company
  • portal
  • contact
  • automation
  • business_hour
  • ticket_form
  • role
  • survey
  • survey_question
  • sla_policy_escalation_resolution
  • agent_role
  • agent_group
  • portal_ticket_form
  • satisfaction_rating_value
  • sla_policy_escalation_response
  • sla_policy_escalation_next_response
  • sla_policy_escalation_reminder_response
  • sla_policy_escalation_reminder_resolution
  • sla_policy_escalation_reminder_next_response
  • automation_type
  • automation_action
  • account
  • discussion_topic
  • and 29 more
Weld MCP server

Ask your agent.
It queries Apache Iceberg for you.

Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the Freshdesk context, finds the tables it needs and runs the query in Apache Iceberg.

Set up the MCP serverClaudeCursorChatGPTGemini
Claude CodeOpus 5
>

How many ticket rows do we have per email_config? Use our Freshdesk data in Apache Iceberg.

Reading the Freshdesk context first, so the query uses the right tables and keys.

●weld·search_available_references
⎿raw.freshdesk.ticket
raw.freshdesk.email_config
+ 57 more Freshdesk tables
●weld·get_reference_schema
⎿ticket · 28 columns
joins email_config on email_config_id
●weld·run_query
⎿select e.id, count(*) from {{raw.freshdesk.ticket}} t
join {{raw.freshdesk.email_config}} e on t.email_config_id = e.id
group by 1
submitted
●weld·get_query_status
⎿DONE
●weld·get_query_result
⎿rows returned
✓Answered from Freshdesk data in Apache Iceberg
>Ask about your Freshdesk data
Under the hood

Technical considerations.
What to expect.

Incremental syncing
Weld uses incremental syncing where supported by the Freshdesk API, loading only new and updated records to minimize data transfer and warehouse costs.
Schema handling
Weld automatically manages schema changes. If Freshdesk adds new fields, they're detected and added to the corresponding Apache Iceberg tables.
Data freshness
Sync frequency depends on your Weld plan. Most connectors support schedules from every 5 minutes up to daily intervals.
Security
All data is encrypted in transit (TLS) and at rest. Weld is SOC 2 Type II compliant and supports IP whitelisting for database connections.
Resources

Keep reading.
Guides, docs and schema.

Documentation

Freshdesk setup guide

How to connect Freshdesk to Weld, step by step.

Documentation

Apache Iceberg setup guide

How to connect Apache Iceberg to Weld, step by step.

Schema

Freshdesk schema explorer

Browse all 59 tables and 535 fields.

Connector

Freshdesk connector

Everything Weld does with Freshdesk.

FAQ

Common questions.
About Freshdesk to Apache Iceberg.

Start syncing Freshdesk to Apache Iceberg.

Set up your Freshdesk data pipeline in minutes. No credit card required. Free for 14 days.

FreshdeskSource
WeldWeld
Apache IcebergWarehouse
Start for freeTalk to us
Related

Related integrations.
More with Freshdesk and Apache Iceberg.

View all