Analysis updated 2026-05-18
Turn an existing REST API's OpenAPI spec into a working Notion Worker without hand-writing each tool.
Quickly prototype a Notion integration for an API you already document with OpenAPI.
Split a large API into multiple smaller Notion Workers using tag filters to stay under the tool cap.
Generate a starter worker project as a base to customize further by hand.
| ravenrepo/notion-workx | 0xradioac7iv/tempfs | abboskhonov/hermium | |
|---|---|---|---|
| Stars | 0 | 0 | 0 |
| Language | TypeScript | TypeScript | TypeScript |
| Setup difficulty | moderate | moderate | moderate |
| Complexity | 3/5 | 3/5 | 4/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires Notion Workers enabled in your workspace plus an OpenAPI spec to generate from.
WorX is a code generator that turns an OpenAPI 3.x specification into a ready to deploy Notion Worker project. If you already have an API described in an OpenAPI file (a common format that documents what endpoints an API offers and what data they expect), WorX reads that file and writes out a TypeScript worker where each supported endpoint becomes a callable tool. It sits alongside Notion's own command line tool, called ntn, which handles authentication, building, deploying, and running workers. WorX does not replace ntn. Instead it focuses on one job: generating the worker code automatically so you do not have to write each endpoint mapping by hand. Using it is a two step process. First you point the CLI at your OpenAPI spec, either a local file or a URL, and tell it where to write the generated project. Then you move into that generated folder, install its dependencies, and deploy it using the generated deploy scripts. Options let you filter which endpoints get generated by tag, preview the output without writing files, or trigger a deploy automatically once generation finishes. The current version supports OpenAPI 3.0 and 3.1, REST APIs using JSON or form encoded request bodies, path, query, and header parameters, and both bearer token and API key authentication. It can resolve references within the same file and handles large sets of optional parameters through a generated helper object. It does not yet resolve references that point to other files, and OAuth2 or OpenID flows need to be wired up by hand. Endpoints that rely on file uploads, binary data, or XML only content are skipped, and complex schema combinations are simplified rather than fully modeled. A practical note for anyone trying this: Notion enforces a cap on how many tools a single worker can expose, currently 100, so a large API may need to be split into multiple generated workers using the tag filter option. The project is released under the MIT license and includes standard contribution, security, and code of conduct documentation.
A code generator that turns an OpenAPI spec into a deployable Notion Worker project, mapping each API endpoint to a callable tool automatically.
Mainly TypeScript. The stack also includes TypeScript, Node.js, OpenAPI.
Use freely for any purpose, including commercial use, as long as you keep the copyright notice.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.