Configuring a Social Connector

This guide uses the YouTube connector as the worked example, because it has the fewest moving parts. Once you have done one connector, the others follow the same shape: choose a source, choose a Discord channel, let the dashboard create the webhook, then tune the optional filters.

What you need

• Manage Webhooks in the Discord channel that will receive the posts.
• The YouTube channel identifier - the channel ID, the handle/name, or the display name.
• A destination channel. A dedicated #youtube-feed channel is easier to manage than a busy general channel.
• The connector module enabled for your role. YouTube is available to everyone by default; Reddit and RSS start manager-only, so authorize your role on the Command Permissions page first if you need one of those.

See Configuring Permissions if you are not sure whether your role can use the module.

Step 1: Prepare the destination channel

Create or pick the Discord channel that will receive the notifications. Make sure GiselleBot has Manage Webhooks there - the dashboard creates and manages the webhook for you, so the bot needs that permission in the channel, not just on the server.

A webhook is what makes the posts look like they come from the YouTube channel (name and avatar) rather than from GiselleBot. You do not need to create the webhook by hand in Discord.

Step 2: Open the connector page

On the dashboard, choose your server and open the YouTube page. The page lists every YouTube feed already linked to a webhook in the server.

If the page is missing, check that the module is enabled for your role on the Command Permissions page.

Step 3: Add a feed

Choose Add New YouTube Feed. The create page asks for:

• YouTube Channel - the channel ID, handle, or display name.
• Destination - Discord Channel (the usual choice) or Webhook URL.

With Discord Channel, pick the destination channel from Step 1 and the dashboard creates and manages the webhook for you. With Webhook URL, paste an existing Discord webhook URL instead - useful when you already have a webhook you want to reuse.

Leave the advanced options at their defaults for the first test, then choose Create Feed. The feed appears in the list and starts monitoring the YouTube channel.

Step 4: Tune the optional settings

Open the feed again if you want to change how posts look or which videos are posted. The most useful options are:

• NSFW handling - censor hides the preview with angle brackets, skip drops age-restricted videos entirely, and only posts only age-restricted videos. The default posts both uncensored.
• Keyword filtering - a comma-separated whitelist applied to video titles. Use Include to post only matching videos, or Exclude to post everything except matching videos.
• Filter match mode - AND requires every filter word, OR requires at least one. The default is OR.
• Custom header message - the text above the video link, with placeholders such as %title%, %channel%, %url% and %timestamp%.
• Custom webhook name - overrides the author name. You can also keep the webhook's own Discord name and avatar instead.

The YouTube Connector reference documents every placeholder and default.

Step 5: Verify it works

The connector checks for new content on its own schedule, so the first post will not appear instantly. Wait for the next upload (or use a channel you know posts regularly), then confirm the post appears in the destination channel with a working preview.

If nothing arrives:

• Confirm the bot still has Manage Webhooks in that channel.
• Confirm the YouTube channel identifier is the one you meant - handles and display names can be similar.
• Check the filter settings. An over-eager Include whitelist is the most common reason a service looks silent.
• Check the fault is not on the source side: the connectors depend on third-party APIs and can be delayed or miss an event occasionally.

Step 6: Edit or remove the feed

Use the same YouTube page to edit or remove the feed. Editing replaces the stored customization options, as noted above. Removing a feed stops monitoring and removes its link to the Discord webhook.

Doing the same for another connector

• Twitch - choose the Twitch account, the destination channel, and optionally filter by game or by live/offline events.
• Reddit - choose the subreddit and destination channel, with optional flair and keyword filters. Reddit checks can be delayed by 5-15 minutes and may miss posts in very busy subreddits.
• RSS - choose the feed URL and destination channel, with optional keyword filters. Feeds are checked periodically and some feeds are simply incompatible with the parser.

Each connector's reference page lists its own filters, placeholders and known limitations. Start there when a source behaves differently from YouTube.