Skip to main content
Apply for a Cheap Website
Website explainer · 1:47

Webhooks Explained: When One Service Notifies Another

How can one service tell another something changed? A webhook sends an update when a chosen event happens.

Jersey Web video: Something just happened

1:47 · No narration: the video shows each step as text on screen, and every step is written out below, with buttons that jump the video to it.

Download the on-screen text track (VTT)

The six points in the video

This is a silent video. The headings, explanations and labels below reproduce the information on screen.

  1. Step 1: Choose the event

    Subscribe to the specific change the business needs to know.

    On-screen labels: Selected event; Relevant update; Clear purpose.

  2. Step 2: Send to a receiving address

    The service delivers event data to a configured URL.

    On-screen labels: Source service; Receiving URL; Event data.

  3. Step 3: Verify the sender

    The receiving system should validate the delivery correctly.

    On-screen labels: HTTPS connection; Signature checks; Protected secret.

  4. Step 4: Define the follow-up action

    Receiving data and completing a business task are separate steps.

    On-screen labels: Received update; Process the data; Confirm the result.

  5. Step 5: Plan for missed deliveries

    Check retry or redelivery options when systems are unavailable.

    On-screen labels: Delivery failure; Retry policy; Recovery process.

  6. Step 6: Handle repeated messages

    A repeated event must not accidentally trigger duplicate work.

    On-screen labels: Event identifier; Duplicate check; Safe processing.

A practical check for your business

Record which event sends the notification and what the receiving system is expected to do. Use safe test data to check delivery, failures and repeated notifications before relying on the workflow.

Sources and further detail

See it in a diagram

Webhook flow showing a selected event, a verified notification delivery and a receiving system processing the follow-up action.
Webhooks, explained. A webhook delivers event data; the receiver must verify and process it.
Read the diagram as text
  1. An event happens: The selected change occurs
  2. Notification is sent: Event data reaches a URL
  3. Receiver processes it: The follow-up task runs

Plan for delivery problems. Check retries, missed events and repeated messages.

Receiving an update is not proof the task completed.

Diagram by Jersey Web. Open full size · Source and further detail (opens in a new tab)

Common questions

How can one service tell another something changed?

A webhook sends an update when a chosen event happens. Check both delivery and the action that follows.

Go further

Guide Read the practical guide More context for planning and maintaining your business website. 5 min read → Jargon Buster Webhook explained Read the related Jargon Buster explanation. Read the explanation →

Check both delivery and the action that follows.

Tell Jersey Web what your website needs to do and which part you want help with.

Talk to Jersey Web →

More video tips

All 205 videos →
Length 1:47 Website foundations

What Is a CMS? Editing Your Website Content Explained

Content management, explained.
Length 1:47 Website foundations

Static vs Dynamic Websites: What the Terms Actually Mean

Two ways to deliver pages.
Length 1:47 Website foundations

HTML Explained: The Structure Behind Your Website

The structure of a web page.