How to Test Netlify Webhooks

Netlify Webhook Events

Netlify's outgoing notification system fires HTTP POST requests to your endpoint when build and deploy state changes. You can configure multiple notification targets for the same event — useful for notifying Slack, a logging service, and your own handler simultaneously.

Step 1: Generate a Requex Endpoint

Open requex.me. A webhook URL is generated for you instantly — no account needed. Copy the full URL:

https://requex.me/hook/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Keep the Requex tab open. Deploy events will appear in real time as Netlify fires them.

Step 2: Add an Outgoing Notification

In the Netlify dashboard, navigate to your site and follow these steps:

1. Go to Site → Settings → Build & deploy → Deploy notifications.
2. Click Add notification.
3. Select Outgoing webhook from the dropdown.
4. Choose the event to listen for (e.g., Deploy succeeded).
5. Paste your Requex URL into the URL to notify field.
6. Click Save.

Repeat for any additional events you want to capture (e.g., also add a notification for Deploy failed). Each event is a separate notification entry.

Step 3: Trigger a Deploy

The simplest way to trigger a deploy is to push to the git branch linked to the Netlify site:

# Push an empty commit to trigger a Netlify build
git commit --allow-empty -m "chore: trigger netlify webhook test"
git push origin main

Alternatively, trigger a manual deploy from the Netlify dashboard: Deploys → Trigger deploy → Deploy site. Netlify will fire the "Deploy started" notification immediately, followed by "Deploy succeeded" or "Deploy failed" when the build completes.

Step 4: Inspect the Payload

Click the captured request in Requex to see the full payload. Netlify sends a rich JSON object with deploy details:

{
  "id": "6612a4f5a1b2c3d4e5f60001",
  "site_id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "build_id": "6612a4f5a1b2c3d4e5f60002",
  "state": "ready",
  "name": "my-netlify-site",
  "url": "https://my-netlify-site.netlify.app",
  "deploy_url": "https://6612a4f5--my-netlify-site.netlify.app",
  "branch": "main",
  "commit_ref": "da1560886d4f094c3e6c9ef40349f7d38b5d27d7",
  "commit_url": "https://github.com/myorg/myrepo/commit/da1560...",
  "title": "chore: trigger netlify webhook test",
  "deploy_time": 42,
  "created_at": "2026-04-05T10:00:00.000Z",
  "updated_at": "2026-04-05T10:00:42.000Z"
}

The state field reflects the deploy outcome: ready for success, error for failure. The deploy_time is in seconds.

Netlify Form Webhooks

Netlify's outgoing notification system also supports form submissions. When a visitor submits a form on your Netlify site (using Netlify Forms), you can have Netlify POST the form data to your webhook endpoint.

To set this up, add a new outgoing webhook notification and choose Form submitted as the event. You can optionally filter by form name to only receive notifications for a specific form. The payload includes the form name, submission data, and metadata:

{
  "number": 42,
  "title": "New form submission from: contact",
  "email": "visitor@example.com",
  "name": "Jane Smith",
  "first_name": "Jane",
  "last_name": "Smith",
  "company": null,
  "summary": "Hello, I would like to enquire...",
  "body": "Hello, I would like to enquire about your services.",
  "data": {
    "name": "Jane Smith",
    "email": "visitor@example.com",
    "message": "Hello, I would like to enquire about your services."
  },
  "form_name": "contact",
  "site_url": "https://my-netlify-site.netlify.app"
}

This makes it straightforward to forward form submissions to a CRM, send Slack notifications, or trigger follow-up emails without a separate backend.

Common Netlify Webhook Issues