Guide · GitHub → Discord · Verified November 1, 2026
GitHub to Discord webhook guide
Short answer: One GitHub endpoint verifies each delivery, a destination filter keeps the events in this guide, and every match is delivered to Discord with its own retry schedule and delivery log.
A reviews channel needs to see pull requests without anyone watching GitHub. This pairing posts each opened pull request as one message plus an embed that links straight to the diff: the title is the approval prompt, and the embed keeps the repository and label context that Discord's plain content would flatten.
At a glance
1. Configure the GitHub webhook
- In the repository, open Settings → Webhooks → Add webhook and paste the endpoint's ingestion URL.
- Set Content type to application/json and paste the same signing secret the endpoint uses.
- Choose “Let me select individual events” and enable Issues, Issue comments, Pull requests, Pushes, Releases, and Workflow runs as needed.
- Open or label an issue to send the first delivery, then check the delivery log.
HMAC-SHA256 over the raw request body, compared in constant time. No timestamp header, so there is no clock-window check.
2. Filter to the events that matter
Filters run per destination before rendering, so a non-matching event is stored with no delivery and no agent call. The rules below are the difference between a useful pairing and a noisy one.
Filter: opened pull requests only
{
"allow": [
{ "field": "event.type", "op": "equals", "value": "pull_request.opened" }
],
"senders": {
"allow": { "associations": ["OWNER", "MEMBER", "COLLABORATOR"] }
},
"ignoreBots": true
}3. Configure the Discord destination
A Hooks Discord destination POSTs a message to a channel's incoming webhook URL; that URL carries the token, so it lives in a project secret. Content is plain text with optional embeds, and Discord answers 204 when the message is accepted.
Destination: Discord incoming webhook
{
"webhookUrl": "{{secret.DISCORD_WEBHOOK_URL}}",
"content": "New PR: {{event.subject.title}}\n{{event.subject.url}}",
"embeds": "{\"title\":\"{{event.subject.title}}\",\"url\":\"{{event.subject.url}}\"}"
}Secrets enter configs only as {{secret.NAME}} references; literal credentials are rejected. Full Discord target guide
4. Verify the delivery and its retries
Send one real event from the source, then open Deliveries. A 2xx from the target means accepted, not finished. 408, 425, 429 and 5xx retry with backoff honoring Retry-After; other 4xx fail permanently with a named code. The rendered request is stored per attempt, so a bad field path is visible without re-sending.

The pitfall this pairing hits
A rendered embed must still be valid JSON. The embeds string is rendered first and parsed second, and template output is not JSON-escaped. A pull request title containing a double quote breaks the JSON and fails the delivery with INVALID_DISCORD_EMBEDS, so keep untrusted text in content and put only URLs and short literals in the embed.
Frequently asked questions
Do I need one endpoint per source or one per destination?
One endpoint per source. Each destination under that endpoint carries its own filter, template, retry schedule, and delivery log, so the same event can feed several targets without duplicate ingress URLs.
What happens while the target is down?
Retryable failures back off and retry within the destination's window; permanent 4xx failures stop immediately. Either way, the original event stays stored, so after fixing the target you replay the event instead of asking the source to send it again.
A rendered embed must still be valid JSON
The embeds string is rendered first and parsed second, and template output is not JSON-escaped. A pull request title containing a double quote breaks the JSON and fails the delivery with INVALID_DISCORD_EMBEDS, so keep untrusted text in content and put only URLs and short literals in the embed.