Weld
Start free

Zendesk to ClickHouse integration

Connect Zendesk to ClickHouse and automatically sync your customer support data. Weld extracts Tickets, Users, Organizations, and Groups from Zendesk, loads them into ClickHouse, and lets you transform the data using SQL or dbt, no custom scripts required.

Start for freeView setup guide
4.8 on G2
ZendeskSource
WeldWeld
ClickHouseWarehouse
Weld · New sync
ZendeskSourceZendeskConnected
Tables to sync
  • ticket48 cols
  • user48 cols
  • organization12 cols
  • group9 cols
  • ticket_form15 cols
  • organization_membership9 cols
  • Extract
  • Load
  • Keep in sync
ClickHouseDestinationClickHouseReady
zendesk schema
  • zendesk.ticketSynced
  • zendesk.userSyncing
  • zendesk.organizationSynced
  • zendesk.groupSynced
  • zendesk.ticket_formSynced
  • zendesk.organization_membershipSynced
Zendesk tables
43
fields, typed
444
relationships kept
23
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 Zendesk to ClickHouse in Weld.
In the app, with the API or an agent.

Setup guideAPI guideMCP docs
Weld · New Zendesk sync
ZendeskNew connectionZendeskAuthorised
Connection namezendesk
AuthorizeOpens Zendesk to grant read access
Use cases

Why sync Zendesk to ClickHouse?
Ready for analysis.

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

Build reliable dashboards and reports by querying Zendesk data directly in ClickHouse using SQL or your preferred BI tool.

  • Support metrics and SLA tracking

    Monitor ticket volume, resolution times, and satisfaction scores from Zendesk in ClickHouse. Correlate support data with product and customer data.

  • Centralized data warehouse

    Bring Zendesk data into ClickHouse 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 Zendesk to ClickHouse. Connect BI tools like Looker, Metabase, or Power BI.

Schema

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

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

Open the schema explorer
All 43 tables
  • ticket
  • user
  • organization
  • group
  • ticket_form
  • organization_membership
  • group_membership
  • ticket_metric
  • ticket_field
  • brand
  • ticket_comment
  • ticket_comment_attachment
  • ticket_activity
  • ticket_side_conversation
  • macro
  • sharing_agreement
  • ticket_audit
  • ticket_side_conversation_participant
  • ticket_side_conversation_event_message_to
  • brand_ticket_form
  • ticket_sharing_agreement
  • ticket_form_ticket_field
  • ticket_side_conversation_event
  • trigger
  • automation
  • automation_condition
  • trigger_condition
  • trigger_category
  • automation_action
  • macro_action
  • and 11 more
Weld MCP server

Ask your agent.
It queries ClickHouse for you.

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

Set up the MCP serverClaudeCursorChatGPTGemini
Claude CodeOpus 5
>

How many ticket rows do we have per brand? Use our Zendesk data in ClickHouse.

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

●weld·search_available_references
⎿raw.zendesk.ticket
raw.zendesk.brand
+ 41 more Zendesk tables
●weld·get_reference_schema
⎿ticket · 48 columns
joins brand on brand_id
●weld·run_query
⎿select b.id, count(*) from {{raw.zendesk.ticket}} t
join {{raw.zendesk.brand}} b on t.brand_id = b.id
group by 1
submitted
●weld·get_query_status
⎿DONE
●weld·get_query_result
⎿rows returned
✓Answered from Zendesk data in ClickHouse
>Ask about your Zendesk data
Under the hood

Technical considerations.
What to expect.

Reverse ETL

ELT vs. reverse ETL: Zendesk and ClickHouse

ELT (Extract, Load, Transform) moves data from Zendesk into ClickHouse for analysis. This is the approach shown on this page, and the one to use for dashboards, reports, and data models.

Reverse ETL works the other direction: it pushes enriched data from ClickHouse back into Zendesk. For example, you could sync computed lead scores or customer segments from your warehouse into Zendesk to personalize outreach.

Weld supports both directions, so you can build a complete data loop between Zendesk and ClickHouse.

ClickHouse to Zendesk
Incremental syncing
Weld uses incremental syncing where supported by the Zendesk API, loading only new and updated records to minimize data transfer and warehouse costs.
Schema handling
Weld automatically manages schema changes. If Zendesk adds new fields, they're detected and added to the corresponding ClickHouse 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

Zendesk setup guide

How to connect Zendesk to Weld, step by step.

Documentation

ClickHouse setup guide

How to connect ClickHouse to Weld, step by step.

Schema

Zendesk schema explorer

Browse all 43 tables and 444 fields.

Connector

Zendesk connector

Everything Weld does with Zendesk.

FAQ

Common questions.
About Zendesk to ClickHouse.

Start syncing Zendesk to ClickHouse.

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

ZendeskSource
WeldWeld
ClickHouseWarehouse
Start for freeTalk to us
Related

Related integrations.
More with Zendesk and ClickHouse.

View all