Zendesk Connector

Zendesk is a customer service platform designed to foster better customer relationships through its comprehensive ticketing, support, and engagement.

4.8 on G2
Weld · Data Sources
ZendeskLive
ticketSynced
userSynced
organizationSynced
groupSyncing
organization_membershipQueued
Lands insnowflakebigquerydatabricksAgent context over MCP
How it works

Set up in minutes.
No code, no maintenance.

Zendesk

Zendesk

Data source

Authenticating...
Ready to connect
Overview

Zendesk in your warehouse.
Ready for your agents.

Zendesk is a customer service platform designed to foster better customer relationships through its comprehensive ticketing, support, and engagement. Weld's Zendesk connector is fully managed: it extracts data from Zendesk, loads it into your warehouse, and keeps it in sync. The data lands in a clean, documented schema with agent context attached, so analysts can query it with SQL or dbt, and agents can query it over the Weld MCP server without guessing at tables or joins.

AgentsQuery over MCPYour warehouse37 tables, with agent contextWeldExtract, load, keep in syncZendeskSource
Agent context

Zendesk data schema.
The map your agents read.

Every table, field and relationship Weld syncs from Zendesk is served to agents as context over MCP, so they pick the right tables and join on the right keys.

tables
37
fields
345
relationships
16
Open the schema explorer
Open the full schema explorer
Weld MCP server

Ask your agent.
It already knows Zendesk.

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

  • Agent contextZendesk tables, fields and joins
  • QuerySQL against your warehouse
  • OperateCheck, rerun and refresh syncs
Claude CodeOpus 5
>

How many ticket rows do we have per custom_status? Use our Zendesk data.

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

●weld·search_available_references
⎿raw.zendesk.ticket
raw.zendesk.custom_status
+ 35 more Zendesk tables
●weld·get_reference_schema
⎿ticket · 26 columns
joins custom_status on custom_status_id
●weld·run_query
⎿select c.id, count(*) from {{raw.zendesk.ticket}} t
join {{raw.zendesk.custom_status}} c on t.custom_status_id = c.id
group by 1
submitted
●weld·get_query_status
⎿DONE
●weld·get_query_result
⎿rows returned
✓Answered from Zendesk data in your warehouse
>Ask about your Zendesk data
Weld Connect API

Set it up in code.
One REST API.

Use the Weld Connect REST API to create Zendesk connections, configure ELT syncs, and manage pipelines entirely through code. Built for embedding, automation, and CI/CD workflows.

POST/elt_syncs
▌
FAQ

Common questions.
About connectors.

Something not covered here? A data engineer can walk through your setup with you.

Talk to us

Put your Zendesk data to work.

Connect Zendesk, pick a warehouse, and your agents can query it today. Free for 14 days, no credit card.

ZendeskSource
WeldWeld
MCPAgents