How do you make a webhook in Discord?

These steps follow Discord's Help Center article Intro to Webhooks, read on 7 October 2026. Discord describes webhooks as a way to send automated messages and data updates to a text channel in your server.

• Open Server Settings for your server and go to the Integrations tab.
• Select Create Webhook.
• Choose the channel the webhook posts to from the dropdown menu.
• Give it a name that tells you which service uses it, and change the avatar if you want by selecting the image next to the name.
• Select Copy Webhook URL and paste it into the service that will send messages.

Discord's developer documentation says webhooks do not require a bot user or authentication to use. A message is a POST to /webhooks/{webhook.id}/{webhook.token}, which is the URL you copied. The body must include at least one of content, embeds, components, file or poll. A minimal JSON body is {"content": "Nightly build passed"}.

The reference sets limits you will meet early. Content can be up to 2000 characters, and a message can carry up to 10 embeds. The username and avatar_url fields override the webhook’s defaults for one message. Adding wait=true makes Discord return the created message instead of an empty response, and thread_id sends the message to a thread in the webhook’s channel. A webhook on a forum or media channel needs a thread.

Discord's help article walks through GitHub. In the repository, open Settings, then Webhooks, select Add webhook and paste the Discord URL into Payload URL. Add /github to the end of the URL, set the content type to application/json, pick the events you want, and select Add webhook again to save.

The developer reference documents the two compatible endpoints behind that: the webhook URL followed by /github, and the webhook URL followed by /slack for tools that send Slack-format messages.

The token sits inside the URL. Because executing a webhook needs no other authentication, anyone who holds the URL can post into your channel as that webhook. The same reference documents a delete call on that URL, DELETE /webhooks/{webhook.id}/{webhook.token}, so the URL alone is enough to remove the webhook too.

Keep the URL in a secret store, never in a public repository or a screenshot. If it leaks, delete the webhook and create a new one, then update the services that used it.

Discord's reference says a webhook name cannot contain clyde or discord, in any case, and can be up to 80 characters. Creating a webhook through the API requires the MANAGE_WEBHOOKS permission. If you cannot see Create Webhook in Server Settings, ask whoever administers the server.

The webhooks you make this way are the Incoming type, which posts with a generated token. The reference also lists Channel Follower webhooks, used by Channel Following, and Application webhooks, used with interactions. We did not verify Discord’s rate limit figures for this page, so read the rate limit documentation before you send in bulk.

You create the webhook in Discord, not in Swfte, and Swfte is not affiliated with Discord.

Discord appears in the Swfte Studio integrations list, and Studio’s workflow wizard includes webhook-handler and notification samples. A common pattern is a workflow that posts its outcome to a team channel once a named approver has signed off. Check the integrations page for what Studio covers for Discord today before you design around it.

• Integrations Studio connects to: check the list for Discord
• Workflows on the Swfte platform

Facts about other vendors and about the terms on this page were read on the pages below on 7 October 2026. Vendor plans, names and menus change, so check the vendor’s page before you rely on a detail.