Niches · Customer support & helpdesk

Export tickets and help centre content

Two or three companies' docs show a full fit.

3companies, full fit
18companies, fit with a limit
18companies carry the tag
5share of the category's work
4first-hand accounts

What counts as done

All articles or tickets retrieved with bodies and attachments by paged or bulk calls, before any seat or plan change.

Measured, for our own tests: the counts match the UI. No docs we read state these figures, so they don't count against a listing here.

How agents ask for it: export our help centre to markdown, pull every ticket before we cancel, sync articles into our docs, keep the archive after we downgrade

Does the job 3

The docs show it meets the test above, and nothing we read says otherwise.

ListingWhy
Help Scout API + MCP B
Help Scout PBC
The Docs API lists articles per collection, 50 a page up to 100, with an article fetch for bodies, and conversations and threads page to completion through the Inbox API. source
Intercom API + MCP BB
Intercom, Inc. (with Intercom R&D Unlimited Company in Ireland)
Articles and internal articles list and search with paging, conversations page by cursor, and export jobs cover content and reporting data. source
Plain API + MCP B
Not Just Tickets Ltd
Help centers and articles can be fetched through GraphQL, and threads page by cursor with chosen fields. source

Does the job, with a limit 18

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
Chatway MCP C
Poptin Ltd
Conversations page at up to 100 with messages by cursor, but the knowledge base is reachable only through search-knowledge-base, not a list, and Free keeps 30 days of history. source
Chatwoot API D
Chatwoot Inc.
Conversations and messages page to completion, but the application API has no list-articles call (only add), and acc-20 notes the free hosted tier keeps limited history. source
Crisp API + MCP D
Crisp IM SAS
Knowledge Base articles list and read through MCP helpdesk tools one at a time, and conversations page at up to 50. source
Dixa D
Dixa ApS
Knowledge collections have a catalog and articles are fetched one by one; conversations come through search and per-conversation message calls, with no bulk export endpoint found. source
Drag E
DragApp.com Ltd
list_articles and get_article cover the knowledge base, and cards list per column, but email bodies come one thread at a time. source
FreeScout F
FreeScout
Conversations with threads page to completion at 100 a page, but the API covers no knowledge base, which is a separate module. source
Freshdesk API + MCP D
Freshworks Inc.
Solution categories, folders and articles have list endpoints, but ticket lists cap at 300 pages (30,000 tickets) and archived tickets drop out of search. source
Front API + MCP BB
FrontApp, Inc.
Knowledge base articles and categories list per knowledge base and conversations page by cursor, but bodies come one message at a time and Starter's 50 requests a minute makes a large archive slow. source
Gladly C
Gladly Software, Inc.
Export jobs cover the lifetime of delivered communications, but schedule changes go through Gladly Support, files expire after 14 days and one-time exports over six months may carry a fee. source
Gorgias API + MCP C
Gorgias Inc.
Tickets list by cursor, but email headers and original bodies are dropped after 30 days (only stripped versions kept), and Help Center tools work article by article. source
HelpDesk D
Text, Inc.
Tickets page by next cursor and silo reaches archive, spam and trash, but HelpDesk has no help centre in this API, and each call counts against the monthly allowance. source
Kustomer D
Kustomer, LLC
Knowledge base and archive search endpoints exist, but standard search covers two years of updates and archived records need the separate archive search. source
LiveAgent D
Quality Unit, s. r. o.
MCP lists knowledge bases and categories and gets articles one by one; tickets come through filtered pages capped at 10,000 per filter, so a large archive needs date slicing. source
Missive API + MCP C
Heliom Inc.
Conversations page with until, but bodies need one Get a Message call each, and Missive has no help centre to export. source
Pylon API + MCP C
Pylon Labs, Inc.
Issues page by cursor and MCP lists knowledge bases, collections and articles, but article export goes one get_article at a time. source
Zammad E
Zammad GmbH
Tickets and articles page with page and per_page under fixed hard limits, and the Knowledge Base has an API, with no bulk export endpoint. source
Zendesk Support API B
Zendesk, Inc.
Incremental cursor export covers tickets, and acc-09 imported a Zendesk help centre, but acc-26 lost archive access while downgrading seats. source
Zoho Desk B
Zoho Corporation Private Limited
Tickets, archived tickets and articles have list operations, but paging is from and limit at 50 with credit costs rising to 100 a call past 100,000 records. source

Doesn't do this job 1

Listings in the category that do something else, with the reason.

ListingWhy
Landbot MCP server E
Landbot
list_knowledge_sources shows what an agent knows, but nothing exports conversations or help centre articles. source

What stops agents finishing

  • archive access needs a paid seat
  • hosted free tier retention limit
  • articles only reachable one at a time

Around it

After: document-extraction.html-to-markdown, knowledge.ingest.

Where this comes from

Weight 5 of 100 in Customer support & helpdesk: 4 of 42 accounts (acc-08, 09, 20, 26); kept low because two are about leaving rather than agents working

The same as data: /api/v1/use-cases/support.export-knowledge-and-archive.json, or the MCP tool get_use_case with id support.export-knowledge-and-archive. Other jobs in this category: /api/v1/niches?category=support.

Draft, read 2026-11-12 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.