How Data Flows
Momen is a full-stack no-code platform. Data drives the UI, backend Actionflows, and AI features — not just what components display.
Your app is a data pipeline network. UI components, Actionflows, and AI agents are nodes on that network.
The model has four stages: Storage, Production and update, Transfer and distribution, and Consumption and processing.
Storage
Core app data lives in two places:
Built-in relational database
High-performance PostgreSQL-backed storage. Business entities (orders, posts, etc.) live in tables linked by one-to-one, one-to-many, and many-to-many relations. The account table holds system users. Data here is the single source of truth for all clients.
Third-party API data sources
External systems (ERP, weather APIs, etc.) are first-class providers. Their data joins the same pipeline as structured virtual data.
Related:
Production and update
Data enters the pipeline through:
Frontend interaction
Users submit forms or trigger database operation actions — the most common write path (Mutation).
Backend automation
Scheduled jobs or webhooks (e.g. payment success from Stripe) run Actionflows without user interaction.
AI and operations
- AI: agents summarize or analyze, then write structured results to the database.
- Ops: admins use online tables or Import and Export Data.
Related:
Transfer and distribution
Data source pipelines
Declare tables or APIs as data sources — pipes that pull data into the runtime (Query):
- Frontend: page or list component queries
- Backend: database query or API nodes in Actionflows
Variables and parameters
Search keywords, navigation IDs, and flow intermediates use client variables, page variables, Actionflow variables, and parameters instead of the database.
Related:
Consumption and processing
| Node type | Role |
|---|---|
| View nodes | UI components display data via databinding |
| Logic nodes | Actionflow nodes execute rules (discount, validation) and may write new data |
| AI nodes | LLM context from structured data + user prompts |
Databinding and tracing
Nodes connect explicitly via databinding:
current account.username— logged-in user’s usernameactionflowname.variable.var1— Actionflow variable field in backend logicqueryName.fieldName— page query field in the UI
Use Bird’s-eye View to inspect dependencies across tables, APIs, Actionflows, and variables.