Troubleshooting
Discord Webhook Keeps Posting and You Can't Find It to Remove
A webhook still posts because it lives in a channel's integration settings, not in the chat log itself.
Is this your situation?
A webhook keeps posting into a channel and you cannot see where it is coming from. A webhook is made by opening Server Settings and going to the Integrations tab.
The short answer
Discord's built in webhooks function as a way to get automated messages and data updates sent to a text channel. To find it, open Server Settings and go to the Integrations tab. A webhook can be named to help distinguish multiple webhooks for multiple different services.
What you see, and why
| Symptom | Cause |
|---|---|
| Messages keep appearing in a channel with no matching user in the member list. | Discord's built in webhooks function as a way to get automated messages and data updates sent to a text channel. |
| You cannot find the sender by scrolling the chat log. | A webhook is made by opening Server Settings and going to the Integrations tab. |
| Several webhooks post into the same channel and you cannot tell which one is which. | A webhook can be named to help distinguish multiple webhooks for multiple different services. |
Check these first
- Check which channel the messages are posting to. Webhooks send automated messages and data updates to a text channel.Verify: Note the channel name shown above each posted message.
- Check Server Settings for the Integrations tab. A webhook is made by opening Server Settings and going to the Integrations tab.Verify: Look under Server Settings for Integrations.
- Check the webhook's assigned channel in the dropdown. The channel a webhook posts to is chosen from a dropdown menu.Verify: Compare the dropdown selection to the channel receiving the messages.
How Discord handles this
- Discord's built in webhooks function as a way to get automated messages and data updates sent to a text channel in a server.
- Webhooks require another website to use.
- Services such as GitHub can use webhooks.
- Webhooks cannot function on their own and need to be linked to another website to function as intended.
Which path applies to you?
- Do you know which channel the messages appear in? Open Server Settings and go to the Integrations tab.
- Do you see multiple webhooks listed there? A webhook can be named to help distinguish multiple webhooks for multiple different services.
- Do you need the channel it posts to? The channel a webhook posts to is chosen by selecting the desired text channel in a dropdown menu.
- Do you need the webhook URL? The webhook URL for a server or channel can be obtained by pressing the Copy Webhook URL button.
Step by step: finding the cause
- Open Server Settings. Access the server's settings menu to reach Integrations.Confirm: Check for a tab labeled Integrations in the settings menu.
- Go to the Integrations tab. A webhook is made by opening Server Settings and going to the Integrations tab.Where: Server Settings → IntegrationsConfirm: Check the Integrations tab for a list of existing webhooks.
- Review the list of webhooks. A webhook can be named to help distinguish multiple webhooks for multiple different services.Confirm: Check each webhook's name against the service you expect it to belong to.
- Check the posting channel. The channel a webhook posts to is chosen by selecting the desired text channel in a dropdown menu.Confirm: Check that the dropdown channel matches where messages are appearing.
- Copy the webhook URL if needed. The webhook URL for a server or channel can be obtained by pressing the Copy Webhook URL button.Confirm: Check that the URL copies to your clipboard.
- Check any connected external service. You can get the webhook URL for a server or channel by pressing the Copy Webhook URL button.Confirm: Check the external service's settings for the matching webhook URL.
- Remove the webhook. To make a webhook, open Server Settings and go to the Integrations tab.Confirm: Check the Integrations tab to see that the webhook no longer appears.
Common mistakes
- Looking in the chat log instead of Integrations. A webhook is made by opening Server Settings and going to the Integrations tab.Why it happens: The posted messages look like chat messages, not settings entries.
- Assuming an unnamed webhook has no source. A webhook can be named to help distinguish multiple webhooks for multiple different services.Why it happens: A webhook left unnamed gives no visible clue to its origin.
- Deleting the webhook but not the external connection. Webhooks require another website to use.Why it happens: The URL remains saved in the external service even after removal in Discord.
Quick reference
| Task | Where it happens |
|---|---|
| Create a webhook | Server Settings → Integrations |
| Name a webhook | Not stated by Discord |
| Choose posting channel | Dropdown menu in webhook settings |
| Copy webhook URL | Copy Webhook URL button |
| Services that can use webhooks | GitHub |
| Services that can't really use webhooks | Twitch and YouTube |
| Requirement to function | Must be linked to another website |
Keeping track of who has access
Delvia keeps a record of server integrations so a posting webhook is never a mystery you have already diagnosed too late.
Was this helpful?