Web app map (UI → documentation)
Lyntaris ships as a Flowise-based web application. This guide is written so operators and builders can use the product end-to-end: canvases, channels, knowledge bases, provider integrations, and APIs. Engineering-only material (exact JSON wire formats, C# types, internal daemon names) stays in your organization’s integration engineering documentation; everything you need to click, configure, and integrate from the browser belongs here.
Use the tables below to jump from a URL path (as shown in the browser) to the right chapter.
Builders & canvases
| Path | What it is | User documentation |
|---|---|---|
/agents |
List of Agentflow V2 agents | Agents (V2 Agent Canvas) |
/v2/agentcanvas / /v2/agentcanvas/:id |
V2 visual builder | Agents (V2 Agent Canvas) and V2 node reference (detailed pages in the sidebar) |
/realtime-v1/agentcanvas / .../:id |
Voice / realtime builder | Realtime Agent Canvas and linked Realtime node pages in the table of contents |
/agentcanvas / /agentcanvas/:id |
Older sequential agent canvas (still in app) | Prefer V2 for new work; patterns overlap with Agents (V2 Agent Canvas) |
Supported builders in this book: Agentflow V2 (/agents, /v2/agentcanvas) and Realtime v1 (/realtime-v1/agentcanvas). All tutorials and API examples assume you build and ship flows from those canvases.
Knowledge, RAG, and content
| Path | What it is | User documentation |
|---|---|---|
/vector-databases (+ document sub-routes) |
Document stores & vectors in UI | Vector Databases (Document Stores) |
/document-stores (+ sub-routes) |
Alternate entry to store detail | Vector Databases (Document Stores) |
/sitemap |
Site map, crawl, Always Fresh, prompts | Sitemap & content pipeline |
/tools |
Tool / integration catalog in UI | Integrations — Tools and What's available in Lyntaris |
Channels, orchestration, and speech
| Path | What it is | User documentation |
|---|---|---|
/orchestrator |
Per-pipeline persona, tool hints, media | Orchestrator |
/prompting |
Prompting / analytics-related views (varies by build) | Orchestrator, Sitemap & content pipeline (domain PROMPT.json), Monitoring if tied to analytics |
/speech |
STT/TTS providers and rehearsal assets | Speech (STT/TTS) |
/pipelines, /pipelines/custom, /pipelines/web-speech, /pipelines/vr |
Pipeline selection and scoped resources | Orchestrator (header pipeline selector), Speech, Realtime Agent Canvas for voice/VR stacks |
/kiosk, /webtext, /web-speech, /call-center, /robot, /vr, /mail, /watsapp |
Channel- or product-specific consoles | Orchestrator, Speech, Embed Chat Widget, Realtime; messaging: WhatsApp, SMS / Telnyx, Mail |
Execution, monitoring, and data ops
| Path | What it is | User documentation |
|---|---|---|
/executions |
Execution history | Turn Executions, Realtime Executions |
/monitoring |
Live apps and usage | Monitoring |
/analytics |
Embedded analytics console | Monitoring — Analytics console |
/analytics/prompting |
Redirects to Orchestrator | Orchestrator |
/data-processing |
Data-processing jobs and automations | Data Processing |
/logs |
Server / audit logs (if enabled) | Monitoring |
/files |
Uploaded files manager | Uploads |
Security, credentials, and API access
| Path | What it is | User documentation |
|---|---|---|
/credentials |
API keys and connections | Credentials |
/variables |
Flow variables | Variables |
/apikey |
API keys for prediction/embed | Embed Chat Widget, Customer integration (HTTP API) |
/workspaces, /workspace-users/:id |
Multi-tenant workspaces | Workspaces |
/users, /roles, /workspace-users/:id, /login-activity |
Users, roles, invitations, audit | Workspaces (creating roles, inviting users, login activity) |
/account |
Profile / account settings | Workspaces (account admin vs invited users) |
/sso-config, /sso-success |
Enterprise SSO setup and callback | Workspaces; IdP-specific wiring stays in deployment docs |
Evaluations & quality
| Path | What it is | User documentation |
|---|---|---|
/evaluations, /evaluation_results/:id, /evaluators |
Eval runs and evaluators | Evaluations |
/datasets, /dataset_rows/:id |
Evaluation datasets | Evaluations |
Lyntaris-specific surfaces
| Path | What it is | User documentation |
|---|---|---|
/lyntclaw |
LyntClaw chat, automations, browser | LyntClaw |
/rts-server |
Render-streaming / RTS controls (if shown) | Deployment-specific; see your engineering docs for WebRTC stacks—Embed and Realtime for related product behavior |
Streaming, sync, and external HTTP
| Topic | User documentation |
|---|---|
| Token streaming from APIs | Streaming Responses |
| Asset updates to clients | Asset Sync and Notifications |
| HTTP prediction, queue, cookies automation | Customer integration (HTTP API) |
Provider & node integrations (palette → docs)
Anything you can add from the node palette (chat models, embeddings, document loaders, vector stores, tools, utilities) should have a user-facing page under Integrations:
- Chat models → Chat Models
- Document loaders → Document Loaders
- Embeddings → Embeddings
- Vector stores → Vector Stores
- Tools & MCP → Tools
- Utilities (If/Else, variables, sticky notes, custom JS) → Utilities
- Third-party platforms (WhatsApp, mail, Zapier, …) → Integrations overview
If your build exposes a node whose guide is missing or outdated, that is a documentation gap to close in this book—not something end users should need internal repos for.
How this relates to the Flowise source tree
The running UI is built from your Lyntaris Flowise fork (for example Flowise-main). When the app adds a new route or node category, add or update the matching row here and the linked chapter so this map stays the single index from browser to help.
Documentation coverage (honest checklist)
Well covered for day-to-day use: Agentflow V2 list and canvas (/agents, /v2/agentcanvas), realtime voice canvas (/realtime-v1/agentcanvas), V2 and realtime node chapters, Orchestrator (/orchestrator), Speech (/speech), Vector databases / document stores, Sitemap, Data Processing, Executions (/executions), Monitoring fleet and costs (/monitoring), LyntClaw, Credentials, Variables, API keys, Embeds & customer HTTP API, Streaming, Asset sync, Uploads, Evaluations & datasets, Workspaces with users/roles/invites, and the Integrations tree (models, loaders, embeddings, vector stores, tools, utilities, selected 3rd-party apps).
Partially covered (enough to orient, not every sub-screen): Analytics (/analytics)—purpose and split from Monitoring are documented; deep feature-by-feature analytics UI may still need screenshots per release. Channel shortcuts (/kiosk, /call-center, /mail, /watsapp, …)—many redirect into Orchestrator tabs; see Orchestrator and channel integration pages rather than separate “placeholder” guides. Custom web assistant (/webtext, /pipelines/custom)—overlaps with Embed and Orchestrator pipeline selection; a dedicated end-to-end “Wonder Widget” tutorial may still be expanded.
Known ongoing gap: The node palette in code can contain more integrations than this book has individual pages for. The Integrations section should be kept in sync with what your build actually ships; anything in the UI without a page is documentation debt, not something operators should need internal repos for.