Create and Manage Webhooks
Learn how to create a webhook, configure which events and projects it covers, and manage it over time.
When you create a webhook, Meldoc generates a signing secret that’s shown only once. Copy it immediately — you can’t retrieve it later.
Prerequisites: Admin role in your workspace.
Note: how many webhooks a workspace can have depends on your Plans & Billing. When you hit the limit, Meldoc says so — remove an unused webhook or upgrade.
Create a webhook
- Open Settings → Webhooks.
- Select Create webhook.
- In Name, enter a label that identifies the webhook’s purpose (for example,
github-sync-agent). - In URL, enter the HTTPS endpoint that will receive events. Use
http://localhostorhttp://127.0.0.1only for local testing. - Under Scope, choose Entire workspace or Selected projects and pick the projects to cover.
- Under Events, choose All events or Selected events. With Selected events, tick whole categories or individual event types.
- Select Create webhook.
- Copy the secret — it starts with
mdw_and is shown only once. Then select I have saved the secret and Done to close the dialog.
Keep in mind: If you lose the secret, rotate it. The old secret stops working the moment you rotate.
Manage webhooks
The webhook list shows each webhook’s name, URL, scope, events, creation date, who created it, and status — Active or Revoked. Select any row to open the detail view.
From the detail view you can:
- Edit — Update name, URL, scope, or event filters.
- Rotate secret — Generate a new signing secret. The old one stops working immediately, so update your receiver first in production.
- Revoke — Pause delivery without deleting. Revoked webhooks can be reactivated later and stay in the audit log.
- Reactivate — Resume delivery on a revoked webhook.
- Delete — Remove the webhook permanently; you confirm by typing the webhook’s name. Entries already in the delivery log stay for audit, but no new deliveries are attempted.
Delivery log
Select the list icon next to any webhook to open its delivery log. You can see the event type, status, attempt number, HTTP response code, duration, and scheduled time for every attempt. Open a row for the full request and response detail. To replay a specific event, select Redeliver on that entry.
What’s next?
Webhook Events — Understand what events fire and what their payloads look like.
Verifying Webhook Signatures — Verify incoming webhooks in your receiver code.
Delivery and Retries — Retry behavior and delivery guarantees.