API & automation
Integrations
Connect Slack, Teams, PagerDuty, Datadog and five more, and org events fan out to them automatically — no glue code.
Integrations are managed providers that receive your org events. Connect one and the same event bus that powers webhooks fans out to it — no endpoint or signature handling on your side.
Connect a provider
Section titled “Connect a provider”From the Integrations page, or:
curl -X POST https://cloud.backlex.com/api/org/<org>/integrations \ -H "Authorization: Bearer pak_..." \ -H "Content-Type: application/json" \ -d '{"kind":"slack","config":{"webhookUrl":"https://hooks.slack.com/services/..."}}'Supported providers
Section titled “Supported providers”| Provider | config | What it does |
|---|---|---|
slack | webhookUrl (incoming webhook) | Posts a formatted message per event |
discord | webhookUrl | Posts a formatted message per event |
teams | webhookUrl (incoming webhook) | Posts to a Microsoft Teams channel |
telegram | botToken + chatId | Sends the event to a chat through your bot |
datadog | apiKey (+ optional site, e.g. datadoghq.eu) | Sends events to your Datadog dashboard |
sentry | dsn | Reports provisioning failures and alerts as Sentry events |
pagerduty | routingKey (Events API v2) | Triggers an incident — payment failures, quota thresholds |
opsgenie | apiKey (+ optional region: us or eu) | Opens an alert and routes it on-call |
github | token (repo scope) + repo | Fires a repository_dispatch you can hook in Actions |
Secret fields (webhookUrl, botToken, apiKey, dsn, routingKey, token) are encrypted at rest and returned masked.
Manage
Section titled “Manage”Disconnect from the UI or DELETE /api/org/<org>/integrations/<id>. Everything is also available via the MCP integrations.* tools. Connecting and disconnecting requires the admin role.