When to use
- You need to analyze raw data from ClaudIA conversations outside the dashboard
- You want to cross ClaudIA metrics with data from your own systems (CRM, BI, data lake)
- You want to query a conversation programmatically, from your own environment
Prerequisites
- Access to your project's Cloud Chat as a supervisor, CX Engineer or administrator — for the Report Builder
- For the technical paths (Data Export and API): a technical or data team on your side
About this article
There are three ways to get ClaudIA's data as a table today. Which one to choose depends on who will consume it: someone in the operation, your company's BI, or a system.
How it works
1 — Report Builder (no technical team needed)
Build your own tables, filters and cross-analyses inside Cloud Chat using the ClaudIA Topic: conversations, messages, generated responses, audit feedback, CSAT and knowledge base content. Exports to CSV, XLSX or JSON.
It is the fastest path, and the one we recommend when your operation has no dedicated data team.
2 — Data Export: raw data in your own data lake (S3)
We provide an S3 bucket dedicated to your company, with Parquet files partitioned by date and a daily D-1 load (today you have everything up to yesterday). This is the path for BI and data lake work, including joining support data with your other internal sources.
The ClaudIA tables delivered to the bucket:
| Table | One row is |
|---|---|
claudia_conversation |
a conversation ClaudIA handled |
claudia_messages |
a message exchanged in the conversation |
claudia_prompt_revision |
one call to the model, with the content it retrieved and the action that followed |
claudia_contents |
a knowledge base content section |
claudia_conversation_feedback |
a quality review made by a human agent |
claudia_csat |
a CSAT response |
eddie_result_outcomes |
one controlled flow execution and its outcome |
The Cloud Chat tables come along with them (conversations, contacts, tags, CSAT, daily agent and team metrics). The Cloud Chat conversation id is the key that ties both sides together.
Access is read-only, and control stays with you: your team sends the identifier of a role in your own AWS account, and we authorize it on the bucket. We do not issue any credential of ours to your team.
3 — Public API (one conversation at a time)
We also have a documented public API. It is meant for querying and integrating, not for bulk extraction:
- ClaudIA API — a conversation summary (status, resolution reason, tag, whether it went to N2, and the messages) and the execution trace behind a processed message
- Cloud Chat API — list conversations, find a conversation by any identifier, list messages, contacts, labels, inboxes and teams
Authentication uses the sign-in of a Cloud Chat user from your own account. Responses are paginated and filters follow a fixed allowlist of parameters — which is why, for a historical BI load, Data Export is the right path, not the API.
How to request it
- Report Builder: already available in Cloud Chat, under Reports.
- Data Export: ask your Cloud Humans point of contact (CSM) or our support team. The service is not enabled by default. Our team provisions the bucket, your team sends the identifier of the role in your AWS account, and delivery starts the next day.
- API: the documentation is public, and the Find your credentials page in the technical documentation issues the token for your user.
Notes
- Technical documentation for your data team: docs.cloudhumans.com — the Data Export table and column catalog, the full API reference (ClaudIA and Cloud Chat), bucket layout and best practices.
- Data Export step by step: How to access your operation's raw data (Data Export)
- ClaudIA Report Builder: How to create custom ClaudIA reports