Connectors
Connectors let Genly securely connect business applications without changing how teams already work—syncing content and permissions to power search, answers, and governed operations.
1. What connectors do
Connectors establish controlled data paths between Genly and your existing systems. They sync business content, identities, permissions, and required metadata while preserving source access boundaries so search, answers, and Agent can run on fresh, traceable enterprise context.
Each connector performs an initial full sync and ongoing incremental updates based on source capabilities, continuously reconciling content and permission changes. Users in Genly only see information they could already access in the source system.
2. Connector catalog
All · 7 connectors
DingTalk
Connect org structure, group chats, messages, and collaboration content for enterprise search within existing boundaries.
PlannedWeCom
Connect org directory, group chats, messages, files, and day-to-day collaboration signals.
PlannedMicrosoft Teams
Connect channels, chats, members, meetings, and files to assemble Microsoft collaboration context.
PlannedConfluence
Connect spaces, pages, attachments, and comments so enterprise knowledge stays searchable under original permissions.
View docs →Jira
Connect projects, requirements, tasks, defects, and comments so AI can understand progress, owners, and business context.
PlannedGitHub
Connect repositories, commits, branches, pull requests, issues, and engineering documentation.
PlannedGitLab
Connect repositories, commits, merge requests, issues, wikis, and engineering collaboration signals.
Planned3. Categories and support scope
Business categories help you find the systems that carry relevant work. Supported objects, sync modes, permission scope, and operational capabilities for each connector are defined in published connector detail guides.