Skip to main content

​
Overview

Webhook Management is the core feature of Discord Webhook Manager. It allows you to store, organize, and manage your Discord webhooks in a centralized dashboard with automatic validation, metadata detection, and collaboration features.

​
Creating a Webhook

1

Navigate to Webhooks

Go to the Webhooks page from the sidebar menu.
2

Click Create Webhook

Click the “New Webhook” button in the top right corner.
3

Enter Webhook Details

Fill in the webhook information:
​
webhook_url
string
required
Your Discord webhook URL. Must start with https://discord.com/api/webhooks/ or https://discordapp.com/api/webhooks/The system will automatically validate this URL with Discord’s API.
​
name
string
Custom name for your webhook. If left empty, the system will auto-fill this from Discord.
​
avatar_url
string
Custom avatar URL for the webhook. Auto-filled from Discord if not provided.
​
description
string
Optional description to help you remember what this webhook is used for (max 1000 characters).
​
tags
array
Add tags to organize your webhooks (e.g., “announcements”, “moderation”, “logs”).
4

Automatic Validation

When you submit the form, the system:
  • Validates the webhook URL with Discord’s API
  • Auto-fills the webhook name and avatar from Discord if not provided
  • Extracts and stores metadata (guild_id, channel_id)
  • Checks for duplicate webhooks and warns you
If the webhook URL is invalid or no longer exists, you’ll receive an error message.

​
Webhook Dashboard

The webhook dashboard shows all your webhooks with key information:
  • Webhook Name & Avatar: Visual identification of each webhook
  • Description & Tags: Organizational metadata
  • Message Count: Total messages sent through this webhook
  • Last Activity: Recent message activity (last 7 days)
  • Permission Level: Shows if you’re the owner or a collaborator

​
Filtering Webhooks

You can filter webhooks by:
  • Ownership: View only your webhooks or shared webhooks
  • Tags: Filter by specific tags
  • Search: Search by name or description

​
Webhook Details & Statistics

Click on any webhook to view detailed statistics:
  • Total messages sent
  • Success rate
  • Failed messages count
  • Recent activity (last 7 days)
  • Associated templates
  • Scheduled messages

​
Organizing Webhooks

​
Tags System

Tags help you organize webhooks by purpose or category: 
{
  "tags": ["announcements", "production", "critical"]
}
Each tag can be up to 50 characters and you can add multiple tags per webhook.

​
Description Best Practices

Add detailed descriptions to help team members understand:
  • What the webhook is used for
  • Which Discord server/channel it targets
  • When it should be used
  • Any special considerations

​
Sharing & Collaboration

​
Permission Levels

Webhooks can be shared with other users with three permission levels: 
{
  "permission_level": "owner",
  "permissions": [
    "view",
    "edit",
    "send",
    "delete",
    "manage_collaborators"
  ]
}

​
Inviting Collaborators

1

Open Webhook Settings

Navigate to the webhook you want to share and click on “Settings” or “Collaborators”.
2

Send Invitation

Enter the email address of the user you want to invite and select their permission level.The user will receive an email invitation with a unique token.
3

Accept Invitation

The invited user can accept or decline the invitation from their dashboard.Invitations expire after a certain period for security.

​
Managing Collaborators

As the webhook owner, you can:
  • View all current collaborators
  • Change permission levels
  • Remove collaborators
  • Cancel pending invitations
Collaborators can leave shared webhooks at any time from their dashboard.

​
Updating Webhooks

​
Changing the Webhook URL

When you change a webhook URL, the system re-validates it with Discord’s API. If the new URL is invalid, the update will fail.
If the URL changes:
  1. The system validates the new URL
  2. Updates guild_id and channel_id metadata
  3. Auto-fills name and avatar from Discord if they were cleared
  4. All associated templates and scheduled messages are automatically updated

​
Editing Metadata

You can update webhook metadata at any time:
  • Name (max 255 characters)
  • Avatar URL
  • Description (max 1000 characters)
  • Tags (array of strings)
Changes are saved immediately and reflected across all views.

​
Deleting Webhooks

Deleting a webhook is permanent and will:
  • Remove the webhook from your dashboard
  • Delete all message history
  • Remove all collaborator access
  • Delete associated scheduled messages
  • Remove webhook references from templates
This action cannot be undone!
Only the webhook owner can delete a webhook. Collaborators must leave the shared webhook instead.

​
Best Practices

  1. Use Descriptive Names: Give your webhooks clear, descriptive names that indicate their purpose
  2. Tag Everything: Use tags consistently to group related webhooks (e.g., “production”, “staging”, “notifications”)
  3. Document with Descriptions: Add detailed descriptions explaining when and how to use each webhook
  4. Regular Audits: Periodically review your webhook list and remove unused webhooks
  5. Permission Management: Grant the minimum necessary permissions to collaborators
  6. Monitor Activity: Check message history regularly to catch any issues or unauthorized usage

​
Technical Details

​
Supported Webhook URLs

Both Discord domains are supported:
  • https://discord.com/api/webhooks/{id}/{token}
  • https://discordapp.com/api/webhooks/{id}/{token}

​
Metadata Storage

The system automatically extracts and stores:
  • guild_id: The Discord server ID
  • channel_id: The channel ID where messages will be posted
  • name: Webhook name from Discord
  • avatar_url: Default webhook avatar
This metadata is used for display purposes and validation.

​
Duplicate Detection

When creating a webhook, the system checks if the same webhook URL already exists in your account. If found, you’ll be warned but can choose to create it anyway (useful for having the same webhook in multiple organizational categories).

Build docs developers (and LLMs) love

Get started for freeTalk to us