All terms · Automation & No-Code

Webhook

A way for one application to automatically notify another when something happens, by sending an HTTP request to a URL you specify.

A webhook is a "reverse API" — instead of your application asking another service for data (polling), the service pushes data to your application the moment something happens.

API vs webhook: - API (pull): "Hey, do you have any new orders?" You ask repeatedly on a schedule. - Webhook (push): "I just got a new order — here are the details." It tells you instantly.

How it works: You register a URL (your webhook endpoint) with the service. When the trigger event occurs, the service sends an HTTP POST request to your URL with the event data. Your application receives it and acts immediately.

Common use cases in AI product workflows: - Stripe sends a webhook when a payment completes → your server activates the user's account - Typeform sends a webhook when a form is submitted → Zapier receives it and triggers an AI email reply - GitHub sends a webhook when code is pushed → your CI pipeline starts a build

In no-code tools: Zapier, Make.com, and n8n can receive webhooks as trigger events, making it easy to connect almost any service to an automation workflow without writing server code.

Example

You paste a Zapier webhook URL into your Stripe dashboard. Every time a new customer pays, Stripe pings that URL with the customer's details. Zapier receives it, looks up the customer in your CRM, and sends a personalised welcome email — automatically.