Integrations / Microsoft Teams
Bring Microsoft Teams conversations into the graph.
Oynix pulls the discussions and decisions from your Teams channels and links them to the code they're about.
$ oynix connect teamsPrerequisites
- An Azure AD app (tenant id + client id + secret) or a Microsoft Graph access token.
- The Oynix CLI installed and signed in (oynix login).
Setup steps
Install the Oynix CLI
Everything Oynix does runs from one small command-line tool on your own machine — there's nothing to deploy or host. Open your terminal (Terminal on Mac, PowerShell on Windows) and paste this in to install it:
$ curl -fsSL https://get.oynix.dev | sh- Don't have a terminal open? On Mac press ⌘+Space, type "Terminal", hit Enter.
- Paste the line, press Enter, and wait for it to finish — that's it.
- Check it installed: run oynix --version (it should print a version number).
Sign in
Tell Oynix who you are. This opens your browser to sign in with GitHub and links this computer to your workspace — it's how your edits, decisions and presence get attributed to you.
$ oynix login- Run the command; your browser opens automatically.
- Approve the sign-in with GitHub, then return to the terminal.
- If your team uses a workspace key, paste it when asked (a teammate with the master key issues it).
Set up Graph access
Register an app in Azure AD with the Graph permissions to read your Teams channels — or grab a Graph access token.
Connect Teams
Run the command, choose Direct, and paste your app credentials (or token).
$ oynix connect teamsSync anytime
Oynix ingests the conversations and links the decisions to your code.
$ oynix connectors sync teamsCheck it worked
List your connectors to confirm Microsoft Teams shows up and is syncing. Once it's synced, ask the graph a question that should now have an answer from Microsoft Teams.
$ oynix connectors- You should see Microsoft Teams listed as "connected".
- Try it: oynix ask "what did we decide about …?" — answers can now draw on Microsoft Teams.
What gets indexed
Messages
Channel conversations parsed for context.
Decisions
The reasoning behind changes, linked to the code.
People
Who said what — wired into authorship and presence.