Skip to main content
Monitoring integrations work by sending alerts to CauseFlow via webhooks. When an alert arrives, CauseFlow immediately runs triage and — depending on severity — dispatches specialized agents to investigate.

​
Webhook endpoint

All monitoring integrations use the same base URL pattern: 
POST https://api.causeflow.ai/v1/webhooks/:tenantId/:provider
Replace :tenantId with your tenant ID (found in Settings > General) and :provider with the provider name for your tool.

​
Authentication

Every webhook request must include two headers:
HeaderDescription
X-API-KeyYour CauseFlow API key, created in Settings > API Keys
X-Webhook-SignatureHMAC-SHA256 signature of the raw request body, signed with your webhook secret
CauseFlow verifies both headers on every request. Requests missing either header are rejected with 401 Unauthorized.

​
General setup steps

1

Create an API key

Go to Settings > API Keys and click Create key. Give it a descriptive name (for example, “Datadog webhook”). Copy the key — it will not be shown again.
2

Note your webhook secret

When you create the API key, CauseFlow also generates a webhook secret used for HMAC signature verification. Copy this too.
3

Configure the webhook in your monitoring tool

Use the webhook URL for your provider and add the required headers. See the provider-specific sections below for exact instructions.
4

Test the connection

Send a test alert from your monitoring tool. You should see the incoming event appear in Dashboard > Incidents within a few seconds.

​
Deduplication

If your monitoring tool sends duplicate alerts for the same firing condition, CauseFlow deduplicates them using the sourceAlertId field in the payload. Duplicate alerts return 409 Conflict — the original incident remains open and is not duplicated.

​
Provider setup

Webhook URL: https://api.causeflow.ai/v1/webhooks/:tenantId/datadogSetup steps:
  1. In Datadog, go to Integrations > Webhooks and click New.
  2. Set the URL to your CauseFlow Datadog webhook URL.
  3. Under Custom Headers, add:
    • X-API-Key: your CauseFlow API key
    • X-Webhook-Signature: leave this blank — see the note below on Datadog’s signature approach
  4. Under Payload, use the default JSON template (CauseFlow accepts the standard Datadog format).
  5. Save and test the webhook from any active monitor.
Example Datadog payload:
{
  "alert_id": "12345678",
  "title": "High error rate on payment-service",
  "text": "Error rate exceeded 5% threshold for 5 minutes.",
  "alert_type": "error",
  "priority": "P1",
  "tags": "env:production,service:payment-service,team:platform"
}
Datadog does not natively sign webhook payloads with HMAC-SHA256. For Datadog, include only the X-API-Key header. Contact support@causeflow.ai if you need signature verification for Datadog.
Webhook URL: https://api.causeflow.ai/v1/webhooks/:tenantId/grafanaSetup steps:
  1. In Grafana, go to Alerting > Contact points and click Add contact point.
  2. Select Webhook as the contact point type.
  3. Set the URL to your CauseFlow Grafana webhook URL.
  4. Under Optional Webhook settings, add the HTTP headers:
    • X-API-Key: your CauseFlow API key
    • X-Webhook-Signature: your HMAC-SHA256 signature (compute from the payload)
  5. Click Test to send a test notification.
  6. Add the contact point to an alert rule via a notification policy.
If you use Grafana OnCall, you can route escalations through CauseFlow by adding the webhook as an outgoing webhook in your OnCall integration settings.
Webhook URL: https://api.causeflow.ai/v1/webhooks/:tenantId/cloudwatchCauseFlow receives CloudWatch alarms via Amazon SNS HTTP subscriptions.Setup steps:
  1. In AWS, create an SNS topic (or use an existing one connected to your CloudWatch alarms).
  2. Create an HTTPS subscription on the topic with the endpoint set to your CauseFlow CloudWatch webhook URL.
  3. CauseFlow automatically confirms the SNS subscription when the confirmation request arrives.
  4. Add your X-API-Key header by using an SNS delivery policy or an API Gateway proxy in front of the SNS subscription if direct header injection is needed.
SNS HTTPS subscriptions do not support custom headers natively. For production use, deploy a lightweight AWS Lambda function or API Gateway as a proxy that adds the X-API-Key header before forwarding to CauseFlow. See our sample Lambda template for a ready-to-deploy option.
Webhook URL: https://api.causeflow.ai/v1/webhooks/:tenantId/sentrySetup steps:
  1. In Sentry, go to Settings > Integrations > WebHooks for your organization.
  2. Click Add to Project and select the project you want to monitor.
  3. Set the Callback URL to your CauseFlow Sentry webhook URL.
  4. Under Request Headers, add:
    • X-API-Key: your CauseFlow API key
    • X-Webhook-Signature: your HMAC-SHA256 signature
  5. Select which events to send: at minimum enable Issue events.
  6. Click Save Changes and then Test Plugin to verify.
To reduce noise, configure Sentry alert rules to only send events above a certain frequency threshold before forwarding to CauseFlow.