Zapier Catch Hook — signed webhook, not a Zapier app

What it does

• Catch Hook, not a Zapier app. When a new feedback item matches a webhook destination, FDT POSTs one JSON body to the HTTPS URL you paste. A Zapier Catch Hook is one such URL. There is no Zapier app and no Zapier OAuth.
• Signed webhook. Signed webhook: each matching item POSTs JSON to your HTTPS URL with header x-fd-signature: sha256=<hex HMAC-SHA256 of the raw body> using the project signing secret. Payload fields: id, projectId, projectName, projectSlug, changeType, whatToChange, expectedBehavior, priority, status, pageContext, screenshotUrl, consoleLogs, networkLogs, classification, createdAt. Works with any HTTPS endpoint, e.g. a Zapier Catch Hook, Make or n8n webhook. Not a native Zapier app.
• Retries / backoff. Delivery goes through the same routing outbox as Slack. A non-2xx from the Catch Hook is retried with backoff, then dead-lettered. The last error shows on the destination row.

How to connect

1. In Zapier, add a Catch Hook trigger and copy the webhook URL.
2. In the FDT project dashboard: Project → Settings → Destinations → Add → Webhook, paste that URL, and set the project signing secret in the same Destinations panel (shown once — it is not part of the URL).
3. Submit a test feedback item. The Zap receives one JSON POST whose header x-fd-signature is sha256= plus the HMAC-SHA256 of the raw body.

Honest limits

• This is not a native Zapier app.
• No two-way sync. FDT does not read Zap history, and it does not update the item when a Zap finishes.
• HMAC verification is the caller's job. A Catch Hook stores the body; it does not check x-fd-signature for you.
• Same sink as Make or n8n — any HTTPS endpoint, not a Zapier-only path.

Board recipes you build yourself (not a published Zapier template): Trello via Zapier, Asana via Zapier, Teamwork via Zapier. Each one is the Catch Hook above plus that tool's create action. Via Zapier, not natively.

See also GitHub, Slack, Linear and docs.