Sign Up for Free

RunKit +

Try any Node.js package right in your browser

This is a playground to test code. It runs a full Node.js environment and already has all of npm’s 1,000,000+ packages pre-installed, including contentful-webhook-tunnel with all npm packages installed. Try it out:

var contentfulWebhookTunnel = require("contentful-webhook-tunnel")

This service is provided by RunKit and is not affiliated with npm, Inc or the package authors.

contentful-webhook-tunnel v2.0.6

An HTTP server for listening to Contentful API Webhooks with secure tunnels to localhost.

contentful-webhook-tunnel

Build Status NPM Dependency Status NPM Verion

A simple HTTP server for listening to Contentful API Webhooks with secure tunnels to localhost by ngrok.

This module extends contentful-webhook-listener.js to automatically start up ngrok with a tunnel to the same port and registers a webhook for the ngrok URL with Contentful.

This is very useful for local development and/or servers behind firewalls to create a script with custom callbacks for any or all actions that occur in Contentful.

Install

npm install contentful-webhook-tunnel

Usage

Require this module and then create a new server. The createServer function expects the first argument to be an object with the spaces key and an array of space IDs to register the webhook with.

Then listen for one or more of Contentful webhook events, create, save, autoSave, archive, unarchive, delete, publish or unpublish on the server object and setup a custom callback. See contentful-webhook-listener.js for details on the payload for each event.

Lastly, instruct the server to start listening.

var tunnel = require("contentful-webhook-tunnel");

var server = tunnel.createServer({
    "spaces": [ "cfexampleapi" ]
});

server.on("publish", function (payload) {

    console.log("Received webhook for Publish event in Contentful");
    
    // see payload for details
    console.log(payload);

});

server.listen();

To register the webhooks via the Contentful Content Management API requires an access token. Vist the Contentful Developer Center to acquire an access token for a local script. Then, save that token to an environment variable named CONTENTFUL_MANAGEMENT_ACCESS_TOKEN.

Ngrok defaults to using tunnel servers in the US. To use a tunnel server outside the US then set the NGORK_REGION environment variable to another region. See the ngrok documentation for the list of supported regions.

To have your tunnel protected with HTTP Basic Auth, you must create an account with ngrok, get your access token, and set the NGROK_AUTH_TOKEN environment variable. If that environment variable is present, then a random username and a random password will be created and registered with Contentful each and every time the script is run.

How it Works

Node.js is used to create a HTTP server that listens for requests and processes them as requests from Contentful Webhooks. When this server starts listening, then ngrok is started up and connected to the same port as the server and requires the same authentication, if any. Once ngork is connected and provides an ngrok URL, then the ngrok URL is registered with Contentful via the Contentful Content Management API. If the server is interrupted or terminated, then the registered webhook will be removed from Contentful.

Deploying and running this server on a publicly accessible system does not require ngrok and, therefore, should use the contentful-webhook-listener.js server, that this is based on, instead.

Advanced Usage

In addition to the Contentful webhook events, this server also emits the following events.

Event: 'error'

  • The error that occurred.

Emitted when an error occurs. The server will be closed directly following this event.

Event: 'ngrokConnect'

  • the public URL of your tunnel
  • the URL to your local ngork web interface
  • the local port number that is forwarded

Emitted after ngork connects.

Event: 'ngrokDisconnet'

Emitted after ngrok disconnects.

Event: 'webhookCreated'

  • <Webhook> the webhook definition from Contentful

Emitted after a webhook record is created via the Contentful Content Management API.

Event: 'webhookDeleted'

Emitted after a webhook record is deleted via the Contentful Content Management API.

Usage with a Proxy

To proxy HTTP(S) requests, then set the appropriate npm config variables.

npm config set https-proxy http://proxy.example.com:3128/
npm config set proxy http://proxy.example.com:3128/

If the npm config variables are not found, then these environment variables will be used.

HTTPS_PROXY=http://proxy.example.com:3128/
HTTP_PROXY=http://proxy.example.com:3128/

Todo

  • added close() method to delete webhook records and close tunnels
  • accept a single space or an array of spaces or an options object as the first argument to createServer()

Change Log

2.0.6 — October 21, 2019

  • updated deps to latest
  • resolved security issue with eslint

2.0.5 — May 24, 2019

  • updated property name for proxy config for contentful-management

2.0.4 — May 23, 2019

  • improved build

2.0.3 — May 23, 2019

  • updated some ngrok calls to promises

2.0.2 — February 19, 2018

  • updated dependancies to resolve security issues

2.0.1 — June 19, 2018

  • updated package-lock.json file

2.0.0 — June 19, 2018

  • updated dependancies to resolve security issues
  • updated to ngrok 3.0 which requires 8.3.0 or greater

1.6.1 — November 21, 2017

  • fixed bug in custom header declaration

1.6.0 — November 21, 2017

  • added custom header when webhook is created in Contentful to note when it was created

1.5.4 — June 13, 2017

  • fixed bug that prevented authentication from being setup

1.5.3 — June 13, 2017

  • fixed bug that caused multiple tunnels to use the same options
  • fixed bug that caused multiple tunnels to register with all spaces
  • optimized tunnel creation
    • multiple spaces no longer require multiple tunnels
    • one tunnel is created and registered in each space
  • improved readability of code in constructor
  • refactored the process of finding and removing existing webhooks with the same name before re-connecting to make better use of promises

1.5.2 — June 12, 2017

  • ngrok options can now be passed to createServer()

1.5.1 — June 12, 2017

  • only binds tls for https

1.5.0 — March 17, 2017

  • port number no longer defaults to 5678
  • if port number is not specified, then the OS will chose a random port number

1.4.0 — March 16, 2017

  • added HTTP proxy support with https-proxy-agent
  • proxy settings are read from the npm config or from the environment variables

1.3.0 — February 7, 2017

  • made HTTP Basic Auth optional since it requires an ngork account
  • options that require an ngork account are now only used if the NGROK_ACCESS_TOKEN is found in the process environment

1.2.0 — January 31, 2017

  • automatically removes orphaned tunnels from the same host upon reconnection
  • returns the URL to the ngrok UI and the local port number that is forwarded as arguments to the ngrokConnect event in addition to the public ngork URL
  • requires ngrok 2.2.6 or greater to get the ngrok UI URL, otherwise that argument will be undefined

1.1.0 — November 4, 2016

  • random username and password are used if none are provided
  • port number defaults to 5678 if none is provided

1.0.0 — November 3, 2016

  • initial version

License

contentful-webhook-tunnel is available under the MIT License.

RunKit is a free, in-browser JavaScript dev environment for prototyping Node.js code, with every npm package installed. Sign up to share your code.
Sign Up for Free