The Fleece AI Brain Zendesk connector syncs your support tickets — subject, description and status — into a local-first knowledge base of plain Markdown and SQLite on your own machine. Each ticket becomes a note titled by its subject and tagged by status, and when a ticket changes its note is refreshed in place. From there, any MCP-compatible AI app such as Claude Desktop or Cursor can answer from your real support history, with the source one click away.
What syncs from Zendesk
Every ticket arrives as a knowledge node — an ordinary file you can open, link and search, not a row trapped in a helpdesk.
Support tickets
Tickets stream in through Zendesk's incremental ticket export, so a large backlog pages in run after run.
Subject and description
Each ticket's subject becomes the note title and its description becomes the body.
Status as a tag
Open, pending, solved — the ticket status is attached as a tag like status/solved you and your agents can filter on.
Recent tickets first
The first sync backfills the last 90 days; later runs resume from a stored cursor, and a stale cursor self-heals.
Updated, never duplicated
When a ticket is edited or resolved, its note is refreshed in place — matched on the ticket's update time, so a re-sync never creates duplicates.
Connect Zendesk in four steps
No export, no CSV wrangling — one sign-in from the desktop app.
- 01
Install Fleece AI Brain
Download the desktop app for macOS, Windows or Linux and open your vault — a folder of plain Markdown files on your machine.
- 02
Open Connectors and pick Zendesk
In the app, open the connectors panel, choose Zendesk, and sign in with your Zendesk account. OAuth is brokered securely and your subdomain is captured; your tickets never pass through our servers.
- 03
Let the backfill run
The first sync reaches back 90 days. A large ticket history pages in over a few runs, then the connector keeps up with new and changed tickets.
- 04
Let it sync — then ask
Sync runs in the background and stays up to date. Point Claude Desktop, Cursor or any MCP app at your Brain and ask how you fixed this exact error before.
Every answer you need is in a ticket you already closed.
A support queue is the most honest record of your product a company owns: the real questions customers ask, the workarounds that hold, the fix that finally worked. And the moment a ticket is solved, it drops out of view — the next agent hits the same wall, and the next customer waits for an answer your team already wrote months ago.
The Zendesk connector turns that closed queue into a living troubleshooting playbook. Each ticket becomes a permanent note, tagged by status and linked to the products and errors it mentions, so the resolution from six months ago is one question away — for a new hire or for an AI agent triaging the next ticket.
Your tickets reach your disk, not ours.
Authentication is a standard OAuth sign-in brokered through Pipedream Connect, but the actual sync calls the Zendesk REST API directly from the desktop app on your machine. Raw tickets never transit Fleece's servers or any third party — they land straight in your vault as Markdown and SQLite.
That is the whole trust model: we can't read your support queue, period. The files are yours, they open in Obsidian or any editor, and if you ever leave, you take everything with you.
- +Direct Zendesk-to-device sync — raw tickets never touch our servers
- +Vault = plain .md files + SQLite, 100% Obsidian-compatible
- +Works offline once synced; cloud sync is optional and end-to-end encrypted
Give every AI app your support history.
One copy-paste connects the Brain to Claude Desktop, Cursor, Cline, Zed or agents you build. From then on, "how have we resolved this timeout error before?" is answered from the actual tickets — with the source note one click away.
Because every agent and tool reads the same graph, a triage agent can draft a reply grounded in what already worked, not a generic guess. On Teams, the organization map also shows which agents used that knowledge and what they cost.
Zendesk connector — FAQ
Do my Zendesk tickets pass through Fleece's servers?+
No. Sign-in uses a brokered OAuth flow, but the sync itself calls the Zendesk REST API directly from the desktop app on your machine. Raw tickets land straight in your local vault and never transit Fleece's servers or any third party; we never see or store your support content.
Which tickets does the connector sync?+
The tickets in the Zendesk account you connect. The first sync only reaches back 90 days, and a large backlog pages in over several runs, so you scope it by which account you connect and how far back the first run reaches.
Does it write anything back to Zendesk?+
No. The connector is read-only: it pulls tickets into your knowledge base and never comments, updates a status or changes anything in your helpdesk.
How often does it sync, and does it pick up updates?+
Sync runs in the background and resumes from a stored cursor, so each run fetches new activity. When a ticket is edited or resolved, its note is refreshed in place rather than duplicated — matched on the ticket's update time.
Which plan do I need to connect Zendesk?+
The local brain is free, and connectors are the paid lever: Solo (€12/month) includes up to 3 connected tools, Pro (€24/month) makes them unlimited with auto-sync. Every plan starts with a 14-day trial, no card required.
How do I ask Claude or Cursor about a past ticket?+
Connect the Brain to Claude Desktop, Cursor or any MCP-compatible app with a single copy-paste. Your AI then answers from the synced Zendesk knowledge, citing the exact ticket it drew from.
Can I open the synced tickets outside the app?+
Yes. Every ticket is an ordinary Markdown file in your vault, fully Obsidian-compatible — open, edit or grep it with any tool, and take it with you if you ever leave.
What happens if I disconnect Zendesk?+
Sync stops, and everything already in your vault stays yours — the notes are local files, not a mirror that vanishes with the connection.
Turn every solved ticket into a searchable answer.
Connect Zendesk in one sign-in and give your whole AI stack the troubleshooting playbook your team has already written.