Build the n8n node you are missing.
Describe an API, test it against the real thing, and publish. No TypeScript, no build tooling, and nothing to install before you start.
Build your first node
Paste a URL or a curl command, name the thing it does, and watch the request assemble itself.
↗Try it for real
Call the API from your own browser before you commit to anything. It is the only step that proves the node works.
↗Install it into n8n
Download the package and add it through the Community Nodes dialog. No npm account needed.
n8n reads a community node from a JSON description. Everything a node does, the fields it shows and where each value ends up in the outgoing request, is data. Node Builder writes that data for you and wraps it in the package n8n expects.
A node is data, not code
The whole behaviour lives in a JSON description. The only JavaScript is a four line shim, identical in every node.
A field is a binding
Not a form input. A field ties something a person fills in to one part of an HTTP request: the path, the query, the body, a header.
The format has no n8n in it
No displayOptions, no routing blocks. You describe the API; the compiler writes what n8n needs.
Every node this builds is an action node. There are no triggers yet, so a node cannot start a workflow on a webhook or a schedule. Authentication covers API keys and HTTP basic; OAuth2 is not there.
The gaps are listed plainly rather than buried, because finding one ten minutes into building is worse than reading it here. See the full list.