Skip to main content
Causeloop needs signal from your systems to find the patterns behind recurring failures. There are three ways to bring that signal in, and one way to push results back out.

​
How data becomes insight

Every piece of data Causeloop receives goes through the same pipeline:
1

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.
2

Normalization & deduplication

Records are validated, normalized to a canonical shape (title, severity, source, timestamp), and deduplicated by external_id + source.
3

Issue created or updated

Each unique signal becomes an Issue — the atomic unit of work in Causeloop.
4

Pattern clustering

Issues with similar root causes are clustered into Patterns. Causeloop surfaces which pattern a new issue belongs to in real time.
5

Prediction & recommendation

Causeloop predicts which open issues will recur and surfaces recommendations for the fix most likely to hold.

​
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 via POST /webhooks, choose your event types, and Causeloop signs every delivery with your secret. See Webhooks for the full inbound and outbound reference.

​
Monitoring your sources

Once data is flowing, Sources gives you a per-source view of real ingest volume — every place findings actually arrive from, whether a configured connector or an ad-hoc ingestion channel (e.g. custom_api for direct API/file ingest with no connector configured). GET /v1/sources returns one card per source: issue count over a rolling 30-day window, last-ingested timestamp, and a 14-day daily sparkline. GET /v1/sources/summary returns workspace-wide KPIs — events_per_day, active_sources / total_sources, and last_ingested_at — over a configurable window (window_days, default 7).
Every figure on the Sources page is computed from stored issue data. A source with no activity in the window shows a zero-filled sparkline, not a synthetic one; metrics that cannot be derived from stored data (like historical parse latency) are simply absent from the response rather than estimated.

​
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
Developers who prefer to manage integrations programmatically can use the Connectors API. All routes require a Bearer token — see Authentication for details.

​
API quick-reference

All API requests are scoped to your workspace. Include your API key as Authorization: Bearer <token>. See API Reference for full endpoint documentation.