> For the complete documentation index, see [llms.txt](https://docs.hablla.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hablla.com/hablla-docs-en/automation-flows/all-components/instagram-components/instagram-question.md).

# Instagram Question

### Overview

The **Instagram Question Component** is an interaction node focused on capturing data, qualifying leads, and conducting structured conversations within the direct messages (DM) environment. Its main function is to send a question to the user and keep the flow in a waiting state (*standby*) until a valid response is entered. Due to layout limitations or the API of this specific channel, the component works in a strictly linear way through text input boxes, not offering support for quick-reply buttons or interactive lists.

### Configuration Parameters

The node configuration determines the dialog behavior and the destination of the strings captured by the chatbot:

* **Type:** Restricted and standardized field in the mode `Text`. Indicates that the entire interaction of the block will depend on a response typed manually by the user in the chat.<br>
* **Message:** Text box where the administrator types the question statement (e.g., "What is your best email?").<br>
* **Has Variable (Toggle Key - Toggle Switch):** When enabled, it allows the platform to save what the customer typed in a memory key for later use in the automation.<br>
* **Variable (\* Required if active):** Input field to define the name of the container that will receive the response (the suggested visual default is `response`).<br>
* **Response Target:** Dropdown menu to synchronize the received input directly with the customer's record in the internal CRM. Supports fields such as: `Address`, `CSAT`, `custom_field` (custom field), `Email`, `Name` and `NPS`.<br>
* **Accept response&#x20;*****(*****&#x20;Required Field):** The data validator (*data validation*) that defines the format the response must have for the flow to continue. The menu offers filters such as: `Text`, `Number`, `Valid Data`, `Phone number`, `Email` and `Location`.<br>

### Visual Builder

The builder interface prioritizes quick completion and focuses on strict control of the syntactic validation of received messages:

* **Simplified Linear Form:** Due to the absence of complex interactive media structures (such as buttons and native lists), the builder displays a clean top-to-bottom layout, where the asterisk (`*`) reinforces the obligation to define a response acceptance criterion to save the node.<br>
* **Hidden Repetition Behavior:** In the flow editor, this component has a traditional output port. However, the platform's Larvic engine generates an automatic loop: if the user types something that does not pass the selected filter in *Accept response* (e.g.: typing regular text when the field requires a `Email`),<br>

### Special Operators

The logical processing properties of this component control the integrity of the entered data before integrating it into the profiles:

* **Syntactic Validation by Regular Expression (Native Regex):** When configured to validate specific formats (such as `Email` or `Phone number`"), the internal engine analyzes whether the character structure meets global patterns (presence of `@` and valid domains in the email, for example). If the input is invalid, the flow blocks saving to the CRM fields to prevent corrupted data.<br>
* **String Interpolation in the Message:** The text box of the field *Message* accepts the use of double braces `{{...}}` to retrieve data that the automation already has about the contact, making the question more human and personalized (e.g.: "Perfect, `{{name}}`! Now enter your phone number with area code:".<br>

### Practical Examples

The table below demonstrates classic application scenarios for this component to safely guide automated support on Instagram:

| **Selected Type** | **Configured Message**                     | **Response Target** | **Accept response** | **Practical Use Case**                                                                                                       |
| ----------------- | ------------------------------------------ | ------------------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| `Text`            | "What is your full name?"                  | `Name`              | `Text`              | Capture the name of the user who just interacted with the bot and update their record on the platform.                       |
| `Text`            | "Enter your email to receive the catalog:" | `Email`             | `Email`             | Capture the email for marketing campaigns. If the user types any text without an email format, the system repeats the block. |
| `Text`            | "Please provide a contact phone number:"   | `custom_field`      | `Phone number`      |                                                                                                                              |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hablla.com/hablla-docs-en/automation-flows/all-components/instagram-components/instagram-question.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.