Overview
ORCA webhooks deliver real-time notifications to your team’s communication channels when important data quality events happen. Configure webhooks to alert your team about quality drops, GDPR detections, new issues, scan failures, and contract violations.Supported platforms
| Platform | Payload format |
|---|---|
| Slack | Block Kit messages |
| Microsoft Teams | Adaptive Cards v1.4 |
Setting up a webhook
Create an incoming webhook in your platform
Slack: Go to your Slack workspace settings, create a new Incoming Webhook, and copy the webhook URL.Microsoft Teams: In your Teams channel, add an Incoming Webhook connector and copy the URL.
Configure the webhook
- Name — a descriptive label (e.g. “Data team alerts”)
- Platform —
slackorteams - Webhook URL — the HTTPS URL from step 1
- Event types — select which events trigger notifications
Event types
Select which events trigger webhook notifications:| Event type | Description |
|---|---|
quality_drop | A dataset’s quality score has decreased |
quality_improved | A dataset’s quality score has improved |
gdpr_detected | GDPR-sensitive data (PII) was detected in an upload |
new_issue | A new data quality issue was found |
scan_failure | A scheduled data source scan failed |
contract_violation | A data contract rule was violated |
quality_drop, gdpr_detected, new_issue, and scan_failure.
Payload format
Slack
ORCA sends Slack messages using Block Kit. Each notification includes a header block with the alert title and a section block with the event details.Microsoft Teams
ORCA sends Teams messages using Adaptive Cards v1.4. Each notification includes a title block and a description block.Failure handling
ORCA tracks consecutive delivery failures for each webhook. If a webhook URL becomes unreachable or returns errors, the failure count increments. You can monitor this in the webhook list view and re-test the connection after fixing the issue.Limits
- Maximum 10 webhooks per organisation
- Webhook test requests have a 10-second timeout
- Webhook URLs are stored securely and displayed masked (only the last 8 characters are visible)
API reference
All webhook management endpoints require admin authentication except listing (any authenticated user). Base path:/api/v1.
| Method | Endpoint | Description | Auth |
|---|---|---|---|
GET | /webhooks | List all webhooks for the org | Any user |
POST | /webhooks | Create a new webhook | Admin |
PATCH | /webhooks/{webhook_id} | Update a webhook | Admin |
DELETE | /webhooks/{webhook_id} | Delete a webhook | Admin |
POST | /webhooks/{webhook_id}/test | Send a test message | Admin |