Skip to content

Apps and integrations ​

Apps let other tools post into Connectdary, listen to what happens and answer people, each under its own name and with only the access you give it. This page is the admin view: who may install, what apps may read, and how to switch them off.

INFO

Setting up apps, tokens and webhooks is done on the web, under Settings, Integrations. The phone lists apps and lets you read their pages, switch them off and revoke tokens, but doesn't add or set them up. On the Free plan, up to 3 apps can be installed; your own apps, outgoing webhooks, API tokens and MCP need the Team plan.

How apps appear ​

An app joins the workspace as a bot with its own name and icon. Its messages carry an App label, so they are never mistaken for a person's. If a message came through someone's token, it says "via" and the app's name.

An app only reads the conversations it was granted. It never has blanket history. Some apps have no channel yet; you or a member add them to a channel, which shows what they can read and do. Anyone who can read a channel can see which apps are in it and when each last read it.

Who can install ​

Priya wants only admins to add apps for the first month.

  1. Open Settings, Integrations.
  2. Under Who can add apps, choose Admins only. The other choice is Admins and members.

Admins can always add and manage apps. Guests never can and don't see the app directory.

  • If members can't, only admins install and set up apps, webhooks and grants.
  • If members can, they install into channels they own, and see in plain words what the app will read and do before they allow it.
  • An app from a publisher you approved can go into any channel without waiting for an admin. Otherwise members are told only an admin can install it there, with the admins' names.
  • Members can't switch off an app an admin installed, and an installer can't undo an admin's switch.

Changing this appears in the audit log under Apps.

Ways to add an app ​

  • App directory (Settings, App directory). Search by name or category and install in one go, or follow a recipe for a tool such as Sentry. The app's token and signing secret are shown once.
  • Manifest (Settings, Integrations, Install from a manifest). Paste an app's description (up to 16 KB) or give an address to load it from. You see in plain words what it can do before you allow it, then its token is shown once.
  • Sign in with the app. The app sends you to Connectdary to approve. Approving hands it tokens; reusing the one-time code stops the tokens it gave.

Removing an app frees its place on a plan with a limit.

Choosing what an app can read ​

A grant is a conversation or a single topic an app may read. Whoever adds the app chooses, and can remove a grant at any time.

Marco installs a release-notes app and wants it to read only #releases:

  1. Open Settings, Integrations and open the app's page.
  2. Under where it can act, press Add to a channel, choose #releases and read what the app will read and do.
  3. Allow it. To undo, remove the channel from the list. There is an Undo.

A few rules:

  • Nobody can grant a private channel they aren't in.
  • An app that sends events outside Connectdary can't read a DM, unless an admin allows that app with Allow anyway on its page. The choice is recorded in the audit log.
  • Each app's page has a What it read log you can filter by channel and period. Members see only the reads of conversations they are in.

Keeping apps under control ​

On each app's page under Settings, Integrations:

  • Switch an app off with the On switch (it asks first). Its tokens, webhooks, deliveries and live connections stop at once. Buttons and commands stop answering. The app stays installed.
  • Noise budget. Under Posts per channel, give an app a number of posts per day in a channel, for example 20 in #alerts. Posts past it are folded and nobody is notified.
  • Mute. Any member can mute an app for themselves, on every device.
  • App notifications show only the card's text, never buttons.
  • Audit. Installs, token changes and webhook posts appear in the audit log under Apps. See Data and compliance.

Messages from apps ​

Apps can post cards with tables, buttons, selects and forms. When you pick a button, the app receives your choice and has 30 minutes to answer. People who can't read the conversation can't use its buttons.

Apps can also add slash commands such as /deploy staging. The app accepts the command at once and answers later, privately to the person who ran it or in the topic. Built-in commands, like /resolve, work without any app. See Shortcuts and commands.

Mention an app in a message and it hears about it, if it is in that channel.

Tokens ​

  • Bot tokens. Give a token scopes and an expiry, such as 90 days. The secret is shown once. Rotating keeps the old secret working for 24 hours. Scope changes apply on the next request, without a new secret.
  • Personal tokens. A member makes one for a script under Settings, Developer, and can revoke it at any time. No one else, including admins, can see it.
  • Agent tokens. A member makes one for an AI agent. Guests can't. Deactivating a member, or requiring two-factor they haven't set up, stops their agent.

Token creation, rotation and revoking appear in the audit log under Apps.

Set up an integration ​

Step-by-step recipes with copy-and-paste samples: