Skip to main content
Claude’s analytics API is only available on the Claude Enterprise plan. You must be on Claude Enterprise to connect this integration.

Benefits of Connecting Claude to Windmill

Connecting Claude to Windmill brings AI usage data directly into stats, performance reviews, and 1:1s — giving managers and engineers visibility into how Claude is being adopted across the team.
  • Tracks how your team uses Claude across chat, Claude Code, and Claude’s Office Agent for Excel and PowerPoint
  • Surfaces adoption patterns across conversations, coding sessions, skills, and connectors without self-reporting
  • Helps managers understand AI tool usage and coach their teams on effective workflows
  • Provides concrete data for performance conversations about productivity and tool adoption
  • Syncs automatically — no manual tracking or surveys required
Windmill turns Claude’s enterprise analytics into actionable stats that flow into your existing performance workflow.

How to Connect Claude

1

Get your API key from Claude

Go to claude.ai/analytics/api-keys and generate an API key. You must be a Primary Owner of your Claude organization to access this page.
2

Open the Claude integration in Windmill

In Windmill, navigate to Settings > Integrations, find Claude, and click Connect.
3

Paste your API key and connect

Paste the API key from Claude into the input field and click Connect Claude. Windmill will validate the key and begin syncing analytics within the hour.
Claude is an account-level integration — an admin connects it once and it covers your entire Claude organization. Individual users don’t need to connect separately.

Connected Data

When connected, Windmill syncs per-user analytics from Claude’s Enterprise Analytics API. This is usage data — Windmill does not access any conversations, prompts, code, or file content.

Claude Chat

StatDescriptionUnit
ConversationsDistinct conversations started in Claudeconversations
Chat MessagesMessages sent in Claude chatmessages
Artifacts CreatedArtifacts created during Claude conversationsartifacts

Claude Code

StatDescriptionUnit
SessionsDistinct Claude Code sessionssessions
CommitsCommits made through Claude Codecommits
Pull RequestsPull requests created through Claude CodePRs
Lines AddedLines of code added through Claude Codelines
Lines RemovedLines of code removed through Claude Codelines
Edits AcceptedNumber of AI-generated code edits acceptededits
Edit Acceptance RateRatio of accepted to suggested AI edits%

Skills and Connectors

StatDescriptionUnit
Skill UsageClaude skill invocations across all productsinvocations
Connector UsageClaude MCP/connector invocations across all productsinvocations

Claude Office Agent — Excel

StatDescriptionUnit
Excel SessionsDistinct Claude for Excel sessionssessions
Excel MessagesMessages sent in Claude for Excelmessages
Excel Skills UsedSkill invocations in Claude for Excelinvocations
Excel Connectors UsedConnector invocations in Claude for Excelinvocations

Claude Office Agent — PowerPoint

StatDescriptionUnit
PowerPoint SessionsDistinct Claude for PowerPoint sessionssessions
PowerPoint MessagesMessages sent in Claude for PowerPointmessages
PowerPoint Skills UsedSkill invocations in Claude for PowerPointinvocations
PowerPoint Connectors UsedConnector invocations in Claude for PowerPointinvocations
All stats are tracked per employee, per day.

Visibility and Access

Claude stats in Windmill follow the manager hierarchy visibility model:
  • Employees can see their own Claude stats
  • Managers can see Claude stats for their direct reports and anyone in their reporting chain
  • Admins can see Claude stats for everyone in the organization
  • Peers cannot see each other’s Claude stats
This means Claude analytics are treated like other sensitive performance data in Windmill — visible to the people who need it for coaching and evaluation, but not exposed broadly.

Permissions

Windmill requests read-only access to Claude’s Enterprise Analytics API.
PermissionPurpose
Read user analyticsTo sync usage stats per team member into Windmill
No access to conversations or promptsWindmill never reads, stores, or accesses any conversation content from Claude
No access to code or filesWindmill does not read any code, files, or artifacts — only aggregate usage counts
Read-only accessWindmill never modifies anything in Claude

User Matching

Windmill matches Claude users to employees using their email address. If a Claude user’s email matches an employee’s email in Windmill, their stats are automatically attributed to that employee. If you notice stats that aren’t being attributed correctly, check that the email addresses in Claude match the employee emails in Windmill.

FAQs

Yes. Claude’s analytics API is only available on the Enterprise plan. The integration won’t work with Claude’s free, Pro, or Team plans.
No. Windmill only reads usage analytics from Claude’s API — session counts, message counts, and acceptance rates. Windmill never accesses conversation content, prompts, code, files, or artifacts.
Windmill syncs with Claude once per hour. New usage data typically appears within a few hours of the activity happening in Claude, as there is a short delay in Claude’s analytics processing.
Yes. Every employee can see their own Claude stats in Windmill.
No. Claude stats follow the manager hierarchy — only your manager (and their managers) can see your stats. Peers cannot see each other’s Claude usage data.
No. Claude is an account-level integration. An admin connects it once using an API key from Claude’s analytics settings, and it covers your entire Claude organization.
Their historical Claude stats remain for context, but Windmill stops attributing new activity once they are an Archived user.
This usually happens when your email in Claude doesn’t match your email in Windmill. Make sure the email addresses match, or ask an admin to check the user mapping.