- [Ruby example](#ruby-example)

- [JavaScript example](#javascript-example)

Now that you have tested out your code locally, you can make changes to use your webhook in production. For more information, see "[Next steps](#next-steps)." If you had trouble testing your code, try the steps in "[Troubleshooting](#troubleshooting)."

This example uses Node.js and the Express library to define routes and handle HTTP requests. For more information, see "[expressjs.com](https://expressjs.com)."

For an example that uses {% data variables.product.company_short %}'s Octokit.js SDK, see "[AUTOTITLE](/apps/creating-github-apps/writing-code-for-a-github-app/building-a-github-app-that-responds-to-webhook-events)."

This example requires your computer or codespace to run Node.js version 12 or greater and npm version 6.12.0 or greater. For more information, see [Node.js](https://nodejs.org).

To use this example, you must install the `express` library in your Node.js project. For example:

```shell copy

npm install express

Create a JavaScript file with the following contents. Modify the code to handle the event types that your webhook is subscribed to, as well as the `ping` event that {% data variables.product.company_short %} sends when you create a webhook. This example handles the `issues` and `ping` events.

```javascript copy annotate

const express = require('express');

const app = express();

app.post('/webhook', express.json({type: 'application/json'}), (request, response) => {

// Respond to indicate that the delivery was successfully received.

// Your server should respond with a 2XX response within {% ifversion fpt or ghec %}10{% else %}30{% endif %} seconds of receiving a webhook delivery. If your server takes longer than that to respond, then {% data variables.product.company_short %} terminates the connection and considers the delivery a failure.

response.status(202).send('Accepted');

// Check the `x-github-event` header to learn what event type was sent.

const githubEvent = request.headers['x-github-event'];

// You should add logic to handle each event type that your webhook is subscribed to.

// For example, this code handles the `issues` and `ping` events.

//

// If any events have an `action` field, you should also add logic to handle each action that you are interested in.

// For example, this code handles the `opened` and `closed` actions for the `issue` event.

//

// For more information about the data that you can expect for each event type, see "[AUTOTITLE](/webhooks/webhook-events-and-payloads)."

if (githubEvent === 'issues') {

const data = request.body;

const action = data.action;

if (action === 'opened') {

console.log(`An issue was opened with this title: ${data.issue.title}`);

} else if (action === 'closed') {

console.log(`An issue was closed by ${data.issue.user.login}`);

} else {

console.log(`Unhandled action for the issue event: ${action}`);

}

} else if (githubEvent === 'ping') {

console.log('GitHub sent the ping event');

} else {

console.log(`Unhandled event: ${githubEvent}`);

}

});

const port = 3000;

app.listen(port, () => {

console.log(`Server is running on port ${port}`);

});

To test your webhook, you can use your computer or codespace to act as a local server. If you have trouble with these steps, see [Troubleshooting](#troubleshooting).

1. Make sure that you are forwarding webhooks. If you are no longer forwarding webhooks, follow the steps in [Forward webhooks](#forward-webhooks) again.

1. In a separate terminal window, run the following command to start a local server on your computer or codespace. Replace `FILE_PATH` with the path to the file where your code from the previous section is stored.

```shell copy

node FILE_NAME

```

You should see output that says `Server is running on port 3000`.

1. Trigger your webhook. For example, if you created a repository webhook that is subscribed to the `issues` event, open an issue in your repository. You can also redeliver a previous webhook delivery. For more information, see "[AUTOTITLE](/webhooks/testing-and-troubleshooting-webhooks/redelivering-webhooks)."

1. Navigate to your webhook proxy URL on smee.io. You should see an event that corresponds to the event that you triggered or redelivered. This indicates that {% data variables.product.company_short %} successfully sent a webhook delivery to the payload URL that you specified.

1. In the terminal window where you ran `smee --url WEBHOOK_PROXY_URL --path /webhook --port 3000`, you should see something like `POST http://127.0.0.1:3000/webhook - 202`. This indicates that smee successfully forwarded your webhook to your local server.

1. In the terminal window where you ran `node FILE_NAME`, you should see a message corresponding to the event that was sent. For example, if you use the example code from above and you redelivered the `ping` event, you should see "{% data variables.product.company_short %} sent the ping event".

1. In both terminal windows, enter <kbd>Ctrl</kbd>+<kbd>C</kbd> to stop your local server and stop listening for forwarded webhooks.

Now that you have tested out your code locally, you can make changes to use your webhook in production. For more information, see "[Next steps](#next-steps)." If you had trouble testing your code, try the steps in "[Troubleshooting](#troubleshooting)."

- Make sure that your webhook uses the JSON content type, if you have a choice about what content type to use. For more information about your webhook settings, see "[AUTOTITLE](/webhooks/using-webhooks/creating-webhooks)."

- Make sure that your server is listening to the same port where smee.io is forwarding webhooks. All of the examples in this article use port 3000.

- Make sure that the path where smee.io is forwarding webhooks matches a route that is defined in your code. All of the examples in this article use the `/webhooks` path.

- Check for error messages in the terminal windows where you are running the smee client and your local server.

Once you have a server that is set up to receive webhook traffic from {% data variables.product.company_short %}, update the URL in your webhook settings. You may need to update the route that your code handles to match the path portion of the new URL. For example, if your new webhook URL is `https://example.com/github-webhooks`, you should change the route in these examples from `/webhooks` to `/github-webhooks`.

You should not use smee.io to forward your webhooks in production.