Where the engine reads work
FlowIQ never asks people to log what they did — it reads the systems where work already happens. Each connector feeds the ingestion loop that turns raw activity into scored signals.
The configure → ingest loop
Point a connector at a workspace and set its mode (live, mock, or off).
The engine pulls artifacts on a schedule — MRs, tickets, meetings, time.
Each artifact becomes a signal judged against the role rubric and goals.
Connected sources
7 sourcesOdoo
Org tree, roles, JDs, reporting lines
Jira
Tickets, sprints, story points, cycle time
GitLab
MRs, commits, reviews — engine reads diffs
Apache DevLake
Unified GitLab+Jira+CI/CD via Grafana proxy — PRs, issues, deployments, DORA
Google Calendar
Meeting load, focus time, collaboration — link via Google SSO
Gmail
Threads, response time, collaboration graph — link via Google SSO
Kimai
Time entries (optional signal source)