Debugging Webhooks
Self-serve tools for diagnosing why events aren't showing up in Discord.
Octoflow's API exposes a few plain-text endpoints you can open directly in a browser to diagnose a webhook without needing GitHub's delivery logs or bot commands.
Webhook diagnostic view
Visiting your webhook's URL directly (instead of having GitHub POST to it) returns a plain-text dump of everything Octoflow knows about that webhook:
- Whether it's marked broken, and its comment
- Every event modifier attached to it (ID, event list, blacklist/whitelist flags, redirect channel, priority)
- Every repository linked to it (repo name, repo ID, channel ID, when it was linked)
This is the fastest way to confirm a repository is actually linked, or that an event modifier looks the way you expect, without running /list or /eventmod commands.
This page is unauthenticated — anyone with your webhook ID can view this info (though not your secret). Don't share your webhook ID publicly.
Per-event audit logs
Every event Octoflow accepts and processes gets a log ID. The response to GitHub's delivery (visible in GitHub's Recent Deliveries tab) includes a line like:
Opening that URL shows a step-by-step trace of how that specific event was handled — ACL/event-modifier checks, channel resolution, and the result of sending to Discord. Use this when an event shows up in GitHub's delivery log as successful but never appears in Discord.
Public status endpoints
These endpoints are informational and may change without notice.
| Endpoint | Returns |
|---|---|
/api/counts | Guild, user, and shard counts, comma-separated. |
/api/events/listview | Human-readable list of currently supported GitHub event types. |
/api/events/csview | Same list, as a comma-separated machine-readable string. |
Common statuses
- 206 (Partial Content) on delivery — the repository named in the payload hasn't been linked to this webhook. Run
/newrepowith the exact owner/name. - 401 (Unauthorized) — the HMAC signature didn't match. Double check the Secret field in GitHub matches the value from your DM, and that you didn't paste the webhook ID into the secret field by mistake.
- 500 (Internal Server Error) — the webhook is marked
broken(see/newhook'sbrokenparameter, or contact support if you didn't set this).