Integrations

Brekfuz connects to the tools your team already uses

No new workflow required. Brekfuz reads knowledge signals from your existing communication, documentation, and project management tools using read-only access.

Available integrations

Six integrations, read-only, zero-friction setup

Brekfuz uses only read-only access scopes. It never posts, writes, or modifies data in any connected tool.

Slack

All tiers

Communication patterns

Brekfuz reads channel activity metadata and message patterns to determine which people are active in which knowledge domains. It does not read message content.

  • Channel membership
  • Message frequency per channel (counts, not content)
  • Thread participation patterns

Confluence

Intelligence + Enterprise

Documentation contributions

Tracks which team members create, edit, and maintain which spaces and pages. Page ownership and edit history become knowledge ownership signals in the graph.

  • Page authorship and edit history
  • Space membership by user
  • Document freshness signals

Jira

Intelligence + Enterprise

Task ownership patterns

Maps which team members own and contribute to which projects, epics, and issue types. Ticket assignment history shows who handles which process areas over time.

  • Ticket assignment history
  • Project and epic ownership
  • Resolution and review patterns

GitHub

Intelligence + Enterprise

Code ownership signals

Reads repository contribution history to understand which engineers own which codebases, services, and modules. PR reviews indicate cross-domain knowledge adjacency.

  • Commit authorship by file path
  • Pull request review patterns
  • Repository ownership signals

Notion

Intelligence + Enterprise

Documentation contributions

Similar to Confluence: tracks page authorship and editing patterns. For teams using Notion as their primary knowledge base, Brekfuz maps knowledge ownership through creation and edit activity.

  • Page creation and edit history
  • Database record ownership
  • Workspace activity by user

Linear

Intelligence + Enterprise

Task ownership patterns

For engineering teams using Linear instead of Jira. Reads issue assignment and project membership data to understand knowledge ownership across feature areas and cycles.

  • Issue assignment history
  • Project and cycle ownership
  • Team membership signals

For custom data sources

REST API and webhooks for Intelligence and Enterprise tiers

If your team uses proprietary tools, internal wikis, or custom project management systems, the Brekfuz API lets you push knowledge signals directly from any data source. Intelligence and Enterprise customers get full API and webhook access included.

  • REST API for pushing activity events
  • Webhook endpoints for real-time signal ingestion
  • Event schema for custom tool integration
  • API keys scoped by integration per organization
  • Rate limits: 5,000 events/hour per key (Intelligence), unlimited (Enterprise)
Talk to the team about custom integrations
# POST a knowledge activity event
POST https://api.inbrekfuz.com/v1/events
Authorization: Bearer <api_key>
Content-Type: application/json

{
  "actor_id":    "user_42",
  "domain":     "payment-reconciliation",
  "event_type": "document_edit",
  "source":     "internal-wiki",
  "ts":         1748822400
}

# Response
{
  "status": "accepted",
  "event_id": "evt_01JNZ7K9"
}

Connect your stack

See Brekfuz read your team's tools in a 30-minute demo

We will connect to a read-only sample of your Slack and one other tool, and show you the knowledge ownership signals Brekfuz surfaces within the demo session.