How data becomes insight
Every piece of data Causeloop receives goes through the same pipeline:Raw signal arrives
A connector polls your external tool on a schedule, or your system pushes a record to the ingestion API, or an inbound webhook delivers an event.
Normalization & deduplication
Records are validated, normalized to a canonical shape (title, severity, source, timestamp), and deduplicated by
external_id + source.Issue created or updated
Each unique signal becomes an Issue — the atomic unit of work in Causeloop.
Pattern clustering
Issues with similar root causes are clustered into Patterns. Causeloop surfaces which pattern a new issue belongs to in real time.
Three ways to bring data in
Connectors
Managed integrations with external tools — Jira, PagerDuty, GitHub, ServiceNow, Datadog, and more. Causeloop polls on your schedule, handles OAuth, and backfills historical data. Best for tools you already use.
Ingestion API
Push records directly from any system using
POST /ingest/events (single event) or POST /ingest/batch (up to 500 at once). Use this for home-grown tools, scripts, or pipelines that don’t have a managed connector.Inbound Webhooks
Register a connector as a webhook target so third-party tools can push events to Causeloop in real time. Every payload is HMAC-SHA256 verified and the endpoint fails closed — a missing or invalid signature is always a 401.
One way to push results out
Outbound webhooks let Causeloop notify your systems when something significant happens — a sync succeeds or fails, an issue is ingested, a pattern is detected. Register an HTTPS endpoint viaPOST /webhooks, choose your event types, and Causeloop signs every delivery with your secret.
See Webhooks for the full inbound and outbound reference.
Where to manage integrations
Admins manage all integrations in the Causeloop UI at Settings → Integrations (https://app.causeloop.ai/integrations). From there you can:
- Browse the connector catalog and connect a new source
- View sync history and health for each connector
- Register and manage outbound webhook endpoints
- Rotate signing secrets
API quick-reference
| Resource | Base path | Required scope |
|---|---|---|
| Connector catalog | GET /v1/connector-catalog | connectors:read |
| Connectors (CRUD) | /v1/connectors | connectors:read / connectors:admin |
| Connector sync / backfill | POST /v1/connectors/{id}/sync | connectors:admin |
| OAuth flow | /v1/connectors/{id}/oauth/start | connectors:admin |
| Ingest (single) | POST /v1/ingest/events | ingest:write |
| Ingest (batch) | POST /v1/ingest/batch | ingest:write |
| Webhooks (outbound) | /v1/webhooks | webhooks:read / webhooks:admin |
| Inbound webhook receiver | POST /v1/webhooks/inbound/{connector_id} | HMAC signature (no Bearer) |
| Integrations health | GET /v1/integrations/health | connectors:read |
All API requests are scoped to your workspace. Include your API key as
Authorization: Bearer <token>. See API Reference for full endpoint documentation.