HELP / ANALYTICS & API

Connect Kudokit to Zapier or Make

Send new testimonials to thousands of other tools with a webhook — no native app required.

2 MIN READ

There is no native Zapier or Make app for Kudokit — but a webhook does the same job. Both tools have a generic "Webhooks" trigger that catches whatever Kudokit sends, so connecting takes about the same effort either way.

What triggers it

One event: a new testimonial, from a form submission or a manual add. A video testimonial fires it once processing finishes, not the moment it is uploaded. Bulk imports — a CSV, an auto-import run — deliberately do not fire it; a 500-row spreadsheet would otherwise flood your Zap with 500 runs at once.

Set it up

  1. In Zapier, create a Zap and choose Webhooks by Zapier → Catch Hook as the trigger. Copy the webhook URL it gives you. (Make's equivalent is a Webhooks module with "Custom webhook.")
  2. In Kudokit, open Workspace settings → Integrations and paste that URL in. Admin only, and available on Pro.
  3. Kudokit shows you a signing secret once, right after you add it — save it if you plan to verify the signature (see below). It is not shown again.
  4. Send a real testimonial through to confirm the connection — there is no separate "send test event" button, so the first real one is the test.

What arrives

A JSON body shaped like:

{
  "event": "testimonial.created",
  "data": {
    "id": "...",
    "type": "text",
    "status": "pending",
    "author_name": "...",
    "author_company": "...",
    "rating": 5,
    "headline": "...",
    "body": "...",
    "mux_playback_id": null,
    "created_at": "..."
  }
}

From there, build whatever Zapier or Make does next — post it to Slack, add a row to a spreadsheet, send yourself an email.

Verifying it's really from Kudokit

Each request is signed with HMAC-SHA256 over the raw body, using your webhook's secret, sent in an X-Kudo-Signature header alongside X-Kudo-Event. If you are building something more custom than a no-code trigger and want to check requests are genuine rather than spoofed, verify that signature server-side before trusting the payload.

If it stops arriving

A webhook that fails several times in a row is disabled automatically rather than retried forever — check Workspace settings → Integrations for one marked failing or disabled, and re-add it.


Related

Was this helpful?

Support

Still stuck? Email support.

A human replies — usually within a few hours.

Email support