Application Integration Points in the Flowlu Interface
One of Flowlu’s key strengths is the ability to integrate custom applications directly into the main areas of the platform interface. Applications appear in predefined locations called integration points. Each integration point defines where and how an application is rendered inside Flowlu.
Header
An application can add a single icon or button to the top navigation bar. This element can be used to open the application interface, display status information, or show a small dropdown with actions or notifications.
To avoid interface clutter, only one header element is allowed per application. The header icon becomes visible automatically after installation and is shown only to users who have access to the application.
Main menu
Applications can add navigation items to the left-hand menu. This can be either:
-
a top-level menu item, or
-
an item inside an existing section, such as CRM.
Selecting the menu item opens the application’s main interface in the central workspace. Menu visibility is handled automatically: only users with access to the application can see its menu items. Changes take effect immediately after installation or removal.
Tabs
Applications can add custom tabs to existing entity pages, such as CRM deals, tasks, projects, or CRM accounts. For example, an application may add an Analytics tab to a deal page to display additional data.
The manifest defines the target entity type and assigns a unique identifier to each tab. Tabs are displayed only when the application is installed and the user has access. Duplicate tab identifiers for the same entity type are not allowed.
Cards and widgets
Applications can display widgets as informational blocks in various parts of the interface, including entity pages, task boards, dashboards, and report views.
Widgets may vary in size and content, from simple indicators to larger data blocks. Their placement and behavior are defined in the manifest. In most cases, users can control widget visibility, such as hiding a widget or adding it to their personal dashboard.
Reports
Applications can register custom report types within the Flowlu reporting module. These reports may use external data or custom calculations provided by the application.
After installation, the report type becomes available to users with the appropriate permissions. Data formats are standardized so Flowlu can render tables and charts consistently. Access to reports follows the same role-based permission rules as native reports.
Dashboard
Applications can add widgets to the user dashboard to display high-level summaries, metrics, or visualizations.
The manifest defines the widget type and size. Users can enable or disable these widgets in their dashboard settings. Multiple application widgets can coexist without affecting platform performance.
Mobile application
Flowlu provides a mobile client, and applications can integrate with it if mobile support is declared in the manifest. Supported applications may add menu items or views in the mobile interface.
If an application does not support mobile usage, its elements are hidden or marked as desktop-only. Developers are encouraged to provide at least basic responsive support to ensure broader usability.
Communications module (optional)
Applications can integrate with the Flowlu Communications module to extend messaging and communication features. This may include adding support for additional communication channels or integrating external communication services.
Such integrations require additional configuration and follow stricter security requirements due to the sensitive nature of communication data. Applications integrating with the Communications module must comply with all platform security and permission rules.
How integration points work
Integration points are handled modularly. When an application is installed, Flowlu reads the relevant sections of the manifest and automatically embeds the application into the appropriate areas of the interface.
This design allows Flowlu to introduce new integration points over time without changes to the core architecture. Applications can support new locations by updating their manifest when additional integration options become available.
