RunOnProof for n8n

Status: public-package source and importable workflow files. npm releases are produced only by the manual trusted-publishing workflow. RunOnProof has no claimed partnership with n8n.

This package translates n8n inputs to the existing RunOnProof HTTPS contracts. It does not define products, prices, evidence sources, payment rules, wallets, or settlements. Runtime 402 metadata is returned by the canonical API and is never copied into this package as a price table.

Ten-minute quickstart for self-hosted n8n

1. Clone runonproof/cdo and enter integrations/n8n.
2. Run npm ci --ignore-scripts --include=dev, npm run certify, and npm pack --dry-run to inspect the package. The checked-in .npmrc uses legacy-peer-deps=true only to resolve the official CLI's incompatible transitive peer declarations; direct versions remain locked.
3. Install n8n-nodes-runonproof from the Community Nodes settings, or install the local folder in a self-hosted n8n custom-node directory, then restart n8n.
4. Import one file from workflows/ using Import from File. Start with company-check.json.
5. Create a RunOnProof API credential. URL: https://api.runonproof.com. Add only the RunOnProof API token. A private key or seed phrase is rejected.
6. Select the credential in the RunOnProof node. Keep the workflow inactive.
7. Replace the synthetic company data, correlation ID, and idempotency key. Reuse that key only for the identical request body.
8. Run manually. No payment proof is sent, so a paid route normally returns HTTP 402 and goes to REVIEW.
9. Inspect product, amount, currency, network, requirements, correlation ID, evidence and limitations. Approve or decline outside the node.
10. Only a fresh canonical PROCEED may use the policy-limited continuation output. Payment execution remains a separate human-controlled action.

n8n Cloud users can install the package through Community Nodes after the npm release is visible in the registry.

Included workflows

• company-check.json
• supplier-approval.json
• invoice-payee-verification.json
• payment-authorization.json
• vendor-change-continuous-authorization.json
• runonproof-common-decision-subworkflow.json for advanced composition

Every commercial workflow exposes PROCEED, REVIEW, STOP, UNKNOWN, transient error, unavailable, rate-limited, and invalid-input paths. REVIEW and UNKNOWN use n8n Wait nodes configured for an explicit callback. The callback must contain both approved: true and the matching correlation_id; false, missing, or mismatched values go to the declined output. Keep the generated resume URL confidential. The callback authorizes only the next workflow step; it never signs or settles x402.

Decision and retry rules

| Output | Meaning | Safe action | | --- | --- | --- | | PROCEED | Canonical allow decision with healthy required sources | Continue only within returned policy and conditions; never execute payment automatically | | REVIEW | Human judgment, source issue, hold, retry state, or HTTP 402 | Pause; inspect evidence/quote; obtain explicit approval or decline | | STOP | Canonical block/deny, unexpected economics, or idempotency conflict | Stop and reconcile; never invent a replacement key to hide a 409 | | UNKNOWN | NO_DECISION or unrecognized/insufficient evidence | Pause; never treat as approval |

The node performs exactly one POST. Redirects are disabled, timeout is 1–30 seconds, payloads are limited to 64 KiB, base URLs are HTTPS allowlisted, and the request carries the same idempotency key in the header and body. Manual retry is safe only with the identical body and key. No Payment-Signature, wallet, settlement client, or automatic retry exists.

Test and remove

From this directory, run npm run certify; it executes the official n8n-node linter/build, strict TypeScript typecheck, the local source/compiled rules from @n8n/scan-community-package, and compiled-node tests. From the repository root, run npm run test:n8n-make for workflow/Make equivalence. For packaging QA, run npm pack --dry-run and inspect the produced local tarball with tar -tzf. To remove the integration, deactivate imported workflows, delete their RunOnProof credential, uninstall the local package, and restart n8n. Remove saved executions according to your own retention policy.

Publication gates

The package is migrated to the current official TypeScript n8n-node scaffold and locally passes its linter, strict typecheck, build, scanner rules on source and compiled output, compiled-node tests, and pack inspection. Publication is restricted to the manual publish-n8n.yml workflow, which uses the npm Trusted Publisher identity for this repository instead of a stored registry token. After the first registry release, run npx @n8n/scan-community-package n8n-nodes-runonproof and submit the node and templates for n8n review.

Official references reviewed 2026-08-12: workflow import/export, private nodes, n8n-node tool, node linter, verification guidelines, credentials files, and security audit. Version observations: n8n 2.34.5, @n8n/node-cli 0.43.3, @n8n/scan-community-package 0.32.0, and stable n8n-workflow 2.33.2 (the registry's latest tag remains 2.16.0).