Oynix
Slack

Connectors / Slack

Capture decisions where they happen.

Read your chosen Slack channels to capture the "why" behind decisions, so knowledge never dies in a thread.

One tapYour own OAuth appA token you paste

Before you start

Install Oynix and open the connectors page. You do this once. Everything below then happens right in the page, with no commands to run.

Install OynixOpen the connectors page

Log in

Pick whichever you prefer. You only need one.

One tap

Click, approve, done.

  1. 1In the connectors page, open Slack and click "Connect with Slack".
  2. 2A provider window opens. Sign in and approve the read-only scopes.
  3. 3It closes and you are connected. There is nothing to copy or paste.

Your own OAuth app

Register an app once.

  1. 1At api.slack.com/apps create an app and add the OAuth redirect URL from the panel.
  2. 2Under Bot Token Scopes add channels:read, channels:history and users:read.
  3. 3Copy the Client ID and Secret.
  4. 4In Oynix pick 'Use your own app', paste both, install to the workspace, then Connect.

A token you paste

Paste a credential.

  1. 1Create the credential: api.slack.com/apps → your app → OAuth & Permissions → Bot User OAuth Token (xoxb-…), with channels:read, channels:history and users:read.
  2. 2Open Slack in the connectors page and choose the token path.
  3. 3Enter the bot or user token, then click Connect. Oynix checks it right then and saves nothing if it fails.

After login

Once connected, this all happens in the page. No commands.

  1. 1The picker opens. Choose which channels to read (empty means every channel the bot can see) to sync.
  2. 2Hit Sync to pull just those into the graph and link them to your code.
  3. 3Deselect one later and Oynix purges only that instance's data.

This is a read-only ingest app, not the ask bot. It only sees channels it is a member of. Invite it to each channel you pick, or that channel syncs as a partial and says so.

What it syncs

Threads

One document per thread (root and replies), plus loose messages grouped by day.

Decisions

The reasoning captured in conversation, linked to the code it shaped.

Links

References to code, PRs and tickets woven into the graph.