Submit a connector

Built one, or want one? We review it in the open on GitHub.

1Before you start

Every connector is reviewed against these rules. An idea does not need to meet them yet.

One catalog entry and one driver (D51). Tools, levels and descriptions are ours, never the provider's.
Only read and write_reversible. Nothing that sends, deletes or pays.
Results are untrusted and private. Writing only in turns the owner started.
OAuth with PKCE, or a key sealed on the server. No scraping behind a login, no CAPTCHA solving.
Passes pnpm typecheck and pnpm test, fuzz tests included.

2Service Name of the service Website of the service Repository with your codeThe catalog entry and the driver, shaped like an instance. What Serain can do with itOne or two sentences, as they would appear in the directory.

3Tools

Every tool with what it does for the owner and its level. Connectors only read or write reversibly.

Tools, one per line: name, what it does, level

4Risks What could go wrongWhat does a write change, and how does the owner undo it? What foreign text does the service return, like titles, notes or messages from others?

5Review

This goes into the issue. On GitHub you pick the status and how it connects, and confirm the rules.

Opens a prefilled issue on GitHub; you need an account there. Never paste tokens, passwords or personal data.

What happens next

1
Issue on GitHub
Your submission opens as a public issue with the label connector.
2
Review in the open
We read the code against the rules and ask in the issue when something is unclear.
3
Pull request
An accepted connector gets an entry in the directory, in a pull request that links the issue.
4
Listed
It appears under From the community, with its review linked. Owners add its code to their instance.

Submit a connector

What happens next

Issue on GitHub

Review in the open

Pull request

Listed