Technical Architecture Guide • Intercom REST API v2.11 • Local CSV/NDJSON/Markdown Extraction

Why Intercom CSV Export Is Missing Message Text (And How to Export Full Transcripts Locally)

If you have ever exported conversations from Intercom's reporting dashboard to prepare a SOC2 compliance archive, migrate helpdesks, or build an AI RAG knowledge base, you likely noticed an immediate blocker: the native CSV export only includes metadata columns (Conversation ID, timestamps, assignee, tag names, SLA timers) and omits the actual customer messages, agent replies, and internal notes.

1. The Structural Reason: Why the List Endpoint Doesn't Include Transcripts

In Intercom REST API v2.11, listing conversations via GET /conversations?per_page=150 returns summary objects only. The full message thread (conversation_parts.conversation_parts, up to 500 parts per ticket) is stored as a nested entity that is only returned when you query each conversation individually:

GET https://api.intercom.io/conversations?per_page=150&starting_after={cursor}
Headers:
  Authorization: Bearer <READ_ONLY_TOKEN>
  Intercom-Version: 2.11

# For each conversation.id in page.conversations (N+1 Detail Fetch):
GET https://api.intercom.io/conversations/{id}?display_as=html

2. The Four Hidden Pitfalls When Exporting 10,000+ Transcripts

3. How ChatVault Solves All Four Pitfalls 100% Locally

ChatVault: Conversation Transcript & CSV Exporter (for Intercom) runs inside a dedicated browser workstation tab using FileSystemWritableFileStream (Direct-to-Disk streaming) and 50-conversation IndexedDB checkpoints:

Try the 500-Chat Interactive B2B Sandbox Demo Right Now (No API Token Needed)

Test a full 500-conversation multi-turn export to Excel CSV, NDJSON, or Obsidian Markdown in 3 seconds directly in your browser.

Launch 500-Chat Interactive Demo & Workstation →

Disclaimer: Independent third-party utility. Not affiliated with, endorsed, or sponsored by Intercom, Inc. • Home • Privacy Policy