Copy page

Anthropic

Chat Messages

Ingests individual chat messages from the Anthropic Compliance API for visibility into Claude conversation activity across your organization.

Sync Type: Incremental

Requirements

Before configuring this input, you need to:

1. Create a Compliance Access Key — Anthropic docs.

   • Log in to your Anthropic account
   • Navigate to the Data Management Settings
   • Create a new Compliance Access Key
   • Ensure the key has the read:compliance_user_data scope
   • Copy and securely store the generated key

2. Identify Organization IDs (optional):

   • You can filter chats by specific Anthropic organization IDs
   • If not specified, chats for all accessible organizations will be fetched
   • Organization IDs are in the format: org_xxxxxxxx

Details

Each sync collects the chats that were created or updated since the previous sync, so new messages added to existing chats are picked up. Chats are collected for every user in the selected organizations.

Each message is emitted as its own record with chat and user context attached (chat ID, chat name, user, organization, and project). This avoids record size limits from large chat histories. When a chat receives new messages, every message in that chat is emitted again, so a destination can receive the same message more than once. Use the message id to deduplicate.

If a chat's messages can't be retrieved, the sync stops and reports an error. Progress up to that chat is kept, and the next sync resumes from it, so no chats are skipped.

For the first run, if no backfill start time is specified, the input defaults to the current time. All subsequent syncs will be incremental from that point forward.

Configuration

The following configuration defines the input parameters. Each field's specifications, such as type, requirements, and descriptions, are detailed below.

Settings

Setting	Type	Required	Description
Backfill Start Time	string	No	Date to start fetching data from (ISO 8601 format). If not specified, defaults to the current time on the first sync. All subsequent syncs will be incremental.
Organization IDs	string[]	No	List of Anthropic organization IDs to filter chats by. If not specified, chats for all organizations accessible by the provided access key will be fetched.
API Rate Limit	object	No	Optional limit on the connector's outbound request rate to the source API. Leave blank to use the connector's default behavior. See API Rate Limiting for the field format, limits, and how to choose a value.

Secrets

Secret	Type	Required	Description
Compliance Access Key	string	Yes	Compliance Access Key with read:compliance_user_data scope. Created in Data Management Settings.

Rate Limits

Scope	Limit	Window	Notes
API Requests	4	Per second	Requests per second across all endpoints
Page Size	1,000	Per request	Maximum records returned per page

Headers: x-api-key

Source: List chats API reference

Related Articles

• Retrieve and delete chats, files, and projects
• List chats API reference
• Set up the Compliance API

Sample Record

Code
{
  "id": "claude_chat_msg_123456",
  "role": "user",
  "created_at": "2026-04-08T14:30:45.123Z",
  "content": [
    {
      "type": "text",
      "text": "Can you help me review this pull request for security issues?"
    }
  ],
  "files": null,
  "artifacts": null,
  "chat_id": "claude_chat_789012",
  "chat_name": "PR Security Review",
  "chat_user": {
    "id": "user_abcdefgh",
    "email_address": "user@example.com"
  },
  "organization_id": "org_12345678",
  "organization_uuid": "550e8400-e29b-41d4-a716-446655440000",
  "project_id": "claude_proj_01KGp4eZNug9ri4kE35RSppq"
}

Sync frequency

By default this input polls approximately every 10 seconds, with each sync beginning after the previous one completes. A cron schedule configured on the pipeline overrides this cadence. See Input Sync Frequency for details.