Embeddable

Send submissions to a webhook

Send each new widget response to a web address you control, signed so your server can check it came from Embeddable.

4 min readPublished by Daniel Sternlicht on Nov 22, 2026, 10:32 AM UTCUpdated Nov 22, 2026

When someone sends a response through your widget, Embeddable can send it to an endpoint you control. Use this to start workflows in any service that accepts HTTP requests, like your own server or an automation tool such as Zapier or Make.

Before you start: you need a publicly reachable URL that accepts incoming HTTP POST requests.

Add the webhook URL

There are two ways to connect a webhook. Use Connect apps if you want to check signatures on your server, because it's the only way to set your own signing secret.

From Connect apps

  1. Open your widget in the editor.
  2. Click More, then Connect apps.
  3. Find Webhook and click Connect.
  4. Click Continue. If you see Which account? instead, choose Add another account.
  5. Give the connection a name in Name (only you see this), then paste your endpoint into Web address.
  6. Enter a signing secret in Signing secret. Use a long random string, at least 32 characters, and keep a copy for your server.
  7. Click Save and continue, make sure the new connection is selected under Which account?, and click Connect.

From the AI chat

Ask the chat to send responses to a webhook. It shows a connection card with a field labeled Webhook URL. Paste your endpoint there and click Save. Once connected, the same card lets you change the URL with the pencil icon or remove the webhook with the trash icon.

When you connect through the chat, Embeddable creates a signing secret for you automatically. You can't see that secret, so you can't use it to check signatures. If you need to check them, remove the chat connection and connect again from Connect apps with your own secret.

What gets sent

The webhook fires each time someone sends a response. For each response, Embeddable sends one request to your URL:

  • Method: POST
  • Header Content-Type: application/json
  • Header X-Signature: the signature, explained below
  • Body: the response's fields as a flat JSON object, exactly as the widget saved them. There's no wrapper, event ID or timestamp.

For example (made-up values):

{
  "name": "Example Name",
  "email": "[email protected]",
  "message": "Hello from the widget"
}

The fields depend on your widget's form. The easiest way to see them is to send a test response and read the request in your endpoint's logs.

If your widget saves more than one kind of data, you can limit the webhook to some of it. In Connect apps, open Webhook, open Send each response, and choose under Run when data is saved to. With nothing selected, it runs for everything the widget saves.

Check the signature

X-Signature is an HMAC-SHA256 of the raw request body, made with your signing secret and written as plain hex. It has no sha256= prefix. To check it, compute the same HMAC over the body exactly as you received it, before parsing the JSON, and compare. In Node.js:

const crypto = require("crypto");

function isValidSignature(rawBody, signature, secret) {
  const expected = crypto
    .createHmac("sha256", secret)
    .update(rawBody)
    .digest("hex");
  const a = Buffer.from(expected);
  const b = Buffer.from(signature || "");
  return a.length === b.length && crypto.timingSafeEqual(a, b);
}

Reject the request if the check fails.

Retries and duplicates

Your endpoint should reply with a 2xx status code. If it returns another status, or can't be reached, Embeddable tries again later. It tries up to 5 times in total. After that, the request is dropped and won't be sent again.

Because of retries, your endpoint can sometimes get the same response more than once. Since there's no event ID, de-duplicate on something in the body, like the email address together with the time, if duplicates would cause problems.

Test delivery

  1. Make sure the webhook shows as connected.
  2. Send a response through your widget yourself with sample data you will recognize, like a test name or a test email address.
  3. Open the logs or request inspector for your endpoint and look for the incoming request.
  4. Read the request body. It shows the exact fields your endpoint will receive. Build your handler against what you see there.

If nothing arrives:

  • Check that the URL is complete and correct, including https://.
  • Confirm the endpoint is publicly reachable and accepts POST requests.
  • Make sure the webhook shows as connected under More, then Connect apps, then send another response.

If it still fails, email us through the contact page with your widget name and any error messages from your endpoint.

Expected result: each test response produces one request at your webhook URL, and your workflow runs from it.

Did this answer your question?

Your feedback helps us improve.