Developer docs

Zapier and n8n: automate around reviews and publishes

Connect VersoDocs to thousands of apps. Triggers fire when proposals are opened or reviewed and when a version is published (every plan). Actions read the Current version, search, propose changes and comment, with the same plans and scopes as the REST API.

Plans

FreeTeamPro
Zapier + n8n triggers (key review events)✓✓✓
Zapier + n8n triggers on every event—✓✓

Actions: reading the Current version works on every plan; search needs Team; comments and advisory reviews need Team; proposing changes with an API key needs Pro.

Connect

  1. In VersoDocs, an owner or admin creates an API key in Settings → Developer (scope docs:read, plus proposals:review or docs:propose for those actions).
  2. Zapier: add the VersoDocs app, paste the key and your organization slug (the part after /org/ in VersoDocs URLs).
  3. n8n: install the community node n8n-nodes-versodocs (Settings → Community Nodes), create a VersoDocs API credential with the key, organization slug and base URL.
  4. Pick a trigger. If the key can see several workspaces, choose the workspace to watch.

Triggers

EventFires whenPlan
version.publishedA document is published as a new version.All plans
version.acknowledgedA member confirms they have read the current version of a document.Team+
document.createdA new document is created in a workspace.Team+
document.updatedA document is renamed or moved to another folder.Team+
document.deletedA document is permanently removed.Team+
document.commentedSomeone (a member, an agent or a share-link guest) comments on a published version of a document or replies in a thread.Team+
proposal.openedA reviewer is asked to review proposed changes to a document.All plans
proposal.updatedAn open proposal’s title, description or content is revised through the API.Team+
proposal.commentedSomeone (or an agent) comments on a proposal or replies in a thread.Team+
proposal.verdict_submittedA reviewer approves a proposal, asks for changes, or leaves a comment.All plans
proposal.publishedA proposal is published: its working copy becomes the new current version.Team+
proposal.closedA proposal is closed by its author without publishing.Team+
review.requestedSomeone asks an external reviewer bot (API key) to review a proposal.Team+
ai_review.completedA hosted AI reviewer posted its (advisory) review on a proposal.Team+
ai_review.failedA hosted AI reviewer gave up after retries (e.g. bad key, provider down).Team+

Each delivery is { event, created_at, data } with the same data as workspace webhooks, signed with x-versodocs-signature-v2. Turning a Zap or workflow off removes its subscription; revoking the API key stops all of its subscriptions.

Actions

ActionREST endpointPlan
Get document (Current version)GET docs/{id}/current, GET docs/by-pathAll plans
Search approved docsGET searchTeam+
Comment on a proposalPOST proposals/{id}/commentsTeam+
Leave an advisory reviewPOST proposals/{id}/reviewsTeam+
Propose a change (never publishes)POST docs/{id}/proposalsPro

Subscription API

Zapier and n8n use these endpoints; any automation tool can too. API key, docs:read scope.

POST/api/v1/orgs/{org}/webhooksAll plans

Query parameters

NameTypeDescription
target_url *stringHTTPS URL that receives deliveries.
events *string[]Event names. Free: proposal.opened, proposal.verdict_submitted, version.published.
workspacestringWorkspace slug or id. Required when the key sees several workspaces.
descriptionstringLabel shown in Settings.

Returns 201 { id, target_url, events, workspace, created_at, secret }. The secret (for signature checks) is shown only here. A Team event on Free answers 402 with locked_events.

GET/api/v1/orgs/{org}/webhooksAll plans

Subscriptions created through the API in the key’s workspaces.

DELETE/api/v1/orgs/{org}/webhooks/{id}All plans

204 when removed.

GET/api/v1/orgs/{org}/webhooks/samples?event={name}All plans

Up to 3 recent deliveries for that event (or one example), for building and testing a Zap or workflow.