Analytics
/analytics is the realtime analytics console for payloads uploaded by Unity after each conversation.
API base paths
Both are supported:
/api/v1/analytics/analytics(non-versioned alias)
Endpoints
POST /api/v1/analyticsGET /api/v1/analytics/storage?restype=container&comp=listGET /api/v1/analytics/storage/<path>PUT /api/v1/analytics/storage/<path>DELETE /api/v1/analytics/storage/<path>
Ingestion payload (POST /api/v1/analytics)
{
"Caller": "38640123456",
"Pipeline": "kiosk",
"BaseName": "call_2026_03_09_001",
"TimestampUtc": "2026-03-09T10:15:00Z",
"Html": "<html>...</html>",
"Markdown": "# Conversation",
"FunctionCallJson": "{\"tool_calls\":[...]}",
"Logs": "trace logs",
"AudioOpusBase64": "<base64>",
"KnowledgeGaps": [],
"Conversations": [],
"Usage": {
"TotalInputTokens": 100,
"TotalOutputTokens": 80,
"TotalTokens": 180,
"TotalCostUsd": 0.01
}
}
Created response:
{
"ok": true,
"pipeline": "kiosk",
"baseName": "call_2026_03_09_001",
"files": ["kiosk/call_2026_03_09_001.html"]
}
Storage backend config
ANALYTICS_STORAGE_PATH=/home/node/.flowise/analytics-data
ANALYTICS_AUTH_SECRET=optional-bearer-secret
- If
ANALYTICS_AUTH_SECRETis set, API requiresAuthorization: Bearer <secret>. - Storage routes are also allowed for authenticated Flowise UI sessions.
UI behavior
The analytics tab supports:
- pipeline-based filtering
- artifact preview/download (HTML, Markdown, JSON, logs, audio)
- refresh and cleanup workflows
- issue/note maintenance in the same view