Skip to main content

Webhooks overview

Webhooks let external services trigger an Intellectible workflow by sending an HTTP request. Use them for incoming form submissions, application events, and notifications from other systems.

These are incoming webhooks: the sender calls Intellectible. The public endpoint does not register subscriptions for Intellectible to send events back to your application.

Configure the destination​

Create a webhook under Settings → Webhook Triggers in the destination workflow, choose its source and authentication method, and copy the generated URL. The webhook identifies the project and workflow, so the delivery URL needs only its webhook ID.

The Webhooks guide covers creation, enabling or disabling, and secret management in the app. This reference covers the public delivery endpoint, not the app’s webhook-management routes.

Choose authentication​

Webhook delivery uses a webhook-specific secret, not a project API key.

ModeSender providesSetup
TypeformTypeform-Signature: Base64 HMAC-SHA256 of the raw body, prefixed with sha256=.Save the generated secret and configure it in Typeform.
Generic static tokenX-Webhook-Token containing the generated secret.Save the token and configure the sender’s header.
Generic HMACDelivery ID, Unix timestamp, and v1= hexadecimal HMAC-SHA256 signature.Save the sender’s signing secret in the webhook settings.

A Generic HMAC webhook remains pending until its signing secret is configured. Other providers’ HMAC formats are not automatically compatible: headers, signed content, and encoding must match the delivery reference.

Use HTTPS, keep secrets server-side, and avoid logging them. Replacing a secret invalidates the old one immediately; coordinate the change with the sender.

Process the event​

Send JSON to the copied URL. The workflow receives two named inputs:

  • payload: the parsed JSON request body.
  • webhook: metadata containing source, webhookId, receivedAt, and filtered headers.

Use Input nodes with these names. Webhooks configured through the app start the workflow’s normal Start path. The guide includes an editor example.

A successful delivery returns 200 OK and {"ok":true} after the workflow is accepted for execution. It does not wait for completion or return workflow outputs. Use the synchronous workflow API if your application needs a result in the same request.

Retries and duplicate deliveries​

ModeDuplicate-delivery identifier
TypeformPayload’s form_response.token, when present.
Generic HMACSender’s Webhook-Id header.
Generic static tokenNo automatic duplicate detection.

Accepted delivery IDs are remembered for 24 hours, separately for each webhook. A recognized accepted duplicate receives the same successful response without starting another run. A concurrent duplicate still awaiting admission receives 503 DELIVERY_PENDING and Retry-After: 2.

If admission fails, the delivery claim is released so the sender can retry. For HMAC retries, preserve the delivery ID but generate a fresh timestamp and signature. Back off on transient failures such as 429 and 503, and respect Retry-After when supplied. Fix authentication or setup errors before retrying.

This is not an exactly-once guarantee. Accepted deliveries are not replayed just because the workflow later fails. Make important downstream operations idempotent, using your sender’s event ID to avoid duplicate writes or notifications.

Limits and observability​

Requests are limited to 1 MiB of JSON body. Webhook and project rate limits, workflow execution quotas, and concurrency limits also apply.

Check delivery status at the sender, then inspect Logs → API in the workflow for accepted executions. Requests rejected before admission do not start a workflow run.

Endpoint​