Skip to content
nouter

Managing connectors

The table has one row per connector, with its name, the Type column (Native or MCP), the Authorization column (Individual, if each person connects their own account, or Automatic) and its Category. At the top you can Search, filter by Type or Category, and use Add to add a custom MCP server.

In each row’s ⋮ menu:

  • Turn on or Turn off the connector for everyone.
  • Mode… on automatic connectors: Disabled, Optional (each person adds it) or Enabled (on for everyone automatically).
  • Resource types… to choose what kind of resources the agent can bring in.
  • Set up app… to load your company’s credentials (below). If the connector already works with Nouter’s app, it says Own app….
  • Edit… and Remove on custom MCP servers.

Set up your company’s app

Section titled “Set up your company’s app”

Google, Slack, Salesforce and GitHub use an app your company creates, so the connections are yours and not nouter’s. Until you load it, the row says Needs setup and nobody can connect it. When you save it, it moves to “Setting up…” and in about half a minute to Available to everyone.

Google and GitHub may already be available with Nouter’s app: the row says so, and everyone connects their own account without you loading anything. When you open Own app… you’ll see “Everyone can connect … with Nouter’s app. There’s nothing to set up.”, with the form folded under Use your company’s app. Loading your company’s app is optional and replaces it, but everyone has to connect that connector again.

When you change a connector’s app (you load your company’s, remove it, or change the Client ID), the accounts people had connected stop working. Nobody needs to disconnect them: they disappear on their own the next time each person opens their connectors, and each one connects again.

The Set up app… form shows the Callback URL to paste into the provider’s app: copy it from there. It’s always your workspace’s address, the connector’s path and /oauth:

https://<your workspace's address>/<connector's path>/oauth

Google

Section titled “Google”

In Google Cloud, create an OAuth client (Web application) in a project with the Gmail, Calendar, Drive, Docs and Sheets APIs, with the consent screen set to Internal, and add the callback URL. Paste its Client ID and Client secret.

Slack

Section titled “Slack”

In api.slack.com/apps, create an app, add the callback URL under Redirect URLs and add the user scopes the connector needs. Paste its Client ID and Client secret.

Salesforce

Section titled “Salesforce”

Create an External Client App (Setup → External Client App Manager) with OAuth, the callback URL, the mcp_api and refresh_token scopes, PKCE required and no secret. Paste its Consumer Key. Salesforce takes about 10 minutes to apply the changes.

GitHub

Section titled “GitHub”

If the row says Available to everyone with Nouter’s app, everyone connects their GitHub account and sees the repositories of the organizations where Nouter’s app is installed. To add an organization, install the app from Organization → Git providers (Connect GitHub to your organization). If the app asks for new permissions, the organization’s admin accepts them on GitHub.

To use your company’s app instead, create an OAuth App (Settings → Developer settings → OAuth Apps) with the callback URL and paste its Client ID and a client secret. With it, the connector reaches everything each person can see, without installing anything. An OAuth App accepts a single callback URL.

The secret is stored encrypted and never shown again: the field stays as Loaded and, if you leave it empty, it’s kept. To rotate it, create the new one in the provider, paste it here and only then delete the old one.

When something doesn’t work

Section titled “When something doesn’t work”

If a state or mode change fails, it goes back to the previous state and a notice appears. If a row says “Couldn’t set it up”, save it again to retry. The usual connection problems are in Connection problems.