Setting up a webhook

Before you start

Make sure you have a Web1on1 admin account.

Setting up the webhook

All bots listen to Web1on1 events via a webhook. With a webhook you can tell Web1on1 to send one or more events from Web1on1 to your bot (the url your bot is connected listening on). Let's create a new webhook by following the click directions in the image below:

Creating the webhook

Adding a webhook to your organization. Webhooks are found by:
(1) Selecting Settings > <Your Organization>
(2) Selecting Integrations sidebar
(3) Clicking on + on bottom right of page.

The webhook creation page will open. Configure it by following the directions in the image below:

Web1on1 Agent UI

(1) Fill in the Webhook URL (the ngrok https url from the previous chapter),
(2) Clicking on Create Service

When we created the webhook Web1on1 did a GET request on the webhook endpoint and expects it to return a 200 OK. And it did. But how, you might ask. The answer is the ChipChat SDK does this for us. It will create the GET endpoint for us and return the 200 OK for us.

actually it does a bit more, but that is outside the scope of this project

Programmatically creating a Webhook using the API

In addition to the admin UI, you may configure a webhook through the API by creating a webhook type service, and specifying your callback url and optional secret and/or events in the params object:

Request: POST /v2/services

    "name": "MCC Webhook",
    "type": "webhook",
    "params": {
        "url": "",
        "secret": "zICWczLmAOEDvh1DiPGSHw==",
        "events": [

You are responsible for the security of the webhook endpoint. We suggest that you use HTTPS in combination with HTTP simple authentication. (e.g. https://username:password@domain.tld/path/to/webhook/)

An optional params.url.secret string may be provided for securing your callback URL; see below for details.

See the chapter on Services and Touchpoints in this guide for more information on this and other types of services.