A webhook sends a POST request with JSON to your URL every time something happens in fydbek: new feedback arrives, a status changes, someone writes a comment. Use it with Make, Zapier, n8n or your own system. For Freelo, Asana, ClickUp, Basecamp, Trello and GitHub fydbek has built-in integrations, no webhook needed.
Setup
An organization admin adds the webhook in the dashboard under Organization settings, Webhooks. Enter the URL (https:// on a public domain only), the project (or all of them) and the events. After saving you see the whsec_... secret once, you need it to verify the signature. Save it, it is not shown again. An organization can have up to 10 webhooks.
In Make use Webhooks, Custom webhook, in Zapier Webhooks by Zapier, Catch Hook, in n8n the Webhook node. Paste the URL the tool gives you into fydbek. The Test button sends a ping event.
Events
| Event | When it arrives |
|---|---|
feedback.created | New feedback from the widget, extension or app. |
feedback.status_changed | Status change, data has from and to. A confirmation or reopen by the reporter also has review. |
feedback.updated | Priority, type, title, assignee or duplicate change, data.before holds the previous values. |
feedback.deleted | Feedback deleted. |
comment.created | New comment. The webhook is for the team, so internal comments arrive too with internal: true. Do not send them to the client. |
link.created | Feedback was linked to a task in another tool. |
Request body
{
"id": "evt_01M5WRV7592BPPHY4JQ9F56XAR",
"type": "comment.created",
"created_at": "2026-10-26T18:51:26.249Z",
"project": { "id": "prj_01M5...", "name": "Eva Vzorová" },
"feedback": {
"id": "fb_01M5...",
"number": 12,
"title": "The contact form does not send",
"status": "triaged",
"priority": "high",
"type": "bug",
"page_url": "https://eva-vzorova.cz/kontakt",
"url": "https://app.fydbek.com/codebros?item=fb_01M5..."
},
"actor": { "type": "user", "id": "usr_01M5...", "name": "Eva Vzorová", "via": null },
"comment": { "id": "cmt_01M5...", "body": "Still showing an error.", "internal": false, "author": "Eva Vzorová" },
"data": { "commentId": "cmt_01M5...", "internal": false }
}
feedback.url opens the detail in the dashboard. Events without a comment have no comment. The data is current at the time of sending, not at the time of the event.
Headers
Fydbek-Event: event type.Fydbek-Delivery: event ID, the same on every retry. Use it to detect duplicates.Fydbek-Signature:t=1793040686,v1=b7cb..., wheretis the send time in seconds andv1is HMAC-SHA256 oft.bodywith the webhook secret, in hex.User-Agent:fydbek-webhooks/1.
Verifying the signature
Compute the signature from the body exactly as received, not from parsed and re-serialized JSON. Reject requests older than 5 minutes.
Node.js
import { createHmac, timingSafeEqual } from 'node:crypto';
// rawBody: the request body exactly as received (string), header: Fydbek-Signature
export function verifyFydbek(rawBody, header, secret) {
const parts = Object.fromEntries(header.split(',').map((p) => p.split('=')));
if (Math.abs(Date.now() / 1000 - Number(parts.t)) > 300) return false;
const expected = createHmac('sha256', secret).update(`${parts.t}.${rawBody}`).digest('hex');
const actual = String(parts.v1 ?? '');
return actual.length === expected.length && timingSafeEqual(Buffer.from(expected), Buffer.from(actual));
}
PHP
<?php
// $body = file_get_contents('php://input');
// $header = $_SERVER['HTTP_FYDBEK_SIGNATURE'] ?? '';
function fydbek_verify(string $body, string $header, string $secret): bool {
parse_str(str_replace(',', '&', $header), $parts);
if (abs(time() - (int) ($parts['t'] ?? 0)) > 300) return false;
$expected = hash_hmac('sha256', ($parts['t'] ?? '') . '.' . $body, $secret);
return hash_equals($expected, (string) ($parts['v1'] ?? ''));
}
Subscribing through the API
Tools such as Make or Zapier can create a webhook on their own when you turn a scenario on and delete it when you turn it off. They use the API with an organization token, which an admin creates under Organization settings, tab AI agents and API. The token needs read access to feedback and has to belong to an admin or an agent.
GET /v1/tokenreturns the token's organization (orgId,orgName), useful for testing the connection.POST /v1/hookswith the body{"targetUrl", "event", "projectId"}subscribes a webhook to one event and returns{"id"}. WithoutprojectIdyou get events from every project.DELETE /v1/hooks/:idunsubscribes it. Only the token that created it can do that.GET /v1/hooks/sample?event=...returns the last three events in the webhook format as sample data.
Admins see these webhooks in the webhook list with their source (Make, Zapier, API). They do not count toward the limit of 10. Revoking the token removes its webhooks too.
Delivery and retries
- A delivery succeeds when the URL answers with a 2xx status within 10 seconds. fydbek does not follow redirects.
- A failure is retried after 30 seconds, 2 minutes, 10 minutes and then every hour, 9 attempts in total.
- Event order is not guaranteed and the same event can arrive twice. Decide by
idandcreated_at. - When 20 events in a row cannot be delivered even after all attempts, fydbek turns the webhook off and emails the person who created it. Turn it back on in the settings.