What types of content does the Builder support

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

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

Keep reading to find out details on all types of content supported by Builder. For more information on all types of content supported by the platform see the Content-Types section in the Blip documentation.

• Text: send a text message (https://docs.blip.ai/#plain-text) to the user.
• Quick Reply: send a quick reply message (replies of immediate scope https://docs.blip.ai/#quick-replies) to the user.
• Image: send an image message (https://docs.blip.ai/#images) to the user.
• Carousel: send a carousel-type message (https://docs.blip.ai/#carousel) to the user.
• Menu: send a message with menu-type content (https://docs.blip.ai/#menu) to the user.
• Typing: shows the user that a message is being typed, just like in common conversations in messaging applications (https://docs.blip.ai/#chat-state).
• Audio: send an audio message (https://docs.blip.ai/#audio) to the user.
• Video: send a message with video content (https://docs.blip.ai/#video) to the user.
• Document: send a message with document-type content (https://docs.blip.ai/#document-files) to the user - PDF, for example.
• Send location: send a message with a map that points to a specific geographic location (https://docs.blip.ai/#send-location) to the user.
• Request location: sends a message with a request to share the user's location. (https://docs.blip.ai/#request-location)
• Web Link: send a web link (https://docs.blip.ai/#web-link) to the user.

• HTTP content: type of special content that allows the generation of dynamic data.

In some situations, the creation of content happens dynamically. A product list, for example, depends on the quantity of products in stock at any given time. Thus, it is not possible to create a carousel in Builder with all products available throughout the day. In such cases, it is necessary to use HTTP Content.

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

Just fill in the URL that Blip should use to search for the content. For the correct format for each type of Blip, consult the documentation.

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

• User input

In addition to sending content, the bot may need to request some input from the user - in this case, there is the User input content. Through this content, it is possible to stop the execution of the state machine and wait for some information that must be sent by the customer.

It is possible to store the received content in any user input type in a variable. To do this, simply define the name of the variable.

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

The rules available for validating user input are:

Rule	Description
Text	Validates whether the user input is text
Date	Validates whether the user input represents a date
Number	Validates whether the user input is a number.
Regex	Validates whether the user input corresponds to a regex pattern.
Type	Validates whether the user input corresponds to a specific type of Blip. Example: image / jpeg checks whether the user has uploaded an image.

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

Comments:

• A block can contain 0 (zero) or 1 (one) User Input.
• In most cases, each block will contain a User Input.
• If a block does not have User Input, the processing of the state machine will take the user to the block with User Input.