---
title: "Troubleshooting: Integrations - In Parallel help"
description: "Solutions for calendar, Recorder, Slack, Teams, Zoom, and MCP connection issues."
url: https://www.in-parallel.com/help/troubleshooting-integrations
---

# Troubleshooting: Integrations

Solutions for calendar, Recorder, Slack, Teams, Zoom, and MCP connection issues.

Updated 9 August 2026

On this page

Troubleshooting & FAQ

## A calendar is connected but the Recorder does not join

A calendar connection makes meetings available to In Parallel; automatic joining is controlled separately.

Open **Settings → Account → Recorder** and review **Automatic joining** for internal and external meetings. Then open the individual meeting and confirm that **Recorder joining** is on. This per-meeting toggle controls whether the Recorder joins regardless of Workspace linkage; linking determines whether the meeting contributes to that Workspace’s shared context, while an unlinked meeting can still produce a meeting summary. If it is a Zoom meeting, also confirm that Zoom is connected.

## The wrong calendar account is connected

Under **Calendar**, select **Disconnect** for the incorrect provider or account, then connect the calendar that contains your work meetings. Disconnecting can affect future meeting capture, so check upcoming meetings afterward.

## A connected calendar or Slack account shows Update available

Select **Update available** and complete the provider’s authorization flow. This adds newly required permission scopes without removing the healthy connection first. Slack may separately show **Update notifications** for the personal notification connection.

The update action does not detect every revoked or expired token. If the connection still fails and no update appears, disconnect and reconnect it after checking the impact. See [Update calendar and Slack permissions](https://www.in-parallel.com/help/update-integration-permissions).

## Slack is installed but I receive no notifications

The Slack app installation and your personal notification authorization are separate steps. In **Settings → Account → Connections**, find Slack and select **Connect notifications**. If the app is not installed, ask a Slack administrator to install it first.

## Teams notifications are missing

Check whether the Microsoft Teams integration shows **Personal notifications enabled**. Follow the integration’s reinstall or uninstall instructions if the personal app connection is not working. Also review **Settings → Account → Notifications** for the event types you expect.

## The Teams app does not reply to connect

The In Parallel chat can look normal in Teams while `connect` gets no reply. Other messages may still get a response. In one observed case, Teams rejected the sign-in card with a `403` response saying `User blocked the conversation with the bot.` even though the conversation did not appear blocked in the user’s Teams client.

1. In Teams, open the In Parallel personal chat. If its menu offers **Block** , block the conversation.
2. Open the same chat’s menu and choose **Unblock** .
3. Send `connect` again and complete the sign-in card if it appears.

Blocking and then unblocking restored the connection in that case. The cause has not been confirmed, so if `connect` still gets no reply or those menu options are unavailable, contact In Parallel support. Tell them that `connect` is silent while the chat looks unblocked, and whether other messages receive replies.

## External Zoom meetings are not recorded

Under **Zoom**, select **Connect** and authorize the integration. Also review the external-meeting Recorder switch and confirm that the meeting host allowed the Recorder to join.

## An MCP-connected AI client cannot see a Workspace

1. Confirm that you can open the Workspace in In Parallel.
2. Recheck the client-specific setup under **MCP connectors** .
3. Reauthorize the connection if the token or session has expired. On the OAuth consent screen, select the missing Workspace and click **Allow access** .
4. Start a fresh client conversation and request the Workspace explicitly.

MCP does not bypass In Parallel permissions. A missing Workspace may be an access issue rather than a connector failure.

## Send to AI opens the wrong client

Under **Settings → Account → Connections → AI assistants**, select **Use [assistant] for Send to AI** for the destination you want. Clear the selected assistant to be asked each time. Use **Setup instructions** separately to configure and verify live context access.

## Still stuck?

Contact the In Parallel support team with the integration name, the status shown on screen, and the last step that succeeded. Do not send access tokens or authorization codes.

## Related

- Connect your calendar, notifications, and AI tools
- [Integrations overview](https://www.in-parallel.com/help/connect-your-tools-integrations-overview)
- [Connect a meeting to a Workspace](https://www.in-parallel.com/help/connect-a-recurring-meeting-meeting-transcriber)
- [Connect your AI tool to In Parallel](https://www.in-parallel.com/help/connect-your-ai-tool-mcp)
- [Update calendar and Slack permissions](https://www.in-parallel.com/help/update-integration-permissions)
- [Use the In Parallel app in Microsoft Teams](https://www.in-parallel.com/help/use-in-parallel-app-in-microsoft-teams)

[All help articles](https://www.in-parallel.com/help)