Automation and AI

Webhook

A webhook is an HTTP request that one system sends to a URL you provide when an event happens, so the receiving system learns about it right away instead of asking.

Also called: webhook payload, webhook URL, HTTP callback, web callback

With a normal API you ask a question and get an answer: “any new orders?”. A webhook flips this around. You give the other system a URL, and when something happens it calls that URL with the details. The other system does the work of telling you; you do not poll.

The parts

  • The event. Something happens: a form is submitted, a payment succeeds, a build finishes.
  • The URL. The endpoint you registered, which you or a tool such as Slack, Zapier, Make or n8n controls.
  • The payload. The body of the request, most often JSON, describing the event.
  • The response. Your endpoint should answer with a 2xx status quickly. Anything else tells the sender the delivery failed.

Good practice for receivers

Return a response fast and do heavy work afterwards. Expect the same event more than once and make handling it safe to repeat. Use HTTPS, and where the sender supports a secret or signature, check it so that a stranger cannot post fake events to your URL.

A typical form payload

{
  "name": "Jane",
  "email": "jane@example.com",
  "message": "Hello!",
  "submitted_at": "2026-11-11T09:30:00Z"
}

In StaticForm

A webhook is one of the submit actions that run after a form submission. You set the URL (which can contain submitted values, URL-encoded automatically), the HTTP method (POST by default), the content type (JSON or form-urlencoded), up to 50 custom headers and a body template with field tokens like {{form.email}}. Slack, Discord and Microsoft Teams get a visual message builder with a live preview, and a Test button sends sample data. Every run is logged with its status, and a failed webhook can be retried from the dashboard. A run condition can limit a webhook to certain submissions.

Learn more