> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nylon.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Telegram and Slack

> Two networks where a chat or channel is the thing you connect, not an account.

Most networks connect an account and you post as that account. Telegram and Slack connect a **place** — one chat, one channel — and Nylon posts into it as an app. Connecting a second channel means connecting again.

## Telegram

Telegram has no permission screen, because a bot cannot be told about a chat from outside. It has to be added to the chat, and somebody has to speak to it.

<Steps>
  <Step title="Start the connection in Nylon">
    In **Connections**, choose **Telegram**. Nylon shows the bot to add and a one-line command to send. The command is good for 15 minutes.
  </Step>

  <Step title="Add the bot to your chat">
    In Telegram, add Nylon's bot to the channel, group or chat you want to connect. Make it an **admin** — without that it cannot post.
  </Step>

  <Step title="Send the command in that chat">
    Paste the `/connect …` command as a message there. The bot replies to confirm, and the chat appears in your connections.
  </Step>
</Steps>

<Note>
  Every Nylon connection posts through the same bot, so there is no token to store and nothing to reconnect when credentials change. Posts and replies appear as the bot, not as a person.
</Note>

Telegram is also the network the [inbox](/inbox) is live on. Messages sent in a connected chat arrive there from the moment it is connected — there is no history, because Telegram does not offer a bot anything that happened before it joined.

<Warning>
  In a group, a reply you send from the inbox is visible to everyone in that group. Only a direct chat is private.
</Warning>

## Slack

Slack uses an ordinary OAuth redirect, but with one difference worth knowing: you pick the channel on **Slack's** screen, not in Nylon.

<Steps>
  <Step title="Choose Slack in Nylon">
    In **Connections**, choose **Slack**. Nylon sends you to Slack to approve the install.
  </Step>

  <Step title="Pick a workspace and channel">
    Slack asks which workspace to install into and which channel posts should go to. That channel becomes the connection.
  </Step>

  <Step title="Repeat for more channels">
    One connection is one channel. To post into a second channel, connect Slack again and pick that one.
  </Step>
</Steps>

<Note>
  Install into a single workspace rather than org-wide. An org-wide install belongs to no one workspace, so there is no channel for Nylon to attribute a post to, and the connection is refused.
</Note>

For a private channel, invite the Nylon app into it first — Slack will not let an app post to, or upload into, a private channel it is not a member of.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.