To sell workflow ZIP bundles, package your original exports with setup instructions, dependencies and a license, then attach the archive to a digital product with delivery after confirmed payment. Your buyer purchases a reusable workflow package; they still need their own application, credentials and any paid services it calls.
This guide is for automation creators selling a focused n8n workflow. The original release worksheet below helps you decide what belongs in the paid download and what the buyer must supply. It is a proposed acceptance checklist, not a claim that we ran a production automation or test purchase.
Sell one useful result
Define the buyer and outcome before counting workflows. A clearly documented lead-routing workflow for a small agency is easier to evaluate than an unexplained collection of thousands of exports. Say which input starts it, what output it produces, how exceptions are handled and whether support covers configuration or custom development.
A static template and a managed automation service have different obligations. If you sell the export, do not imply that PayRequest runs the automation, provides n8n hosting or maintains the buyer's integrations.
Export and inspect the actual customer file
n8n documents JSON export and import. That document also warns about credential references and authentication headers in exported workflows. Inspect the export, anonymize sensitive names, remove secrets and replace customer data with invented examples before sharing it.
Check HTTP headers, webhook URLs, account identifiers, pinned example data and hardcoded recipient addresses. The absence of a separate credentials file is not proof that the workflow contains no secrets. Document each credential the buyer must reconnect and the permissions it needs.
Use this original package manifest
For an illustrative lead-routing product, prepare one genuine ZIP with this structure. These are proposed filenames, not downloadable or tested artifacts.
| File | Purpose | Release decision |
|---|---|---|
| workflow.json | Original exported workflow | Opens in documented n8n version |
| setup.pdf | Import, credential and activation instructions | New user can follow the steps |
| requirements.txt | Nodes, app accounts and service costs | Every dependency stated before checkout |
| example-input.csv | Invented sample leads | No real customer or account information |
| license.txt | Usage and redistribution terms | Rights match every included asset |
| changelog.txt | Edition and known limitations | Matches the product description |
Do not rename JSON to ZIP. Create a real archive and keep a copy of the exact edition offered to customers. ZIP packaging changes delivery, not the quality or safety of the workflow.
Test import separately from execution
Use a clean environment with the version advertised. Import the customer export, reconnect fresh test credentials, feed invented inputs and confirm the intended result. Keep external actions disabled until you are ready to inspect them. Test an empty input, a failed integration and a duplicate event as well as the happy path.
Record environment, package edition, test input and result. If a node is missing, document how to obtain it or remove the dependency. A screenshot of your own working account does not prove that the buyer can install the package.
Create the paid download in PayRequest
The reviewed PayRequest upload rules allow ZIP; JSON is not a direct-upload allowlist member. Upload the genuine archive as a digital product, show the outcome and requirements, set your price and connect a suitable payment provider. Account limits and file validation still apply.
Check the buyer page, then verify payment-confirmed delivery with an appropriate end-to-end purchase check before launching. Keep the order, package edition and delivery record together. PayRequest delivers files; it does not import them into n8n or provision the buyer's accounts.
Use the specialist download directory to choose related products. For a creative node graph, the ComfyUI workflow guide covers a different dependency problem. For a Markdown knowledge system, see Obsidian vault templates.
Make your offer easy to evaluate
Show a short demo with invented data, list required services and their separate costs, and explain support and updates. A small original sample can demonstrate quality without exposing the entire paid pack. Measure completed seller signup and first product creation alongside search clicks; visits alone do not establish customer acquisition.
Editorial note: AI assisted with writing and the illustrative cover. Sources and PayRequest upload code were reviewed on 14 October 2026. The manifest is an original proposed worksheet; no live import, execution, purchase or customer result is claimed.
