Connect an account

You need the Admin role to connect an account. Open Settings → Connections and click Connect. To connect a tool server for the Assistant without that role, use Assistant → MCP Integrations.

The picker lists only the providers your organization can connect. If a provider you expect is missing, see Providers.

Pick a provider and fill in the Connection name. How you finish depends on the provider.

A connection made here starts with the provider’s usual capability: Notifications for Slack and Jira Cloud; Meetings for Google Workspace and Zoom; Workflows for AWS, Azure, a custom MCP server, and OAuth 2.0; and AI for the assistant tools. Change what it’s used for, and who can use it, afterward under Edit.

Connect through OAuth

Slack, Jira Cloud, Google Workspace, Sentry, and the Google Cloud providers send you to the provider’s own site. Click Connect and approve the access there. KloudMate adds the connection when you’re done.

Zoom works the same way, except that you install the KloudMate app in Zoom instead of approving a consent screen. Install it from a Licensed Zoom account, because every war room meeting is hosted by the account that installed the app.

Microsoft Teams is the exception: a team is connected from Teams. Choosing it opens the steps and a Download app package button. See Microsoft Teams Integration.

The connection records the account you authorized, so you can tell two Slack installs or two Google accounts apart.

Connect with a credential form

AWS, Azure, GitHub, Atlassian, a custom MCP server, and a generic OAuth 2.0 API take their credentials in a form. Fill in the provider’s fields and click Connect.

Where a provider supports more than one method, choose one under Authentication. For example, a custom MCP server offers None, Bearer token, Basic auth, API key, or OAuth.

A custom MCP server with OAuth is saved as Pending first, and then KloudMate opens the server’s own sign-in page. KloudMate finds the server’s sign-in, registers itself as a client, and uses PKCE, so you don’t need a client ID. If the sign-in doesn’t finish, the row stays Pending with an Authorize button beside it.

KloudMate checks the credential as soon as you save. If the check fails, it still saves the connection, so you don’t lose what you typed, and marks it Degraded. Click Edit beside it and fix the values.

Note

The generic OAuth 2.0 provider works with any API that uses OAuth 2.0 and has no provider of its own in KloudMate: you supply the authorize and token URLs, the scopes, and your own client id and secret. With the client-credentials grant it works the moment you save. With the authorization-code grant, KloudMate saves it as Pending first, then sends you to approve it. If the approval doesn’t finish, the row stays Pending with an Authorize button beside it. For a worked example with Google, see Trigger a workflow when a new email is received in Gmail.

Connect from a workflow step or trigger

You don’t have to start in Settings. A workflow step’s connection picker and an app-event trigger’s Account picker both offer New connection, or Connect followed by the app’s name when the app has no connection yet. They open the same form, and the new connection can be used for Workflows straight away.

That matters most for app-event triggers. A Slack account connected from Settings for notifications still appears in a trigger’s Account picker, but it’s flagged Not enabled for workflows until you add Workflows to it under Edit.

Visibility

Every connection is Workspace or Private. A connection that can be used only for AI starts Private. Every other connection starts Workspace.

A Workspace connection belongs to the workspace. Anyone in the workspace can use it, anyone with the Admin role can manage it, and it keeps working when whoever connected it leaves.

Private restricts a connection to its creator. Only a connection whose one capability is AI can be private, so use it for a personal GitHub or Google account that you want the Assistant to use on your behalf and nobody else’s.

A private connection is invisible to everyone else: it’s absent from their list, and they can’t use it even if they know its id.

To make a connection private, set Visibility under Edit. To share a private connection with the workspace, use Share with workspace on its row menu. Only an Admin who created the connection can share it.

Related

• Providers for what each one covers and what a plan includes.
• Manage a connection for editing, reconnecting, and deleting.
• Workflows for binding a connection to a step or a trigger.