Causeloop ships a catalog of managed connectors. Each connector handles scheduling, pagination, rate-limiting, and credential refresh automatically. You choose which connectors to enable in Settings → Integrations or via the API.
The catalog below reflects the connectors available in the current release. The full catalog is config-driven and grows with each release — call GET /v1/connector-catalog to see the live list for your instance.
Browsing the catalog via API
# List all available connector types
curl https://api.causeloop.ai/v1/connector-catalog \
-H "Authorization: Bearer $TOKEN"
# Filter by keyword
curl "https://api.causeloop.ai/v1/connector-catalog?q=jira" \
-H "Authorization: Bearer $TOKEN"
# Get a single connector type's full metadata
curl https://api.causeloop.ai/v1/connector-catalog/pagerduty \
-H "Authorization: Bearer $TOKEN"
Each catalog entry includes:
| Field | Description |
|---|
type | Connector type identifier (used in API calls) |
display_name | Human-readable name |
description | What the connector ingests |
category | Grouping (see categories below) |
auth_type | oauth2 or api_key |
oauth | true if the connector uses the OAuth flow |
supports_backfill | true if historical data can be pulled |
supports_incremental | true if incremental syncs are supported |
supports_webhook | true if inbound webhooks are supported |
Catalog by category
Operations & Incident Management
| Connector | Type | Auth | What it ingests |
|---|
| PagerDuty | pagerduty | OAuth 2.0 | Incidents, alerts, escalations |
| Jira | jira | OAuth 2.0 | Issues, bugs, epics, sprint activity |
| GitHub | github | OAuth 2.0 | Issues, pull requests, CI failures |
| ServiceNow | servicenow | API key | ITSM tickets, incidents, change requests |
| Linear | linear | OAuth 2.0 | Issues, cycles, project updates |
| OpsGenie | opsgenie | API key | Alerts, on-call notifications |
| Zendesk | zendesk | OAuth 2.0 | Support tickets, customer issues |
Observability & Error Tracking
| Connector | Type | Auth | What it ingests |
|---|
| Datadog | datadog | API key | Alerts, monitors, metric anomalies |
| Sentry | sentry | OAuth 2.0 | Error events, exceptions, performance issues |
| New Relic | new_relic | API key | Alerts, APM traces, infrastructure events |
| Dynatrace | dynatrace | API key | Problems, anomalies, Smartscape events |
Cloud Infrastructure
| Connector | Type | Auth | What it ingests |
|---|
| AWS | aws | API key | CloudWatch alarms, Config events, GuardDuty findings |
| Azure | azure | API key | Monitor alerts, Sentinel incidents, resource events |
| GCP | gcp | API key | Cloud Monitoring alerts, Security Command Center findings |
Security
| Connector | Type | Auth | What it ingests |
|---|
| Okta | okta | API key | Identity events, policy violations, suspicious logins |
| CrowdStrike | crowdstrike | API key | Detections, incidents, threat intelligence |
| Splunk | splunk | API key | SIEM alerts, notable events |
| Tenable | tenable | API key | Vulnerability scan findings |
Productivity & Collaboration
| Connector | Type | Auth | What it ingests |
|---|
| Slack | slack | OAuth 2.0 | Notifications and digest delivery (outbound) |
| Microsoft Teams | teams | OAuth 2.0 | Notifications and digest delivery (outbound) |
| Confluence | confluence | API key | Page events, knowledge base changes |
| Asana | asana | OAuth 2.0 | Tasks, project activity |
CRM & Customer Experience
| Connector | Type | Auth | What it ingests |
|---|
| Salesforce | salesforce | OAuth 2.0 | Cases, opportunities, account signals |
| HubSpot | hubspot | OAuth 2.0 | Deals, support tickets, contact activity |
| Freshworks | freshworks | API key | Support tickets, CSAT signals |
HR & People
| Connector | Type | Auth | What it ingests |
|---|
| Workday | workday | API key | HR events, workforce changes |
| BambooHR | bamboohr | API key | Employee records, time-off events |
| Greenhouse | greenhouse | API key | Recruiting pipeline events |
| Connector | Type | Auth | What it ingests |
|---|
| Snowflake | snowflake | API key | Query errors, warehouse events |
| Databricks | databricks | API key | Job failures, pipeline errors |
| PostgreSQL | postgresql | API key | Table-level change events (CDC) |
Custom & Generic
| Connector | Type | Auth | What it ingests |
|---|
| Generic REST | generic_rest | API key | Any REST API with configurable field mapping |
| Generic Webhook | generic_webhook | HMAC | Any system that can POST a signed webhook |
| Generic CSV | generic_csv | API key | Scheduled CSV file imports |
| Generic Kafka | generic_kafka | API key | Messages from any Kafka topic |
Don’t see the tool you need? Use the Ingestion API to push records from any source, or build a custom integration using the Ingestion API and webhooks together.
Authentication types
OAuth 2.0 — Connectors marked oauth: true use the authorization-code flow. Causeloop redirects the user to the provider to grant access, exchanges the code for tokens, and refreshes automatically. No credentials are stored in plain text.
API key — Connectors marked oauth: false require a static credential (API key, service account token, or client secret). You supply this when creating the connector. Causeloop encrypts it at rest.
What happens after you connect
Once a connector is active, Causeloop:
- Runs an initial backfill to pull historical data (configurable window)
- Switches to incremental syncs on your chosen schedule (default: every 30 minutes)
- Emits
connector.sync.succeeded or connector.sync.failed events you can subscribe to via outbound webhooks
See Connecting a Source for the step-by-step setup guide.