Skip to main content

Projects

Ingests Anthropic project metadata along with project details and attachments for compliance visibility and data governance.

Sync Type: Full Snapshot

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 projects by specific Anthropic organization IDs
    • If not specified, projects for all accessible organizations will be fetched
    • Organization IDs are in the format: org_xxxxxxxx

Details

This input fetches all Anthropic projects accessible by the provided Compliance Access Key. For each project, it retrieves:

  • Project metadata - name, organization, creator, visibility, and timestamps
  • Project details - description, instructions, attachment and chat counts
  • Project attachments - documents (with full content) and files associated with the project

Results are sorted by created_at and paginated with a limit of 100 records per page. Each sync performs a full snapshot of all projects.

Configuration

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

Settings

SettingTypeRequiredDescription
Organization IDsarray of stringsNoList of Anthropic organization IDs to fetch projects for. If not specified, projects for all organizations accessible by the provided access key will be fetched.

Secrets

SecretTypeRequiredDescription
Compliance Access KeystringYesCompliance Access Key with read:compliance_user_data scope. Created in Data Management Settings.

Rate Limits

ScopeLimitWindowNotes
API Requests4Per secondRate limited to 4 requests per second
Page Size100Per requestMaximum records returned per page is 100

Headers: x-api-key

Sample Record

{
"id": "claude_proj_abc123def456",
"is_private": false,
"name": "Security Automation",
"organization_id": "org_12345678",
"updated_at": "2025-03-20T10:15:30.000000Z",
"created_at": "2025-03-18T14:30:45.000000Z",
"user": {
"email_address": "user@example.com",
"id": "user_abcdefgh"
},
"details": {
"attachments_count": 3,
"chats_count": 12,
"created_at": "2025-03-18T14:30:45.000000Z",
"description": "Automated security workflows and compliance checks",
"id": "claude_proj_abc123def456",
"instructions": "Follow security best practices and ensure all outputs comply with organizational policies.",
"is_private": false,
"name": "Security Automation",
"organization_id": "org_12345678",
"updated_at": "2025-03-20T10:15:30.000000Z",
"user": {
"email_address": "user@example.com",
"id": "user_abcdefgh"
}
},
"attachments": [
{
"created_at": "2025-03-19T09:00:00.000000Z",
"filename": "Security Guidelines.md",
"id": "claude_proj_doc_xyz789",
"mime_type": "text/markdown",
"type": "project_doc",
"content": {
"content": "This document outlines the security guidelines for the project...",
"created_at": "2025-03-19T09:00:00.000000Z",
"filename": "Security Guidelines.md",
"id": "claude_proj_doc_xyz789",
"user": {
"email_address": "user@example.com",
"id": "user_abcdefgh"
}
},
},
{
"created_at": "2025-03-19T11:30:00.000000Z",
"filename": "System Architecture.pdf",
"id": "claude_file_qrs456",
"mime_type": "application/pdf",
"type": "project_file"
}
]
}