Import an n8n Workflow to Sell
Paste an n8n export on the builder site, read the per-node import report, and publish a workflow listing with credentials removed and buyer connections listed.
You keep building in n8n. To sell a workflow, export it as JSON, paste it into a new listing, and the SchemaBounce importer converts it to a native workflow, removes your credentials and tells you what it could not convert (dec-016).
- Execution certification is not enabled. Every listing shows the Verified badge. The Certified badge appears when the platform turns certification on.
The paste flow
- In n8n, export the workflow as JSON.
- On the builder site open Sell, then New listing, and set the kind to Workflow.
- Paste the JSON into the n8n workflow JSON field. The page analyzes it as you paste. Nothing is created yet.
- Read the import report (below). Fix the n8n workflow and paste again until no node is unsupported.
- Fill in the listing fields and publish. See Listing types and pricing.
Publishing is blocked while any node is unsupported. The server makes the same check, so the page cannot skip it.
Read the import report
The report starts with one line: how many nodes are supported, how many converted with changes, how many are unsupported. Each node then carries one status.
| Status | What it means | What you do |
|---|---|---|
| Supported | The node maps to a native workflow step. | Nothing. |
| Converted with changes | The node maps, but something changed or needs setup. Examples: a lead webhook becomes a data trigger, a HubSpot credential becomes a buyer connection, an agent or route must be chosen. | Read the note under the node. Check the converted behavior against the original. |
| Unsupported | The importer has no safe mapping. | Rebuild that step with supported nodes, or split it out. The listing cannot publish until it is gone. |
The report ends with a list headed The buyer connects, for example HubSpot (OAuth). That is every account the buyer must connect after they install the automation.
Conversion is not a guarantee of identical behavior. Run the converted workflow on test data and compare each branch, retry path and side effect with your n8n original. Write any intentional difference into the listing description.
Credentials never travel
- The importer does not copy credential values. It records the type of credential a node needs.
- Secrets typed into a node are removed. The marketplace stores only the sanitized source from core-api.
- The buyer connects their own accounts in their workspace. You never see them.
Never paste a real credential into a listing field. See Builder rules.
Notes stay as notes
n8n sticky notes become inert annotations on the workflow. They do not run and do not block an import. Buyers read them as untrusted text, so keep secrets and client names out of them.
What changes for a workflow listing
- A workflow listing cannot be sealed. A sealed workflow cannot be installed. See Open and sealed listings.
- Certification imports the workflow into an isolated workspace and runs it with side-effecting steps mocked. It requires an import with no unresolved setup. See Certification and trust badges.
- A workflow manifest can declare a proof fixture that certification runs. See the fixture format on the certification page.
Advanced: import through the platform MCP
If you operate a customer workspace through your own MCP client, the same importer is available as workflow_import_analyze and workflow_import on the hosted sb_automation tool. Import there creates a draft in that workspace. It does not publish a marketplace listing. The step-by-step setup of sources, sinks, routes and connections is on Hosted MCP.
Related
Related Documentation
Continue exploring