Agent skill

Typeform Webhooks Skill

Receive and verify Typeform webhooks. Use when setting up Typeform webhook handlers, debugging Typeform-Signature verification, or handling form events like form_response and form_response_partial submissions.

Install this skill

npx skills add hookdeck/webhook-skills --skill typeform-webhooks

When to Use This Skill

  • How do I receive Typeform webhooks?
  • How do I verify Typeform webhook signatures?
  • How do I handle form_response (form submission) events?
  • Why is my Typeform-Signature verification failing?
  • Understanding Typeform event types and the form_response payload

Verification (core)

Typeform signs the raw request body with HMAC-SHA256 keyed on your per-webhook secret. The digest is base64-encoded (not hex) and sent in the Typeform-Signature header prefixed with sha256=. Pass the raw body, build sha256=<base64 digest>, and compare timing-safe. Typeform does not follow the Standard Webhooks spec, and there is no signature-verification SDK — verify manually.

Node:

const crypto = require('crypto');

function verifyTypeformSignature(rawBody, signatureHeader, secret) {
  if (!signatureHeader) return false;
  const hash = crypto.createHmac('sha256', secret).update(rawBody).digest('base64');
  const expected = `sha256=${hash}`;
  try {
    return crypto.timingSafeEqual(Buffer.from(signatureHeader), Buffer.from(expected));
  } catch {
    return false; // length mismatch = invalid
  }
}

Python:

import hmac, hashlib, base64

def verify_typeform_signature(raw_body: bytes, signature_header: str, secret: str) -> bool:
    if not signature_header:
        return False
    digest = hmac.new(secret.encode(), raw_body, hashlib.sha256).digest()
    expected = "sha256=" + base64.b64encode(digest).decode()
    return hmac.compare_digest(expected, signature_header)

Important: The signing secret is only sent when you add one to the webhook (Connect > Webhooks > Edit > Add a Secret, or via the Webhooks API). If no secret is configured, no Typeform-Signature header is sent.

For complete handlers with route wiring, event dispatch, and tests, see:

Common Event Types

Event TypeTriggered WhenCommon Use Cases
form_responseA respondent completes and submits a formCRM sync, notifications, lead capture, fulfillment
form_response_partialA respondent submits partial answers (requires the partial submit points form feature)Abandoned-form follow-up, drop-off analytics

form_response_partial requires the partial-submit-points feature enabled on the form and may be plan-gated. The payload shape matches form_response.

Payload Structure

{
  "event_id": "01F...",
  "event_type": "form_response",
  "form_response": {
    "form_id": "lT4Z3j",
    "token": "a3a12ec67a1365927098a606107fac15",
    "landed_at": "2026-07-22T14:00:00Z",
    "submitted_at": "2026-07-22T14:05:00Z",
    "definition": { "id": "lT4Z3j", "title": "...", "fields": [ ] },
    "answers": [
      { "type": "email", "email": "user@example.com", "field": { "id": "abc", "type": "email" } }
    ]
  }
}

Only answered fields appear in answers — unanswered or logic-skipped fields are omitted. See references/overview.md for the answer types.

Environment Variables

TYPEFORM_WEBHOOK_SECRET=your_webhook_secret   # The secret you set on the webhook (UI or API)

Local Development

# Start tunnel (no account needed). Typeform requires HTTPS — the tunnel provides it.
npx hookdeck-cli listen 3000 typeform --path /webhooks/typeform

Reference Materials