> 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/hablla/feed-posts.md).

# Feed posts

### Overview

The **Internal Feed Publishing Component** is an action node focused on corporate communication, team engagement, and information sharing. Its main function is to automate the sending of structured content directly to the timeline or notice board (*Feed*) visible to users of the platform. It allows important notifications to be centralized throughout the automation journey, eliminating the need for manual posting for recurring events.

### Configuration Parameters

The component's configuration defines the visual format of the post, its categorization, and the text content that will be shown to employees:

* **Operation:** Static and restricted field of the component. It only supports the action of `Create`, establishing that the purpose of this block is solely the insertion of new records into the system timeline.<br>
* **Type:** Determines the media structure that will accompany the publication. Available options include:
  * `Text`: Purely textual posts.<br>
  * `Image`: Delivery focused on visual/graphic files.<br>
  * `Video`: Sharing audiovisual content.<br>
  * `Text with image`: Mixed structure containing text body and visual attachment.<br>
  * `Text with video`: Mixed structure containing text body and video attachment.<br>
* \_*Title (* Required Field):\_\* The header or main subject of the post. Supports static text entry or the injection of dynamic flow tags.<br>
* \_*Description (* Required Field):\_\* The main body of the message, where the information the company wants to convey is detailed.<br>
* **Action:** Dropdown menu that functions as a classifier or context marker (Tag) for the post, allowing users to filter the board. Categories include:
  * `Achievement`, `New`, `Highlight`, `Alert`, `Announcement` and `Celebration`.<br>

### Visual Builder

The builder dynamically adapts the form input fields based on the user's combination of selectors:

* **Required Fields with Prior Validation:** The asterisk indicators (`*`) in the fields of *Title* and *Description* block the node execution if the flow tries to pass through them without valid content, preventing blank posts on the corporate board.<br>
* **Responsive Media Behavior:** When selecting mixed formats in the field *Type* (such as `Text with image`), the interface enables additional fields for file upload or insertion of CDN links to render the attached media.<br>

### Special Operators

The logical properties of this component handle visibility, indexing, and concurrency control in the timeline:

* **Dynamic Indexing by Category:** The selector *Action* injects hidden metadata into the feed database. This allows the system to organize the posts generated by automation into specific viewing channels (e.g., if categorized as `Alert`, the platform can trigger an additional push notification for users).<br>
* **Variable Rendering:** The field of *Description* accepts string interpreters. This means it is possible to mix fixed text with variables collected in the flow (e.g., "The employee `{{name}}` just closed a new account!").<br>

### Practical Examples

The table below demonstrates classic application scenarios for this component to generate automated notifications based on events:

| **Selected Media Type** | **Category (Action)** | **Originating Flow Trigger**                        | **Practical Use Case**                                                                                                                            |
| ----------------------- | --------------------- | --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Text`                  | **Alert**             | **Cron** *(Every Monday at 08:00)*                  | Automatically publish a reminder on everyone's board reinforcing the opening of the weekly general meeting.                                       |
| `Text with image`       | **Achievement**       | **Transfer Component** *(Sale Closing)*             | As soon as the salesperson finishes the closing process, the flow generates a celebratory post with the salesperson's name and the client's logo. |
| `Text with video`       | **New**               | **Event Trigger** *(Person Created - New Operator)* | When a new user is registered in the system, the flow publishes an institutional onboarding video welcoming the team.                             |


---

# 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/hablla/feed-posts.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.