Skip to main content
Discord
Beta. This integration is available, but how accurately Cogno extracts tasks and context from these messages has not been validated yet. Expect rough edges, and tell us what you see.

At a glance

Connect a Discord server and Cogno reads what your community is already discussing, using it as workspace context and turning actionable messages into Tasks. Agent posting and replies are allowed by default, so Cogno answers when it is mentioned; configure Send to Discord under Agent tools to block them.

Before you start

  • You can open Settings in the target workspace.
  • The Cogno bot is (or can be) added to the Discord server you want to read from.

Connect Discord in Cogno

1

Open the Discord integration

Open Integrations and find Discord.
2

Authorize Discord

Click Connect. Cogno opens Discord’s authorization screen in a new window; approve it and Discord returns you to Cogno.
3

Confirm the connection

The Discord page shows a Connection section for this workspace.

Select a server

1

Open Server

In the Server section, open the Discord server picker. It lists the servers where both you and the Cogno bot are present; if none appear, add the bot to your server and choose Refresh.
2

Choose the server

Pick the server this workspace should read from. The connection row at the top of the page then names it.
The Channels section lists the channels the Cogno bot can see in the selected server. Choosing a different server clears the Discord channel selections for every Project using this connection and removes the previous server’s channels from the Project picker. Until you narrow them again, those Projects read every channel in the new server. Past conversations are kept. Selecting the same server again keeps the existing channel selections.

Choose channels for a Project

Selecting a server decides what Cogno may see at all. A Project reads every channel in it until you narrow the Project to some of them, the same way it works for Slack channels. Once a Project has selected channels, messages from other channels create no Attention or Tasks for that Project.
1

Open the Project's integrations

Open the Project’s settings and find Project integrations. The Discord row names the connected server.
2

Select channels

Under Channels, choose Select and pick the channels this Project should take conversations from. Channels and forums appear after the server is selected, even before anyone posts. Cogno refreshes the list every five minutes to pick up new, renamed, and removed channels.
A thread belongs to the channel it was started in, so selecting a channel includes its threads. Any number of Projects may select the same channel. For a forum channel, select the forum itself. The selection covers its posts and replies; you do not need to create a post before selecting it.

Read conversations from before connecting

Cogno automatically imports the previous 90 days of human-authored messages from the channels your Projects read. This includes accessible active threads, public archived threads, and private archived threads the Cogno bot has joined. The bot needs View Channel and Read Message History permissions. The import starts when Cogno connects to Discord. Newly selected channels are checked every 10 minutes. Messages are saved in batches of 100, with no total message-count limit within the 90-day window. If Discord refuses a request or an import fails, Cogno retries the unfinished import. Imported conversations are available as context; importing them does not create Tasks or send replies to old messages.

Set agent access

On the Discord page, Agent tools controls access for this connection. Read Discord defaults to Allow for stored messages, threads, history, files shared in messages, the Project’s channel list, and looking up the Discord users Cogno has seen. Send to Discord defaults to Allow for posting, replying, and adding or removing the bot’s emoji reactions. Choose Block to prevent an operation, Ask to require your approval during an interactive run, or Allow to let it run without asking. Autonomous runs cannot use tools set to Ask. Chat replies stay short: a post of more than 12 lines is refused and nothing is sent unless the person asked for the full text, so Cogno leads with the conclusion, turns a long list into an image or its top three, and keeps the details in the Task. In Project integrations, each row starts on the workspace setting. A Project can restrict access further but cannot grant more access than the workspace allows. Reading and sending remain limited to the channels the Project reads, and a Project that turned Discord off reads and sends nothing. Agents see the files shared with a message by attachment_id, name, type and size, and discord_read_file reads one of them by its message_id and attachment_id. Text files (plain text, CSV, JSON, XML and similar) and PDFs return their text, and images return the image itself. Text is cut at 20,000 characters, images at 1 MB and PDFs at 5 MB; larger files and other types return their metadata with a note that the content was not read. Cogno asks Discord for the file each time and stores nothing, so the bot needs View Channel and Read Message History in the channel; without them the tool reports that Discord refused the file instead of returning an empty result. Only files attached to stored messages in the channels the current Project reads can be read, including messages imported from before connecting.

Map Discord users to workspace members

Expand Member mapping and choose Sync members to gather the Discord users Cogno has seen in messages, then map each to a Cogno member so authors and mentions resolve to the right person.

Disconnect

Open the ⋯ menu on the connection row and choose Disconnect, then confirm.

Common states

Reference URLs