When the built-in integrations do not cover your workflow, webhooks give you a raw HTTP callback for every feedback event. Quackback sends a JSON payload to your endpoint whenever a post is created, a vote is cast, a status changes, or a comment is added. Every payload is signed with HMAC-SHA256 so your server can verify the request came from Quackback. Failed deliveries retry with exponential backoff, and delivery logs in the admin panel let you debug issues without guessing. Developers who want to feed feedback data into internal tools, data warehouses, or custom notification systems can build on top of webhooks without depending on third-party automation platforms.
How it works
Connect Webhooks to Quackback in three steps.
Register your endpoint URL
Add your HTTPS endpoint URL in the Quackback webhook settings and set a signing secret for HMAC-SHA256 verification.
Select event types
Choose which events (post created, vote cast, status changed, comment added) trigger a delivery to your endpoint.
Payloads start arriving
Your endpoint receives signed JSON payloads within seconds of each event. Failed deliveries retry automatically with exponential backoff.
Why connect Quackback to Webhooks
Build any integration you need
Webhooks deliver structured JSON for every event type. Your backend receives the same data the native integrations use, so you can build a Slack bot, a custom dashboard, or a data pipeline. Whatever your workflow requires.
Verify payloads cryptographically
Every webhook payload includes an HMAC-SHA256 signature computed with a secret key you set in the admin panel. Your endpoint can verify the signature before processing, ensuring the request is authentic and unmodified.
Debug failed deliveries in the admin panel
The delivery log shows every webhook attempt, response code, and payload. If your endpoint returns an error, you can inspect the request body, fix the issue, and manually re-trigger the delivery. No guesswork involved.
Capabilities
HMAC-SHA256 signed payloads for security
Configurable event triggers
Retry logic with exponential backoff
Delivery logs and debugging tools
Use cases
Build custom notification pipelines
Trigger internal workflows when feedback changes status
Feed feedback data into analytics or data warehouses
Webhooks setup guide
Step-by-step instructions to connect Webhooks with Quackback.
Frequently asked questions
Are webhook payloads signed for security?
Yes. Every payload is signed with HMAC-SHA256 using a secret key you configure, so you can verify the request came from Quackback.
What happens if my webhook endpoint is down?
Quackback retries failed deliveries with exponential backoff. You can view delivery logs and manually re-trigger failed payloads from the admin panel.
Get started with Quackback + Webhooks
Deploy Quackback and connect Webhooks in minutes. Free forever on your own infrastructure.