🪝 Bleed Webhook Management

Bleed’s Webhook system allows the Owner to create, manage, lock, unlock, and send messages through Discord webhooks.

Webhooks can post messages through custom identities and are useful for automation, announcements, integrations, and themed system messages.

Because webhooks can imitate custom senders and affect server content directly, these commands should remain Owner-only.

🪝 Open Webhook Management

,webhook

Opens Bleed’s webhook-management system.

➕ Create a Webhook

,webhook create [name]

Creates a webhook that can be used to send or forward messages.

Permission Required: Manage Webhooks

Choose clear names so you can identify each webhook later.

📋 View Webhooks

,webhook list

Lists available webhooks in the server.

Bleed lists no special Discord permission for this command, but within the Archivist’s Vault I would still treat webhook information as owner-level administration.

📤 Send Through a Webhook

,webhook send [identifier] [message or embed code]

Sends a message through an existing webhook.

This can be useful for:

• themed announcements
• automated notices
• system-style messages
• embeds posted under a specialized identity

✏️ Edit a Webhook Message

,webhook edit [message link] [message or embed code]

Edits a message that was sent through an existing channel webhook.

Use this when correcting or updating webhook-posted information.

🔒 Lock a Webhook

,webhook lock [identifier]

Locks a webhook so it cannot be accessed by others through Bleed.

This is especially useful for important announcement or system webhooks.

,webhook unlock [identifier]

Removes the lock.

⚠️ Only unlock a webhook when there is a clear reason to restore broader access.

🗑️ Delete a Webhook

,webhook delete [identifier]

Deletes a webhook from the channel.

Permission Required: Manage Webhooks

Treat deletion carefully, especially if other systems or integrations depend on that webhook.

⚖️ Laws of Webhook Use

I. Protect Webhook Identity

Do not create webhook identities that falsely impersonate real members or staff.

II. Lock Important Webhooks

Announcement, moderation, or system webhooks should be locked when possible.

III. Keep Ownership Clear

Members should be able to distinguish official system messages from ordinary user speech.

IV. Avoid Unnecessary Webhooks

Create only those with a defined purpose.

V. Review Before Deleting

Confirm that no automation or integration still depends on a webhook before removing it.

📜 Quick Reference

,webhook create — Create webhook
,webhook list — View webhooks
,webhook send — Send through webhook
,webhook edit — Edit webhook message
,webhook lock — Restrict access
,webhook unlock — Restore access
,webhook delete — Delete webhook

🪝 Webhooks may speak with many voices, but every official voice of Holme should remain deliberate and accountable.