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

# Discord

> Connect a Discord application to an assistant

Discord lets you attach an assistant to an application you create in the Discord developer portal. People invite that bot to a server. What the assistant can hear is narrower than a normal chat member: Famulor answers interactions sent to the webhook, not ordinary messages typed in a channel.

## When to use it

Use it when the community already lives on a Discord server and you want the assistant available through that application: a slash command or a button, with the reply posted back by the bot and the thread kept in History. Do not use it if you need the assistant to read every message people type in a channel. That needs a Gateway connection, and Famulor does not keep one open.

## What the assistant hears

With the Interactions Endpoint URL set, Discord sends the connectivity check, slash commands and button clicks to Famulor. Ordinary channel messages and reactions do not arrive. Turning on Message Content Intent does not change that. Discord delivers interactions either to this URL or through the Gateway, not both. Famulor uses the URL.

## Where the keys come from

The linked provider guide shows the screens for these clicks. Follow the clicks below together with those pictures.

Open [discord.com/developers/applications](https://discord.com/developers/applications). **Application ID** and **Public Key** are on **General Information**. The **Bot token** is created under **Bot** with **Reset Token** and shown once. Official guide: [Getting started](https://docs.discord.com/developers/quick-start/getting-started).

## Create it at the provider

1. Open the [Discord developer portal](https://discord.com/developers/applications) and choose **New Application**.
2. On **General Information**, copy the **Application ID** and the **Public Key**.
3. Open **Bot**, choose **Reset Token**, and copy the token. It is shown once.
4. After the Famulor connection exists, paste the webhook into **Interactions Endpoint URL** on **General Information**. Discord sends a check, and Famulor answers it.
5. Open **OAuth2**, then **URL Generator**. Select the scopes `bot` and `applications.commands`. Grant **Send Messages**, **Read Message History**, **Add Reactions** and **Attach Files**.
6. Open the generated URL and invite the bot to the server.

Famulor does not register slash commands for you. A command has to exist on the application before someone can start a conversation with it.

## Connect it in Famulor

Your plan includes this channel. Open **Settings → Channels**, choose the card, name the connection, pick an assistant and save. The shared conversation settings — response delay (default 5 seconds) and inactivity timeout (default 30 minutes) — are described on the [messaging channels](https://docs.famulor.io/channels/messaging.md) page.

On the **Discord** card paste **Bot token**, **Public key** and **Application ID**.

## Point the provider at Famulor

1. Copy the Famulor webhook URL from the connection menu.
2. Paste it into **Interactions Endpoint URL** and save. Discord checks the address.
3. Invite the bot with the URL from the previous section. A slash command or a button that Discord posts to that URL appears in History. A normal channel message does not.

## History

Open [History](https://docs.famulor.io/monitoring/history.md) and filter by **Discord**. The thread, the assistant reply and any analysis appear there. You can pause the assistant and answer manually.

## API, MCP and command line

Create this connection in the dashboard. The public API and the command line cannot pass every value this card asks for, so they cannot finish this setup. The card needs the public key and the application ID, and a public create call does not accept those values.


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