Changelog
Back to All
Fixed

Slack Integration Supports Direct-Source Data Products

4 months ago

Slack workspace mapping responses now include routing metadata for direct-source data products that do not have an external workspace ID. This lets Slack integrations route to BigQuery, PostgreSQL, and direct Snowflake data products instead of treating them as misconfigured.

Fixed Behavior

  • Direct-source Slack data-product mappings can return externalWorkspaceId: null
  • providerSlug is populated with the account slug for non-Sledhouse data products
  • webSearchEnabled, chatHistorySearchEnabled, domainAllowlist, dataSourceType, and semanticSourceMode are included so Slack routing can preserve the selected data product's agent context
  • Sledhouse mappings continue to use the configured Bobsled provider slug when available

Modified Endpoint

  • GET /api/v1/accounts/{accountId}/integrations/slack/data-products

Response Example

{
  "ok": true,
  "data": {
    "workspaces": [
      {
        "id": "3f15d2a0-442d-4d69-9631-8ce53303d734",
        "workspaceId": "8b7d58a2-68a8-4f2d-aad6-1c7051de7783",
        "workspaceName": "Usage Analytics",
        "description": "Usage analytics data product",
        "externalWorkspaceId": null,
        "providerSlug": "production",
        "webSearchEnabled": true,
        "chatHistorySearchEnabled": false,
        "domainAllowlist": ["example.com"],
        "dataSourceType": "bigquery",
        "semanticSourceMode": "all",
        "isComposite": false,
        "createdAt": "2026-05-08T12:00:00.000Z"
      }
    ]
  }
}

Migration Notes

Clients should continue to treat externalWorkspaceId as nullable. Use workspaceId as the stable Bobsled data product identifier, and use providerSlug, webSearchEnabled, chatHistorySearchEnabled, domainAllowlist, dataSourceType, and semanticSourceMode for app routing context.