Skip to main content

What types of content are supported by the Builder?

  • Updated

Index:

  1. Text
  2. Quick Reply
  3. Image
  4. Carousel
  5. Menu
  6. Typing
  7. Audio
  8. Video
  9. Document
  10. Send Location
  11. Request Location
  12. Web Link
  13. HTTP Content

Within any content block, it is possible to define which messages will be sent from the bot to the client. BLiP supports any type of content available in the channels connected to the platform.

In the Builder, to add content to a block, simply select the icon corresponding to the desired content. The most commonly used types (text, quick reply, image, carousel, and menu) have specific icons and can be easily chosen. Other types of content can be found through the "more content" icon ("..."), as shown in the image below.

 

1.png

 

See below the details of all content types supported by the Builder. For more details on all content types supported by the platform, see the Content-Types section in the BLip documentation.

  • Text

2.png

Sends a text message (https://docs.blip.ai/#plain-text) to the user.

  • Quick Reply

3.png

Sends a quick reply message (immediate scope responses https://docs.blip.ai/#quick-replies) to the user.

  • Image

4.png

Sends an image message (https://docs.blip.ai/#images) to the user.

  • Carousel

5.png

Sends a carousel-type message (https://docs.blip.ai/#carousel) to the user.

  • Menu

6.png

Sends a message with menu-type content (https://docs.blip.ai/#menu) to the user.

  • Typing

7.png

Shows the user that a message is being typed, as in regular conversations in messaging apps (https://docs.blip.ai/#chat-state).

  • Audio

8.png

Sends a message with audio content (https://docs.blip.ai/#audio) to the user.

  • Video

9.png

Sends a message with video content (https://docs.blip.ai/#video) to the user.

  • Document

10.png

Sends a message with document-type content (https://docs.blip.ai/#document-files) to the user - for example, a PDF.

  • Send Location

11.png

Sends a message with a map pointing to a specific geographic location (https://docs.blip.ai/#send-location) to the user.

  • Request Location

12.png

Sends a message requesting the user to share their location (https://docs.blip.ai/#request-location)

  • Web Link 

13.png

 

Sends a web link (https://docs.blip.ai/#web-link) to the user.

  • HTTP Content

14.png

A special content type that enables dynamic data generation.

In some situations, content creation happens dynamically. For example, a list of products depends on the number of products in stock at a given moment. In these cases, the use of HTTP Content becomes necessary.

With this type, the responsibility for generating content is transferred to an API. Currently, Quick Reply, Carousel, and Menu are accepted as dynamic content.

Simply fill in the URL that Blip should use to fetch the content. To know the correct format for each Blip type, consult the documentation.

Note: The URL for HTTP content must support a GET request.

  • User Input

15.png

In addition to sending content, the bot may need to request input from the user. For this purpose, there is User Input content. Through this content, it is possible to pause the execution of the state machine and wait for information that the client should send.

It is possible to store the received content in a variable in any User Input content. To do this, simply define the variable name.

 

16.png

Furthermore, it is also possible to validate user input. Just check the "Validate user input" option, define the rule, and an error message.

The rules available for validating user input are:

 

Rule Description
Text Validates if the user input is text.
Date Validates if the user input represents a date.
Number Validates if the user input is a number.
Regex Validates if the user input matches a regex pattern.
Type Validates if the user input corresponds to a specific Blip type. For example, image/jpeg checks if the user sent an image.

If the rule defined in a User Input is not satisfied, the user will receive the defined error message.

 

Notes:

  • A block can contain 0 (zero) or 1 (one) User Input.
  • In the vast majority of cases, every block will contain a User Input.
  • If a block does not have User Input, the state machine processing will lead the client to the block that does.

 

For more information, visit the discussion on the subject in our community or the videos on our channel. 😃

Related articles