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.

• Type: Determines the media structure that will accompany the publication. Available options include:

  • Text: Purely textual posts.

  • Image: Delivery focused on visual/graphic files.

  • Video: Sharing audiovisual content.

  • Text with image: Mixed structure containing text body and visual attachment.

  • Text with video: Mixed structure containing text body and video attachment.

• _Title ( Required Field):_* The header or main subject of the post. Supports static text entry or the injection of dynamic flow tags.

• _Description ( Required Field):_* The main body of the message, where the information the company wants to convey is detailed.

• 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.

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.

• 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.

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

• 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!").

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.