Automation

Webhooks

A webhook is a message konnos sends to a URL you choose whenever something happens in a repository — a push, for example. It's how you wire konnos into a CI pipeline, a chat notifier, or any tool that should react to your code.

How it works

You give konnos a payload URL — an address on your side that can receive an HTTP request. When the events you picked happen, konnos POSTs a JSON body describing what occurred to that URL. Webhooks are set per repository.

Create a webhook

  1. 1

    Open the repo's Settings

    Go to the repository, open Settings, and find the Webhooks section.

  2. 2

    Enter your payload URL

    Paste the URL konnos should call. It must start with http:// or https://. The content type defaults to json, and the default event is a push.

  3. 3

    Add an optional secret, then create

    You can set a signing secret so your receiver can verify the request really came from konnos. Save, and the hook is live.

List and delete webhooks

The same Webhooks section lists every hook on the repo — its URL, content type, events, and whether it's active. Delete any one from there when you no longer need it; deleting a hook just stops the messages, it doesn't touch your code.

From the MCP

An agent can manage a repo's webhooks over the MCP phone line with the create_webhook tool — handy for wiring up delivery as part of a build. A minimal call:

{
  "tool": "create_webhook",
  "arguments": {
    "owner": "<you>",
    "repo": "invoice-parser",
    "url": "https://example.com/hooks/konnos",
    "content_type": "json",
    "events": ["push"]
  }
}

Test it before you rely on it

Point a new hook at a request-inspector URL first (any service that echoes back what it received) so you can see konnos's payload before wiring it into something important.