Supported Integration Points
Flowlu lets apps integrate directly into the main areas of its interface. Apps appear in predefined locations called integration points, and each one defines where and how an app is rendered inside Flowlu. The available points are below.
Header
An app can add a single icon or button to the top navigation bar, used to open the app's interface, show status information, or display a small dropdown of actions or notifications. To keep the interface uncluttered, only one header element is allowed per app. The icon appears automatically after installation, with a tooltip on hover, and is shown only to users who have access to the app.
Main menu
An app can add navigation items to the left-hand menu, either as a top-level item or as an item inside an existing section such as CRM. Selecting the item opens the app's interface in the central workspace.
Menu visibility is handled automatically: only users with access to the app see its items. The menu updates dynamically, so installing an app adds its item immediately and removing the app takes it away, with no need to restart the portal.
Tabs
An app can add custom tabs to existing entity pages, such as CRM opportunities, tasks, projects, or contacts. For example, an app might add an "Analytics" tab to an opportunity page to show additional data.
The manifest defines the target entity type and assigns a unique identifier to each tab. A tab appears only when the app is installed and the user has access to it.
Important: the system monitors uniqueness — two different apps cannot add tabs with the same name to one object; this is checked during installation.
Widgets (cards)
An app can display widgets (cards), informational blocks placed in various parts of the interface: entity pages, task boards, dashboards, and report views. Widgets range in size and content, from small indicators to larger data blocks. Their placement and content are defined in the manifest's cards section.
The platform provides an API to update widget content in real time, so an app can push new data and have a chart or figure redraw without a reload.
For example, a weather integration might show a "Current Weather" card inside the portal, and a finance app might show a card with the current balance or currency rates. In most cases users can control widget visibility, hiding a widget or adding it to their personal dashboard.
Reports
An app can register a custom report type in the Flowlu reporting module, using external data or its own calculations. After installation, the report type becomes available to users with the appropriate permissions.
When a report is built, Flowlu requests the data from the app via its API. The app returns standardized JSON (tables and datasets) and defines, through a schema, how the data should be visualized, so Flowlu can render tables and charts consistently. Access follows the same role-based rules as native reports.
Dashboard
An app can add widgets to the user dashboard to show high-level summaries, metrics, or visualizations. The manifest defines the widget's type and size, and provides data for display. Users enable or disable these widgets in their dashboard settings, and multiple apps' widgets can run together without affecting performance. Flowlu keeps them updated through periodic polling or push updates from the app.
Mobile application
Flowlu has a mobile client, and apps can integrate with it when mobile support is declared in the manifest. A supported app can add a navigation item or a screen in the mobile interface, or a widget on the mobile dashboard.
Mobile integration is implemented through a WebView: Flowlu opens the app's responsive web page inside the mobile client and passes context such as the user token. If an app doesn't support mobile use, its elements are hidden or marked as desktop-only. We recommend providing at least basic mobile support so your app reaches the widest audience.
Communications module
An app can integrate with the Flowlu Communications module to extend messaging and communication features, for example by adding support for additional channels or connecting external communication services.
These integrations need extra configuration and follow stricter security requirements, given the sensitive nature of communication data. An app 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 app is installed, Flowlu reads the relevant sections of its manifest and automatically embeds the app in the right places. This design lets Flowlu add new integration points over time without changes to the core architecture; apps adopt a new location simply by updating their manifest once it's available.
