[Extension] How to create webhooks in Blip to send bot data to external systems

1. Introduction

2. Features

3. Installation

4. How to create and configure a webhook

5. Usage examples

6. Tips

7. Support

Brief description: Create custom webhooks in Blip to automatically send contacts, messages, and events from your chatbot to CRMs, spreadsheets, and other external systems via HTTP.

Introduction

The Webhook Manager extension creates custom webhooks in Blip to automatically send your bot’s data to external systems. Whenever a contact is updated, a message flows in the conversation, or an event is recorded, the extension triggers an HTTP request to the URL you define, with the content in the format expected by the target system.

For example, you can send each new WhatsApp contact to your CRM as soon as they appear in the conversation, keeping the external database synchronized without manual work. The URL and request body accept Liquid, so you can build the payload with fields from the contact, message, or event.

Features

• Creation of multiple webhooks, each with its own configuration.

• Three types of sending: contacts, messages, and conversation events (event tracking).

• HTTP methods POST, PUT, and PATCH.

• Custom headers for authentication, such as token or API key.

• Dynamic URL and body with Liquid, using fields from the contact, message, or event.

• Option to not send the request when the rendered body is empty.

• Editing and deletion of already registered webhooks.

Supported on the following channels: all channels available on the Blip platform.

Note: Webhook Manager sends data one-way only. The external API response does not return to the bot flow.

Installation

Attention: this is a paid extension, developed by Wiv.

1. Access the Webhook Manager on the Blip Store and activate the extension.

2. Install the extension on the Router or on the bot that processes the channels used in your operation. The extension will start receiving contacts, messages, and events from this bot.

3. Open the bot where you installed the extension, click the three dots in the upper right corner, and select Webhook Manager. The management screen for registered webhooks will open.

On this screen, you can create new webhooks, edit existing configurations, or delete those you no longer use.

How to create and configure a webhook

Click Create new webhook. The configuration screen opens with a default webhook ready for you to adjust.

Configure the following fields:

Types of sending

Select which information the webhook will send. You can check one or more types:

• Contact: contact data, such as identity, name, email, phone, and extra fields.

• Message: message data, such as id, type, sender, recipient, content, and metadata.

• Events: event tracking data, such as identity, category, action, and extra fields.

URL

In the URL field, enter the endpoint that receives the data, provided by the external system. The field accepts Liquid, so you can create dynamic URLs based on contact or conversation fields. For example:

Method

In Method, select the HTTP method for the request: POST, PUT, or PATCH. Follow the target system’s documentation. Generally, use POST to create a record, PUT to replace an entire record, and PATCH to update part of a record.

Header

Use the header to send authentication or identification data, such as a token or an API key. Click Add new header key and fill in the key and value. Header keys accept only letters, hyphens, and underscores. A common example:

Request body

In the Body field, define the content sent to the URL. The body accepts Liquid, which allows inserting variables, contact fields, and conditional logic. Three objects are available according to the type of sending: contact, message, and tracking. For example, to send contact data:

Check the option If the body is empty, do not perform the request when the body depends on some condition. If the logic results in an empty body, the extension does not send the request, avoiding unnecessary calls to the external system.

After filling in the fields, click Save webhook.

The saved webhook appears in the list of registered webhooks, where you can edit or delete it whenever needed. From then on, it sends Blip information to the defined external system.

Usage examples

A common use of the Webhook Manager is integrating the bot with a CRM or an external contact database, such as HubSpot, RD Station, Salesforce, Airtable, or a spreadsheet.

To register new contacts, create a webhook of type Contact, enter the destination API URL, choose the POST method, and build the body with the necessary fields. This way, whenever a contact is identified, the data automatically goes to the external system.

To update existing contacts, use the PUT or PATCH method, depending on the destination API, and send the fields that change. This configuration keeps the external system updated with the latest contact information in Blip.

Tips

• Test the destination URL with a tool like webhook.site before using it in production to check the format that reaches the external system.

• Configure first in a staging bot and, after validating the behavior, replicate it in the production bot.

• Make sure the fields used in Liquid exist in the contact or conversation context. Nonexistent variables generate incomplete sends.

• Confirm with the destination API documentation which method to use and which authentication headers to send.

Support

If you have questions about configuration or problems with the extension, contact Wiv’s support team at support@wiv.com.br.

Need more help? Explore our content at Blip Academy or Blip Community, watch tutorials on our YouTube channel, or get your questions answered in our support channel 😃