One n8n node. One payment.

An OpenAPI 3 specification of your API is required. Upload the file, paste the document, or point NativeShip at its URL, and the operations, parameters, and authentication described there become the node. Nothing else is needed: no SDK, no sample code, and no access to your source.

An n8n community node is an npm package that adds your product to n8n as a first-class node, so people can drag it onto a workflow instead of wiring up a generic HTTP Request node. NativeShip generates that package for you.

Yes. Every generated package follows n8n's official community node guidelines, including the required package structure, node and credential file layout, naming conventions, and the n8n-nodes- package prefix, so it installs cleanly in self-hosted n8n.

Yes. You get the complete, publish-ready npm package, including package.json, the compiled node and credential files, and the metadata n8n reads. Publish it to npm under your own account with npm publish, keep it private, or push it to GitHub first.

No. It is a single one-time payment of $79. There is no recurring charge, no seats, and nothing to cancel later.

A build job is one full generation run: NativeShip reads your specification, compiles the node package, and validates the result. Importing or re-importing your OpenAPI document does not use a build job, so you can get the specification right before you spend one.