npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

node-webhooks

v1.6.0

Published

Create and trigger your own webHooks

Readme

node-webhooks Build Status NPM Version Coverage Status JavaScript Style Guide Dependency Status

What webhooks are used for

Webhooks are "user-defined HTTP callbacks". They are usually triggered by an event, such as pushing code to a repository or posting a comment to a blog. When that event occurs, the source site makes an HTTP request to the URI configured for the webhook. Users can configure webhooks to cause events on one site to invoke behavior on another. Common uses include triggering builds with continuous integration systems or notifying bug tracking systems. Since webhooks use HTTP, they can be integrated into web services without adding new infrastructure.

Install

npm install node-webhooks --save

or:

yarn add node-webhooks

Supports Node.js 18 or later.

How it works

When a webhook is triggered, it sends a POST request to each attached URL. The request body contains the JSON-serialized payload passed to the trigger method.

Debug

This module uses the popular debug package. Set the environment variable to enable debug output: DEBUG=node-webhooks. To launch the example with debug output enabled, run: DEBUG=node-webhooks node example.js

Usage


// Initialize the WebHooks module.
var WebHooks = require('node-webhooks')

// Initialize the webhooks module with an on-disk database.
var webHooks = new WebHooks({
  db: './webHooksDB.json', // JSON file that stores webhook URLs.
  httpSuccessCodes: [200, 201, 202, 203, 204] // Optional success status codes.
})

// Alternatively, initialize the webhooks module with an object.
// Changes will only be made in memory.
webHooks = new WebHooks({
  db: {
    addPost: ['http://localhost:9100/posts']
  }
})

// Add a new webhook called 'shortname1'.
webHooks.add('shortname1', 'http://127.0.0.1:9000/prova/other_url').then(function () {
  // done
}).catch(function (err) {
  console.log(err)
})

// Add another webhook.
webHooks.add('shortname2', 'http://127.0.0.1:9000/prova2/').then(function () {
  // done
}).catch(function (err) {
  console.log(err)
})

// Remove a single URL attached to the given shortname.
// webHooks.remove('shortname3', 'http://127.0.0.1:9000/query/').catch(function (err) { console.error(err) })

// If no URL is provided, remove all URLs attached to the given shortname.
// webHooks.remove('shortname3').catch(function (err) { console.error(err) })

// Trigger a specific webhook.
webHooks.trigger('shortname1', {data: 123})
webHooks.trigger('shortname2', {data: 123456}, {header: 'header'}) // Send a JSON POST body with custom headers.

Available events

The module uses an event emitter to expose request information when a webhook is triggered.

var webHooks = new WebHooks({
  db: WEBHOOKS_DB
})

var emitter = webHooks.getEmitter()

emitter.on('*.success', function (shortname, statusCode, body) {
  console.log('Successfully triggered webhook ' + shortname + ' with status code', statusCode, 'and body', body)
})

emitter.on('*.failure', function (shortname, statusCode, body) {
  console.error('Error triggering webhook ' + shortname + ' with status code', statusCode, 'and body', body)
})

This makes it possible to check whether a webhook trigger succeeded and to inspect request information such as the status code or response body.

Events use the format eventName.result. The selected library, eventemitter2, provides a flexible way to listen for events. For example:

  • eventName.success
  • eventName.failure
  • eventName.*
  • *.success
  • *.*

API examples

Webhooks are useful whenever you need to make sure an external service receives updates from your app. You can build API endpoints like these in your app.

  • GET /api/webhook/get Return the full webhook DB file.

  • GET /api/webhook/get/[WebHookShortname] Return the selected webhook.

  • POST /api/webhook/add/[WebHookShortname] Add a new URL for the selected webhook. A JSON body with the url parameter is required: { "url": "http://..." }

  • GET /api/webhook/delete/[WebHookShortname] Remove all URLs attached to the selected webhook.

  • POST /api/webhook/delete/[WebHookShortname] Remove a single URL attached to the selected webhook. A JSON body with the url parameter is required: { "url": "http://..." }

  • POST /api/webhook/trigger/[WebHookShortname] Trigger a webhook. It requires a JSON body that will be forwarded to the webhook URLs. You can also provide custom headers.

Author

Rocco Musolino - @roccomuso