Skip to main content

Integrations Overview

Integrations in ClarityLoop are either personal or workspace-level.

  • Personal integrations help one person work more smoothly in their own tools.
  • Workspace integrations connect shared systems so the whole workspace benefits.

Choose an integration when it does one of two things well:

  • it reduces friction in a workflow people already use
  • it adds better context to feedback, goals, 1:1s, or reviews

If an integration affects your own calendar, browser, or AI access, it is usually personal. If it connects Slack, engineering systems, HR data, or shared business tools, it is usually workspace-level.

How integrated data is used​

For most work-system integrations, data reaches ClarityLoop in two ways:

  • Automatic work context: supported flows can bring a work item into ClarityLoop together with metadata and collaboration on that item. That context can support recent work views, feedback opportunities, and growth signals.
  • Manual linking: people can explicitly attach a PR, issue, page, task, or deal while writing feedback, preparing a 1:1, responding to a request, or updating a goal.

That distinction matters. Automatic context helps reduce friction and spot patterns. Manual linking keeps a specific conversation tied to the exact example a person wants to use.

Access and privacy​

For engineering, project, and CRM integrations, ClarityLoop is focused on shared work items such as pull requests, issues, pages, tasks, and deals.

  • ClarityLoop does not open-endedly ingest everything from those tools. Automatic capture only works for supported sources your workspace allows.
  • The goal is to ground people conversations in shared work and collaboration on that work, not to create a public activity feed.
  • In ClarityLoop, work-context views are scoped. In practice, that context is available to the person, their manager, and workspace owners.
  • If a work item is attached to feedback, reviews, goals, or another workflow, access to that workflow still follows that workflow's own visibility rules.

Personal integrations​

These are connected by the individual user and affect only their own account or workflow.

Personal

Google

Link your own Google Calendar so ClarityLoop meetings stay in your daily calendar flow.

Personal

Microsoft

Link your own Microsoft Calendar if Outlook is where you manage your day.

Personal

ClarityLoop MCP

Connect AI tools to your personal ClarityLoop context using your own MCP API keys.

Personal

Browser Extension

Capture pages, screenshots, and evidence while you work, then send them into ClarityLoop without switching context.

Workspace integrations​

These are connected once by a workspace owner and support the wider team.

Communication

Slack

Bring feedback, surveys, and recognition closer to where work conversations are already happening.

Engineering

GitHub

Use pull requests as evidence in feedback, goals, and manager conversations.

Engineering

GitLab

Connect merge requests and review work through tokens and webhooks.

Engineering

Bitbucket

Bring PR examples into people conversations when review work matters.

Engineering

Azure DevOps

Use pull requests and work items as context in feedback, goals, and 1:1s.

Projects

Jira

Keep feedback and manager conversations grounded in actual issue work.

Projects

Confluence

Use documents and decision records when the writing itself is part of the contribution.

Projects

Linear

Reference issue work in goals, feedback, and 1:1s without turning ClarityLoop into another tracker.

Projects

Asana

Use task context to make delivery and follow-through conversations more concrete.

Projects

Forecast

Bring Forecast projects, tasks, phases, and time context into ClarityLoop through API access and webhooks.

CRM

HubSpot

Use deals as evidence of customer impact in feedback and manager conversations.

HRIS

HiBob

Keep ClarityLoop membership, titles, managers, and onboarding timing aligned with your HR system of record.

Browser extension and auto-capture​

The browser extension and auto-capture policy work together, but they are different controls:

  • Browser extension is a personal tool each person installs in their own browser.
  • Auto-capture policy is a workspace-level control that decides which connected sources are allowed to auto-capture in the background.

Background auto-capture needs all three of these:

  • the extension is installed
  • the user is signed in
  • the source is allowed by the workspace policy

Manual capture through the extension still works even when background auto-capture is off.

Login and SSO setup are covered in Login Methods and SAML.

Next steps​