Integrations
Bitaic integrations route monitoring alerts, incident signals, API access, and webhook events into the tools operations teams already use. Use this page to choose a launch-supported delivery path, configure the right provider access, and test routing before sending production alerts.
Launch Integration Matrix
| Integration | Status | Workflow | Permission or auth | Typical use |
|---|---|---|---|---|
| Slack | Launch-ready | Alert routing | Authorize the Bitaic app with posting access to selected Slack channels. | Send warning, critical, and recovery alerts to team channels. |
| Microsoft Teams | Launch-ready | Alert routing | Configure a Teams Workflows webhook URL for the destination channel. | Post operational alert cards to Teams channels. |
| Launch-ready | Notification | Verify recipients or group inboxes from Bitaic notification settings. | Route alerts to individual owners or shared operations inboxes. | |
| PagerDuty | Preview | Incident routing | Use a PagerDuty Events API v2 routing key for a service or event orchestration. | Create and resolve preview incidents from Bitaic alert events. |
| API keys | Launch-ready | Automation | Create workspace-scoped service tokens with explicit API scopes. | Read monitoring data or manage configuration from scripts. |
| Webhooks | Launch-ready | Custom routing | Configure an HTTPS receiver, selected events, filters, and signing secret. | Deliver signed monitoring events to internal workflows. |
Slack
Microsoft Teams
Email
PagerDuty
API keys
WebhooksConfigure integrations from a Bitaic role that can manage notification routing, API access, or webhook settings, and complete any provider-side authorization before sending production alerts.
Setup And Test Flow
| Provider | Bitaic setup path | Setup action | Test behavior |
|---|---|---|---|
| Slack | Settings > Integrations > Slack | Authorize the Bitaic app, choose the destination channel, then attach the integration to alert policies. | Post a sample Bitaic alert card to the selected channel. |
| Microsoft Teams | Settings > Integrations > Microsoft Teams | Create or choose a Teams Workflows webhook URL, add a workflow co-owner, then save the URL in Bitaic. | Post a sample alert card to the configured Teams workflow. |
Settings > Notifications | Add recipients or group inboxes, verify external addresses, then apply severity and product routing. | Send a sample alert email without opening a production alert. | |
| PagerDuty | Settings > Integrations > PagerDuty | Add an Events API v2 routing key, map Bitaic severities to PagerDuty severities, and keep escalation policy management in PagerDuty. | Send a preview test event with a non-production summary and dedup key. |
| API keys | Settings > API Keys | Create a workspace-scoped token with the narrowest scopes needed by the automation. | Run a scoped API request and log the returned request ID. |
| Webhooks | Settings > Integrations > Webhooks | Add an HTTPS receiver URL, select events, configure filters, and store the signing secret. | Send a signed webhook.test delivery to the receiver. |
Provider Notes
- For Slack, private channels require the channel owner to add or authorize the Bitaic app before alerts can be posted there.
- For Microsoft Teams, use a Teams Workflows webhook URL for new channel delivery. Legacy Microsoft 365 connector URLs are migration-only and should not be the setup path for new launch customers.
- For PagerDuty preview routing, use the Bitaic alert ID as the
dedup_key, sendtriggerwhen an alert opens, and sendresolvewhen the alert recovers or resolves.
Routing And Filtering
Default notification routing sends warning and critical alert openings plus recovery or resolution events for those alerts. Add filters when a provider should receive only a subset of product, service, team, or monitored-resource events.
| Filter | Applies to | Notes |
|---|---|---|
severity | Slack, Microsoft Teams, email, PagerDuty preview, webhooks | Use for warning, critical, and recovery routing. |
product | Slack, Microsoft Teams, email, PagerDuty preview, webhooks | Route SSL, Endpoint, Domain, DNS, Health, or Windows events differently. |
target_id or check_id | Slack, Microsoft Teams, email, PagerDuty preview, webhooks | Scope delivery to specific monitored resources or checks. |
label | Slack, Microsoft Teams, email, PagerDuty preview, webhooks | Use labels such as environment, service, region, or owner. |
team | Slack, Microsoft Teams, email, webhooks | Route alerts to the owning team when the alert policy has team metadata. |
service | PagerDuty preview, webhooks | Map Bitaic service metadata to the destination service where supported. |
state | Slack, Microsoft Teams, email, PagerDuty preview, webhooks | Send opening, update, recovery, or resolved notifications. |
API keys are an automation path, not a notification destination. Use API token scopes and list filters when automation needs to read or update monitoring resources.
API And Webhooks
Bitaic's API and Webhooks enable custom automation, signed event delivery, and integration management. Use the API and Webhooks reference for authentication, workspace-scoped paths, response shapes, token scopes, webhook events, signing headers, retries, and delivery history.
Bitaic API
- Bitaic's REST API provides programmatic access to metrics, alerts, monitored targets, checks, agents, integrations, webhook subscriptions, and exports under
/v1/workspaces/{workspace_id}. - Authenticate API requests with workspace-scoped bearer tokens created in Settings > API Keys.
- API responses include resource data, pagination metadata where applicable, token-scope enforcement, and a request ID for support and audit review.
Webhooks
- Use webhooks to send event data to external systems when alerts, checks, agents, or monitored resources change state.
- Under Settings > Integrations > Webhooks, configure webhook URLs, selected triggering events, alert filters, and signing-secret rotation.
- Security: Verify Bitaic webhook signatures against the raw request body, reject deliveries older than five minutes, and use event IDs to prevent duplicate processing.
Failure Handling
| Provider | Handling |
|---|---|
| Slack | Record failed posts, prompt for reauthorization when channel access is removed, and allow channel remapping. |
| Microsoft Teams | Record failed workflow deliveries and prompt for webhook replacement when the workflow is disabled or orphaned. |
| Suppress hard-bouncing recipients, show delivery failures, and require verification before external recipients receive alerts. | |
| PagerDuty | Record PagerDuty response details and keep preview routing disabled until the service mapping and routing key are valid. |
| API keys | Rotate or revoke compromised tokens and record administrative actions in the audit trail. |
| Webhooks | Use webhook delivery records, retries, disabled-endpoint handling, and secret rotation from the webhook contract. |
Security And Data
Send only the alert context your response workflow needs, restrict API tokens to the least privilege available, rotate credentials when owners change, and verify webhook signatures before trusting incoming event data.