9 sources · 2 sinks · first-party

Connect the systems
you already use.

Connectors plug kyyn into your world. Sources bring evidence in — mail, meetings, files, systems of record. Sinks carry accepted output back out. All of them are listed on taps — connector registries, first-party and third-party alike.

Capability keys
ns writes to this namespace
net enforced host allowlist
auth sign-in realm
target where a sink delivers
Files & repositories
Local trees and git, no auth
sweep

Glob a local directory tree into hashed, versioned evidence.

ns · file
git-repo

Any git repository's tree, local or remote, at a ref — swept as versioned evidence.

ns · reponet · git remote
Microsoft 365 · Graph
Shared multi-tenant app · device-code sign-in · auth: ms-graph
graph-mail

Microsoft 365 mail with attachments; narrow with mail_filter.

graphgraph.microsoft.com
graph-calendar

Microsoft 365 calendar events, over the same sign-in.

graphgraph.microsoft.com
graph-meetings

Teams meetings that carry transcripts or attendance reports.

graphgraph.microsoft.com
graph-chats

Teams chats and their messages — the slow crawl, on its own cadence.

graphgraph.microsoft.com
sharepoint-file

A tracked SharePoint / OneDrive file or folder, by sharing link, snapshot-fetched.

sharepoint*.sharepoint.com
Shared sign-in

The four windowed Graph plugins share one config — owner_addresses, plus optional client_id / tenant. Leave the app id empty to use the shared multi-tenant kyyn app. mail_filter is graph-mail only; sharepoint-file takes a sharing-link url instead.

Systems of record & federation
salesforce

A SOQL query's records as evidence, via a Connected App device-flow sign-in.

ns · sfauth · salesforce
kb

Ingest another kyyn KB as evidence — federation via curation, no shared ontology.

ns · kbnet · KB remote
Sinks
Accepted output, delivered out
file-replace

Atomically replace one local file with a rendered artifact — a report, a page, a dataset.

target · local file
git-ref

Publish a one-commit bundle to a ref in another repository — a site, a data repo, a mirror.

target · git refnet · git remote
Coming soon
plannedWhat we intend to build next — and the registry below means you don't have to wait
gmail
source

Google Workspace mail, the counterpart to Graph mail.

google-calendar
source

Google Workspace calendar events, same sign-in.

slack
source

Channels and threads — where decisions actually happen.

notion
source

Pages and databases as tracked evidence.

hubspot
source

CRM records from a saved query, HubSpot-side.

xero
source

Invoices, bills and contacts from the ledger.

email-send
sink

Deliver a rendered report to an inbox.

slack-post
sink

Post an accepted artifact to a channel.

object-store
sink

Put an artifact to S3-compatible storage.

The tap registry
Where connectors come from
A tap is a registry

An ordinary repository whose manifest lists connectors — sources and sinks alike. Your KB pins the taps it uses, and their connectors become available to configure.

First-party

Everything on this page ships on kyyn's own tap. It gets no special treatment — it's listed, pinned and run exactly like any other.

Third-party & your own

Anyone can publish a tap. Build a connector with the Rust SDK — or any language that compiles to a WebAssembly component — list it in your tap, and pin it alongside the first-party one.

How connectors are verified and contained is the Trust page's story.

Ready when you are.

Kyyn is in beta and under active development. Join the waitlist and we'll reach out as onboarding opens.

kyyn— from kin: knowledge that knows what it's related to.How it worksConnectors