Turn every policy into automated workflows with built-in enforcement and audit-ready proof.
Claude Compliance API Integration

Process Street is a Compliance Operations Platform: workflows, approvals, audit trails and evidence collection that compliance and operations teams run every day. We are building a native connection to Claude Enterprise’s Compliance API so that Claude Enterprise activity flows directly into those same workflows, instead of living in a separate export nobody reviews.
Status: early access. This integration is in active development and is not yet generally available. The page below describes what we are building and why, so compliance teams already evaluating Claude Enterprise can register interest and get early access once the connector ships.
What the Claude Compliance API integration does
Claude Enterprise generates activity and audit events every time an admin changes a setting, a user signs in, or a workspace configuration changes. Today, a compliance team has to pull that activity out of Claude Enterprise on its own and manually fold it into whatever review process it already runs. The Process Street connector removes that manual step.
Once connected, Claude Enterprise activity feed and audit log events route into Process Street as triggers for existing workflow runs: an audit-review checklist, a retention task, or an approval step, depending on how a customer has their compliance program set up. The event and the workflow live in the same system of record.
How it works
- Claude Enterprise emits an activity or audit log event (an admin action, a sign-in, a configuration change).
- Process Street reads that event through the Compliance API’s activity feed surface.
- The event is attached to a Process Street workflow run: an audit-review checklist, an evidence-collection task, or an approval, depending on the customer’s own compliance program.
- The workflow run carries a full audit trail: who reviewed the event, when, and what was decided.
The connector is designed to poll the Compliance API on a fixed interval using cursor-based checkpointing, so only new events are pulled each cycle, with backoff on rate-limit responses. Every event surfaced inside Process Street is labeled as coming from Claude Enterprise, so a reviewer always knows the source.

The screen above shows the shape of the connection: an incoming Claude Enterprise activity event triggers a highlighted audit-review task inside an existing Process Street workflow run, with the same assignment and due-date tracking as every other task.
Use cases
- Audit trail consolidation. Keep Claude Enterprise admin activity in the same evidence trail as every other compliance control, instead of a separate export.
- Review workflows. Trigger a standing audit-review checklist whenever a sensitive Claude Enterprise action occurs, with assignment, due dates, and sign-off tracked in Process Street.
- Retention and evidence collection. Route Claude Enterprise events into the same retention schedule and evidence-collection process a compliance team already runs for other systems.
- Approvals. Require a documented approval step before a flagged Claude Enterprise event is closed out.
What data the integration reads
The integration is scoped to the Compliance API’s activity feed and audit log events for Claude Enterprise: admin actions, sign-ins, and workspace configuration changes. It does not read conversation content today. Any future extension to conversation-level data would only happen with explicit customer authorization, and would be documented here before it ships.
Security and compliance
Process Street maintains SOC 2 Type II and ISO 27001 certifications, and is HIPAA compliant. Current reports and certificates are available on our security page. Any credential this integration uses to call the Compliance API will be stored as an encrypted credential in Process Street’s existing secrets infrastructure, scoped per customer organization, and never logged or exposed in plaintext.
Why Process Street for Claude Enterprise compliance
Process Street has 5,000+ integrations, so Claude Enterprise activity does not need to live in a system by itself. It sits alongside every other control, approval, and audit trail a compliance team already runs. Process Street is the AI-native workflow runtime built for compliance operations, not a legacy checklist tool bolted onto a new AI surface.
Get early access
This integration is in development. If your team runs Claude Enterprise and wants Claude activity inside your existing compliance workflows, request early access and we will reach out when the connector is ready to pilot.
Frequently asked questions
Is the Process Street Claude Compliance API integration live today?
No. It is in active development. This page describes the planned integration so teams evaluating Claude Enterprise can register interest and request early access.
What is the Claude Compliance API?
It is Anthropic’s API for Claude Enterprise customers to pull activity, audit log, and (where authorized) conversation data out of Claude Enterprise for compliance and archiving purposes.
Which Claude product does this integration cover?
Claude Enterprise. The planned integration reads Claude Enterprise’s activity feed and audit log events through the Compliance API.
Does this integration read Claude conversation content?
No, not in the planned first version. It is scoped to activity feed and audit log events. Any extension to conversation-level data would require explicit customer authorization and would be documented here before it shipped.
How do I get early access?
Request early access through our demo form. We will reach out to schedule a pilot once the connector is ready.