Integrations

ComplianceLayer connects to your existing security and DevOps toolchain. Webhooks and the SDKs are available today; the Zapier integration's API is live, pending directory listing.

Native Integrations

First-party integrations that connect directly to your tools, configured from Settings → Integrations in your dashboard.

SDKs

Client libraries with automatic retry, error mapping, and polling helpers. Python offers both sync and async clients. Both packages are published: pip install compliancelayer and npm install compliancelayer.

Webhook-Based Integrations

Outbound webhooksare the integration path that works today. They deliver real-time HTTP notifications when scans complete or alerts trigger, and work with any system that accepts HTTP POST — including Slack and Teams incoming webhook URLs.

Same event system. The Zapier integration is built on top of the same events that webhooks deliver, so anything you build on webhooks keeps working alongside it.

Comparison

FeatureZapierWebhooksSDKs
StatusAPI live, app pending listingAvailableAvailable (npm + PyPI)
Scan notificationsTrigger → any appJSON POSTPoll
Alert notificationsTrigger → any appJSON POSTPoll
Run scansRun Scan actionscan()
Minimum planProFreeFree
Plans includedPro, MSP, Enterprise, CustomAll plans (Free: 1 endpoint)All plans

Plan gating is enforced by the API, so the tiers above match what your key can actually call. See Pricing for what else each plan includes.

Integration Architecture

All integrations are built on ComplianceLayer's event system. When a scan completes or an alert triggers, the event dispatcher fans out notifications to every configured channel:

Scan Engine
scan.completed
Event Dispatcher
parallel fan-out
Webhookslive
Zapierlive
Fault-tolerant: Each integration is dispatched independently, so a failure in one does not affect delivery to the others. Failed webhook deliveries are retried with exponential backoff.

Getting Help

Need help setting up an integration?