> 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/check-if-a-user-is-a-follower.md).

# Check if a user is a follower

### Overview

The **Follower Verification Component** (identified in the interface by the technical name `check_follower`) is a conditional flow control node based on Meta's Graph API. Its main function is to perform an instant and synchronous query on Instagram's servers to validate whether a given user follows or does not follow the brand's business profile. It acts as an audience validator, allowing the creation of gamification dynamics or restricting access to automation branches based on the contact's relationship status.

### Configuration Parameters

The component's configuration requires two main pieces of data to perform the information cross-check on the social network:

* **Credential:** Dropdown menu used to select the authenticated access token for the Instagram Business account. This credential grants the necessary permission for the system to query the interaction list and the business profile database.<br>
* **User's Instagram ID (\* Required Field):** Text input field where the unique numeric identifier or dynamic variable (ex: `{{instagram_id}}`) that represents the client integrated into the flow.<br>

### Visual Builder

The graphical interface is minimalist, focusing exclusively on the API routing fields:

* **Direct Input Form:** The builder does not require complex selectors and focuses on the mandatory nature of the user identifier (`*`). Without this destination information, the node prevents the flow from being saved to avoid Meta request failures.<br>
* **Bifurcated Output Structure:** In the graphical flow editor, inserting this component changes the branch morphology, providing two physical output ports for connecting subsequent blocks:
  * Output A: **Is a follower**<br>
  * Output B: **Is not a follower**<br>

### Special Operators

The logical properties of this component handle real-time external requests and boolean conditionals:

* **Dynamic Injection Mapping:** The field *User's Instagram ID* is prepared to read global variables or payloads inherited from the flow's initial trigger (such as the DM or comment trigger). The engine processes this tag in real time before sending the validation endpoint.<br>
* **Binary Conditional Processing:** When executed, the system engine pauses the flow for milliseconds to obtain Meta's response (JSON). If Instagram's server confirms the friendship/follower link, the automation transparently routes the contact to the first branch; otherwise, it sends the user to the rejection path.<br>

### Practical Examples

The table below demonstrates classic application scenarios for this component in conversational marketing and engagement strategies:

| **Selected Credential** | **User ID (Input)** | **Meta Response (API)**            | **Triggered Output in the Flow** | **Practical Use Case**                                                                                                                                                                                                 |
| ----------------------- | ------------------- | ---------------------------------- | -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **@fictitious\_store**  | `{{instagram.id}}`  | User active on the followers list. | **Is a follower**                | The client sends a message in DM asking for a discount coupon. The system validates that they are a follower and immediately releases the promo code.                                                                  |
| **@fictitious\_store**  | `{{instagram.id}}`  | User not found on the list.        | **Is not a follower**            | The user asks for the coupon, but the bot identifies that they do not follow the page. The flow sends a friendly message: *"You don't follow us yet! Follow our profile and type the word again to unlock the prize."* |
| **@fictitious\_brand**  | `{{instagram.id}}`  | User active on the followers list. | **Is a follower**                |                                                                                                                                                                                                                        |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hablla.com/hablla-docs-en/automation-flows/all-components/instagram-components/check-if-a-user-is-a-follower.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.