Skip to content
← All guidesKnowledge Base

Connect Slack, Telegram & cloud drives

Link Slack and Telegram bots, forward email to your capture address, and sync Google Drive, Dropbox, and Notion into your knowledge base.

Bring your knowledge base to the tools you already use. Manage every connection from Settings in the sidebar.

If a connector isn't set up on your deployment, the section says so rather than failing when you click it. That's expected, not a bug.

Telegram

Connect a Telegram bot to use your knowledge base from your phone. Create a bot with Telegram's @BotFather, copy the token it gives you, and paste it into the Telegram section of Settings. Then send /start plus the code shown in that same section to your bot, within 24 hours. Until you do, the bot refuses every message. Once linked, you can message the bot to ask questions, save notes, and send files, photos or voice messages that get added to your knowledge base.

Slack

Connect Slack to ask questions right from your workspace. Authorize the connection in Settings, then invite the bot into a channel or send it a direct message, and it answers from your knowledge base.

Email Capture

The Email Capture section of Settings gives you a personal address. Forward any email to it and the message becomes a searchable document. Use the copy button next to the address to grab it.

Treat that address like a password. Anyone who has it can add documents to your knowledge base, so don't put it on a public page or in a shared signature.

Cloud drives

Sync content from the places your files already live:

  • Google Drive
  • Dropbox
  • Notion

Connect an account from Settings. Google Drive opens a file picker, so you choose exactly which files come across rather than importing your whole account. Once imported, the content is searchable alongside everything else, no manual uploading required.

Connected drives re-sync automatically once a week, and each connection has a Sync Now button if you don't want to wait.

Keep it organized

Imported and forwarded content behaves like any other document, so you can tag and file it and scope chat to it later.

Next