What website is this?
NativeShip helps SaaS teams turn an existing API into an installable n8n community node, skipping the work of starting from the node's file conventions. With an OpenAPI 3 specification ready, it can generate a node package. You adjust resources, operations, and interface copy in a preview, then publish from your own GitHub repository to your own npm account. Each release keeps a record of the npm package, the Git tag, and the workflow. It fits teams that want customers to call the product inside n8n workflows and do not have someone maintaining the node project full time.
Key Features
- Upload, paste, or enter an OpenAPI 3 URL, and turn its operations, parameters, and authentication into a node.
- Rename resources, reorder operations, hide items you do not need, and rewrite the labels on the interface.
- Preview the node's parameters and operations as they appear inside n8n.
- Connect your own GitHub and npm, check the package name and version, and publish only after you confirm.
- Tie each version to the npm package, the Git tag, and the steps recorded in the workflow.
- Organize the package with n8n community-node folders, naming, and the
n8n-nodes-prefix. The pricing page says it can be installed on self-hosted n8n.
Use Cases
- A SaaS product that already has an OpenAPI document generates a community node when customers ask about n8n, instead of first assigning someone to learn the node project layout.
- After an API change, the team imports the spec again and runs another build so the node's operations and parameters match the API.
- Someone responsible for external integrations edits resource names and field labels before release and checks the workflow screen against the preview.
- A team that must keep the package on its own GitHub and npm reviews the version in the product, then creates the tag and publishes.
Who is it for?
- SaaS companies that already have an OpenAPI 3 spec and plan to offer customers an n8n node.
- Small teams that do not want to maintain node file layout and publish scripts on their own.
- Product owners who want users to see only their own integration, not which tool generated it.
- A poor fit for people without OpenAPI 3 who only want to write HTTP requests inside a workflow. It is also not n8n itself, the product end users use to build automations.
How It Compares to Similar Tools?
The split is what you ship. For an occasional call to one endpoint, n8n's HTTP Request node is enough, and your product will not appear as its own node in the workflow. If people should drag a node onto the canvas and pick resources, operations, and authentication, you need a community node, which is an npm package. NativeShip generates that package from OpenAPI 3 and organizes it with the folders, naming, and n8n-nodes- prefix that n8n requires. When someone on the team already knows node development, writing it by hand can control edge cases more tightly. Here, generation, interface preview, and publishing from your own repository are connected, and the number of full builds depends on the plan you buy. The pricing page lists a one-time price of $79, also shows $129, and says it is not a monthly subscription.
FAQs
Q: Do I still have to write the n8n node myself?
A: You do not have to start from a node project scaffold. The pricing page says you need an OpenAPI 3 spec, which you can upload, paste, or provide as a URL. It does not ask for an SDK, sample code, or access to your source. You get a publishable npm package. You can push it to GitHub first, or leave it unpublished.
Q: How does NativeShip charge, and what counts as one build?
A: The pricing page states a one-time payment of $79, shows $129 beside it, and says there is no subscription and no seats. The plan includes 1 node, about 3 builds, automatic generation, a node that follows the guidelines, a publishable npm package, GitHub integration, and priority support. Importing or importing a spec again does not use a build. One build reads the spec, compiles the package, and validates it.
Q: Will customers see NativeShip, and is the imported API used to train models?
A: The site says customers use an n8n integration and do not need to know about NativeShip. The privacy policy says personal information, imported API information, project information, and generated node content are not used to train or fine-tune models. Accounts can sign in with Google or email. Polar processes payments.
Q: Where can the generated node be installed?
A: The pricing page says the package follows n8n's community node guidelines and can be installed on self-hosted n8n. The page does not say whether n8n Cloud is supported. The nodes directory lists community nodes NativeShip published under @nativeship, including Outrank, Post Bridge, Reoon Email Verifier, SendPilot, Supermemory, and TrustMRR.
