versodocs

n8n nodes for VersoDocs: trigger workflows on proposals, reviews and published versions, read approved docs, propose changes and review proposals.

Package Information

Released: this month
Downloads: 0 weekly / 0 monthly
Latest Version: 0.1.0
Author: VersoDocs

Documentation

n8n-nodes-versodocs

n8n community nodes for VersoDocs, the document approval platform: every document has one approved Current version, and changes go through proposals and review.

  • VersoDocs Trigger: start a workflow when a proposal is opened, a proposal is reviewed, a version is published (every plan), or on any other VersoDocs event (Team plan and up).
  • VersoDocs: get a document's Current version, search approved docs, propose a change, comment on a proposal, leave an advisory review.

Install

In n8n: Settings > Community Nodes > Install, enter n8n-nodes-versodocs, accept the risk prompt. Self-hosted with npm:

cd ~/.n8n/custom && npm install n8n-nodes-versodocs

Credentials

Create an API key in VersoDocs: Organization settings > Developer > API keys (owners and admins).

Field Value
API Key the vsd_... key
Organization Slug the part after /org/ in your VersoDocs URLs
Base URL https://versodocs.com (change only for staging)

n8n tests the credential with GET /api/v1/orgs/{org}/webhooks.

Trigger

Activating the workflow subscribes a webhook through POST /api/v1/orgs/{org}/webhooks; deactivating deletes it. Set Workspace (slug or ID) when the key can see several workspaces. Each delivery is { event, created_at, data }; with Verify Signature on (default), the node checks the x-versodocs-signature-v2 HMAC with the secret returned at subscription time and rejects deliveries older than 5 minutes.

Operations and plans

Operation Plan / scope
Trigger: proposal opened, proposal reviewed, version published All plans
Trigger: every other event Team and up
Document: Get (Current version, by ID or path) All plans, docs:read
Document: Search Team and up
Proposal: Create (find and replace, or full Markdown) Pro for API keys (docs:propose); never publishes
Proposal: Comment, Review (advisory verdict) Team and up, proposals:review

The server enforces scopes and plans; its error message (with an upgrade link when relevant) is shown on the failing node.

Docs: https://versodocs.com/docs/automations

Develop

npm install --no-package-lock
npm run build
npm link            # then in ~/.n8n/custom: npm link n8n-nodes-versodocs

Release: bump version in package.json, merge to main, then push a matching tag (git tag n8n-v0.1.0 && git push origin n8n-v0.1.0). The publish-n8n.yml workflow publishes to npm with provenance.

License

MIT

Discussion