Integrations

Integrations connect BrowserStack AI Evals to external services for notifications, automation, and authentication.

Slack

Connect Slack to receive alert notifications from AI Evals in your Slack channels. The connection is managed at the BrowserStack organisation level — all BrowserStack products in your organisation share a single Slack workspace.

Prerequisites

• Only Owner or Admin project roles can connect or disconnect Slack.

Connecting Slack

Navigate to Settings → Integrations in your project.

One Slack workspace can be connected per BrowserStack organisation. The same connection is shared across AI Evals, Test Observability, Test Case Management, Live, and App Live.

Disconnecting Slack

Click Disconnect on the Slack card. A confirmation dialog opens — type Disconnect in the field and click Disconnect to confirm.

Using Slack for alert notifications

Once connected, Slack becomes available as a Notification Channel option when creating or editing an alert:

1. Open or create an alert.
2. In the Notification Channel dropdown, select Slack.
3. In the Slack Channel field, choose the target channel from the dropdown.
4. Optionally click Send test message to verify delivery before saving.

Zenduty

Zenduty needs no org-level connection on this page — it is configured per alert rule. When creating or editing an alert, pick Zenduty as the Notification Channel and paste your Zenduty Generic Integration URL. See Alerts → Zenduty for the setup walkthrough and payload reference.

Webhooks (API Management)

Webhooks and API management are accessed via Settings → API Management ↗, which opens the dedicated API management section.

From there you can:

• Create webhook endpoints that receive events when traces are ingested, scores are created, or experiments complete
• Configure event filters (which event types trigger the webhook)
• View delivery logs and retry failed deliveries

Supported Events

Payload Format

Webhooks send JSON POST requests to your endpoint with an event envelope:

{
  "type": "trace.created",
  "projectId": "proj_abc123",
  "timestamp": "2026-04-03T12:00:00.000Z",
  "data": {
    "traceId": "...",
    "name": "...",
    "userId": "..."
  }
}

Verify authenticity using the X-BrowserStack-Signature header (HMAC-SHA256 of the raw body using your webhook secret).

SSO / SCIM

SSO and SCIM configuration is managed at the organization level in your BrowserStack account, not in project settings.

Supported SSO Providers

• SAML 2.0 — compatible with Okta, Azure AD, Google Workspace, and other SAML providers
• OIDC — compatible with Auth0, Okta, and other OpenID Connect providers

SCIM Provisioning

Enable SCIM to automatically provision and deprovision users from your identity provider:

• New users in your IdP are automatically invited to BrowserStack
• Removing a user in your IdP immediately revokes their access
• Group memberships in your IdP can map to BrowserStack organization roles

Contact your BrowserStack account team or see the BrowserStack organization documentation to configure SSO/SCIM.

Permissions