Connect Slack, Telegram & cloud drives

Bring your knowledge base to the tools you already use. Manage them from Settings in the sidebar: Slack, Telegram and the cloud drives each have a card in the Connected Services section.

If a connection isn't available on your account yet, its card says Not available yet instead of showing a Connect button. 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, paste it into the Bot token box on the Telegram card, and click Connect. Then send /start plus the code shown under the card 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. If you get stuck, the Need help connecting Telegram? link under the card spells out every step.

Slack

Connect Slack to ask questions right from your workspace. Click Connect on the Slack card and approve the connection in Slack, then invite the bot into a channel or send it a direct message, and it answers from your knowledge base. It answers the person who connected it, and it is for questions only: Slack messages are not saved into your knowledge base.

Email Capture

Your knowledge base has its own private email address. Find it in Settings, under Email Capture, and click the copy button next to it. Save it in your contacts so it is easy to pick.

Forward or send an email to that address and it is added to your knowledge base, usually within a minute:

• The email itself becomes a searchable document, titled with its subject.
• Each attached file becomes its own document and is read the same way as an upload: PDF, Word, Excel, CSV, text and Markdown files, images (JPG, PNG, WebP) and audio (MP3, WAV, M4A). Each file can be up to 25MB, with up to 10 files per email.
• Pictures inside the email body, like the logo in a signature, are left out, and so are file types the knowledge base can't read.

Only email from the address you sign in to Noli with, or from the sign-in address of someone on your team, is added. Settings lists the addresses that count. The email also has to really come from that address: your email provider signs what you send, and anything sent from somewhere pretending to be you is not added.

Anything else is not added and nobody is emailed back. Settings shows your recent emails under the address, with what was added and why anything wasn't: sent from an address that isn't yours or your team's, we couldn't confirm it really came from you, or there was nothing we could read. If an email from you shows "we couldn't confirm it really came from you", send it again from your usual email app rather than a script or a forwarding rule.

Cloud drives

Sync content from the places your files already live:

• Google Drive
• Dropbox
• Notion

Click Connect on the card for the service and sign in. For Google Drive, then click Choose files: a picker opens, so you choose exactly which files come across rather than importing your whole account, and you can pick more anytime. 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 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

• Add documents to your knowledge base
• Set up notifications and your weekly digest