Skip to main content

Workspace Integrations

Workspace integrations connect Harmony to organisation-level systems such as CRMs, telephony platforms, contact centres, and support systems. They are managed by workspace admins and are shared across the workspace.

Where to find them​

  1. Open Marketplace in the sidebar.
  2. Use the Apps tab to browse and connect new integrations.
  3. Use the Installed tab to see and manage integrations that are already connected.

The older Workspace Settings → Integrations route still works but redirects to the Marketplace surfaces today (/integrations → /marketplace/installed, /integrations/{provider} → /marketplace/apps/{provider}).

Workspace vs personal integrations​

Each integration has a scope — workspace or personal. The Apps tab shows both, with the right action / badge per tile. The scope is a property of the integration provider, not a setting you choose.

Workspace and personal integrations differ mainly in their scope, who manages them, and the kind of systems they connect to Harmony.

Workspace integrations are organization-wide connections to key business platforms. Common examples include major CRMs such as HubSpot and Salesforce, telephony and call center platforms like Talkdesk, Aircall, and Dialpad, and support or communication systems such as Intercom. These integrations are centrally managed and configured by workspace administrators—typically, only those assigned the Admin role have the necessary permissions to view and connect or disconnect these integrations. Access is governed by the integrations:read:all permission for viewing and the integrations:write:all permission for installing or removing integrations at the workspace level. This setup ensures that sensitive data connections and sync configurations remain under the control of trusted organizational leads, safeguarding both security and data consistency.

Personal integrations, on the other hand, are tailored to individual users. Each person connects their own accounts to services like Google Calendar, Google Contacts, Linear, Todoist, Notion, Gmail, or Slack, and they do not need special workspace-level permissions to do so. This allows users to bring their individual productivity tools and communication channels into Harmony, powering features like calendar syncing, task management, email drafting, or connecting to app-specific tools used by Companion. Each user's integration operates independently, and access is limited to their connected account without affecting the broader workspace or requiring administrator approval.

A special note about Slack: in Harmony, Slack functions strictly as a personal integration, not a workspace-wide sync. Each user individually connects their Slack workspace, which makes Slack-powered tools available to Companion—such as reading channels, sending messages, or looking up users. However, linking Slack in this way does not result in the import of Slack messages or users into Harmony’s main records or conversations, nor does it enable organization-wide Slack data sync. Slack’s integration scope is entirely personal and focused on tool access for the individual user through Companion.

If you are looking for more detail on how personal integrations work and what tools are supported, see the Personal integrations documentation.

When considering which types of systems are generally connected as workspace integrations, most organizations use them for three major categories:

First, there are major CRM platforms such as HubSpot, Salesforce, Pipedrive, and Attio, which become central sources of truth for customer and contact data within Harmony.

Second, there are telephony or call platform integrations—including services like Talkdesk, OpenPhone, Aircall, Dialpad, JustCall, and Ringostat—which connect your workspace to real-time call data, recordings, and telephony workflows.

Lastly, the communication and support integrations help organizations connect products like Intercom, Zendesk, Chatwoot, and conferencing solutions such as Zoom (used by the Companion Bot to join and transcribe meetings).

Some integrations may appear in the Marketplace as “Coming Soon” before their full feature set is available. While you can see these tiles, they can’t be connected yet, and clicking them provides more information on what’s coming.

Overall, workspace integrations provide the shared, organization-level foundation for Harmony’s connection to business-critical systems, while personal integrations empower each user to bring in and use their own productivity tools independently.

Some apps appear in the catalog as Coming Soon before full sync is available. Coming-soon tiles cannot be connected; clicking them shows a placeholder.

Microsoft Teams: Coming Soon for the integration, supported for recording​

Microsoft Teams support today is limited to meeting recording via the Companion Bot — the same path Zoom and Google Meet use. The Companion Bot can join scheduled Teams meetings as a participant for transcription, action items, and insights.

There is no first-party Microsoft Teams chat or messaging integration today. Microsoft Teams is listed under Communication → Coming Soon in the Marketplace, which means:

  • You cannot read or send Teams chat messages, list channels, or search Teams content from Companion.
  • You cannot connect Teams as an OAuth integration on the Apps tab.
  • You cannot post alerts or summaries to Teams channels.

There is also no native Microsoft 365 / Outlook calendar integration today. If your Teams meetings live only on an Outlook calendar, the Companion Bot cannot pick them up automatically through auto-join. Either move the events to Google Calendar (the supported calendar source) or send the bot manually with Remote in Quick Launch.

Connect a workspace integration​

  1. Open Marketplace → Apps.
  2. Find the integration and click the tile to open its detail page.
  3. Review what the integration provides, the permissions it needs, and the auth method (OAuth, API key, enterprise OAuth credentials, instance URL, region, or private app token, depending on the provider).
  4. Follow the provider's connect flow (for OAuth, this opens the provider's consent screen).
  5. Once authorised, the integration appears under the Installed tab.

Workspace-scope connect / disconnect requires the integrations:write:all permission. Without it, Connect / Manage / Disconnect actions are not available. See Roles and Permissions.

Manage an active integration​

Open Marketplace → Installed and click the tile (or open the integration from the Apps tab). The manage page exposes the actions the provider supports — typical examples include:

  • Re-authenticate.
  • Trigger a sync.
  • Configure object or field mappings (where supported).
  • Switch environments (sandbox / production) where supported.
  • Disconnect the integration.

Per-row controls and labels vary per provider — only the actions a provider actually supports are shown.

Sync behaviour​

Workspace integrations can sync data in different directions, depending on what the provider supports:

  • Inbound only — pulls provider data into Harmony.
  • Outbound only — pushes Harmony data to the provider.
  • Bidirectional — keeps mapped fields updated in both systems.

For CRMs that support mappings, admins can decide how provider objects map to Harmony objects and which fields sync in each direction.

Example: Talkdesk​

Talkdesk is a workspace telephony integration. Depending on your setup, Harmony may ask for enterprise OAuth credentials, an instance URL, or region information before opening the OAuth authorisation flow. Once connected and configured, Talkdesk call recordings can be imported into Harmony for transcription and analysis.