> 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-comment.md).

# Instagram Comment

### Overview

The **Instagram Comments Trigger** is an input node (*inbound trigger*) based on public engagement events. Its main function is to listen for interactions left on the account's posts (such as feed posts and Reels) and trigger an automated support flow immediately when a user leaves a comment. It works as a direct conversion bridge, allowing you to respond to the user automatically or start a lead qualification journey in private.

### Configuration Parameters

The trigger configuration maps the account's social monitoring using the following criterion:

* **Channel:** Drop-down menu used to select which Instagram Business Account linked to the dashboard will be monitored by this automation node. It queries Meta's Graph API to list the eligible profiles.<br>

### Visual Builder

The builder interface was designed to focus on simplicity and the quick inheritance of the source channel:

* **Unified Channel Selector:** The drop-down centralizes the choice of the institutional account. Once the option is selected, the system begins listening to comment webhooks from all active posts associated with that profile.<br>
* **Inputless Start Node:** In the visual flow editor, this component is positioned at the initial left root of the screen. It has no input connectors, since the generating stimulus is entirely external (the user's comment on a social network post).<br>

### Special Operators

The logical properties of this component manage the tracking of public content and the opening of the private messaging channel:

* **Post Metadata Capture (Engagement Payload):** At the moment the comment is generated, the trigger engine captures a complete data object containing the **Post ID**, the **Comment Text**, the **Instagram Username** of the author and the **Comment ID**. These variables become available for use in subsequent blocks (e.g.: to validate whether the user commented a specific keyword, such as "WANT").<br>
* **Private Routing (DM Injection):** The Meta API allows the system, starting from a valid public comment, to open a private conversation channel (DM) with the user. The engine of this component prepares the contact to receive the first message in the flow directly in their personal inbox, moving the interaction from the public space to the private environment for sales or support.<br>

### Practical Examples

The table below shows classic application scenarios for this trigger to boost conversational marketing strategies on Instagram:

| **Selected Channel**   | **User Action on the Post**     | **Subsequent Conditional Filter**          | **Practical Use Case**                                                                                                                       |
| ---------------------- | ------------------------------- | ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------- |
| **@fictitious\_brand** | Commented: "I really liked it!" | *None (Any comment)*                       | Send an automated DM thanking them for the engagement and offering a welcome discount coupon.                                                |
| **@fictitious\_brand** | Commented the word: **WANT**    | `Comment Text` equals `WANT`               | Immediately trigger a DM sending the link to the e-book or catalog promised in the post caption (Keyword Campaigns).                         |
| **@fictitious\_store** | Commented: "How much is it?"    | `Comment Text` contains `value` or `price` | Start a private flow by automatically sending the product price list and asking whether the customer would like to speak with a salesperson. |


---

# 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-comment.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.