Developer docs

Integrations: VersoDocs inside the tools you already use

Every integration works the same way: connect it once, choose where it applies (a channel, a repo, a folder, a workspace), and approved documents show up there. Org admins manage them in Settings → Integrations; the API, CLI and AI agents use keys or connections from Settings → Developer.

Chat

Slack

Review requests, verdicts and publishes in the Slack channels your team already reads. Full guide. All plans

  1. Connect: Click Connect Slack and approve the VersoDocs app for your Slack workspace.
  2. Choose where: Pick a channel for each VersoDocs workspace and the events it posts.
  3. What happens: Reviewers get the request in Slack and, on Team, approve from the message. Pasted links preview the doc.

Streamlines: Reviews move without anyone checking another inbox.

Microsoft Teams

Review cards, approvals and pinned approved docs inside Microsoft Teams. Full guide. All plans

  1. Connect: Add the VersoDocs app to a team in Teams. Your Teams admin may need to allow it.
  2. Choose where: In a channel, click Connect this channel and pick the workspace and events.
  3. What happens: Review requests and publishes post as cards, with approve buttons on Team. Pin an approved doc as a channel tab.

Streamlines: Teams-first groups review and read approved docs without leaving Teams.

Teams Workflows & webhooks

No app installs allowed? Post to Teams or Slack with a webhook URL instead. Full guide. All plans

  1. Connect: Create a Teams Workflows webhook or a Slack incoming webhook and copy its URL.
  2. Choose where: Paste it in a workspace's webhook settings and pick the events.
  3. What happens: Publishes and proposal updates post to that channel, on every plan.

Streamlines: Works where IT blocks third-party chat apps.

Code & issues

GitHub

Flag pull requests that cite an outdated spec, and mirror approved docs into a repo. Full guide. Team+

  1. Connect: Click Connect GitHub and install the VersoDocs GitHub App on your organization or repos.
  2. Choose where: Choose warn or fail for stale references. On Pro, map a workspace to a repo, branch and folder.
  3. What happens: Every pull request gets a check that flags cited spec versions that are no longer Current. Mirrored docs stay current as Markdown.

Streamlines: Code review catches spec drift before merge.

Jira

Link proposals and docs to the Jira issues they implement. Full guide. Team+

  1. Connect: Paste a Jira issue URL in Linked issues. Connect Jira to also show titles and statuses.
  2. Choose where: Link issues on each proposal or document.
  3. What happens: When the proposal is published, VersoDocs comments on the linked Jira issue.

Streamlines: Engineers see which approved spec an issue ships against.

Linear

Link proposals and docs to the Linear issues they implement. Full guide. Team+

  1. Connect: Paste a Linear issue URL in Linked issues. Connect Linear to also show titles and statuses.
  2. Choose where: Link issues on each proposal or document.
  3. What happens: When the proposal is published, VersoDocs comments on the linked Linear issue.

Streamlines: Engineers see which approved spec an issue ships against.

Docs & wikis

Notion

Put approved docs on the Notion pages other teams already read. Team+

  1. Connect: Create a Notion internal integration, paste its secret here and share a parent page with it.
  2. Choose where: Editors choose Export to… on a document, or Export folder to… on a folder.
  3. What happens: The approved version lands as a Notion page that links back. On Pro it updates on every publish.

Streamlines: Notion readers always see the approved text, with no copy-paste.

Confluence

Put approved docs in the Confluence spaces other teams already read. Team+

  1. Connect: Create an Atlassian API token, then enter your site, account email and token here.
  2. Choose where: Editors choose Export to… on a document and pick the space. A default space is optional.
  3. What happens: The approved version lands as a Confluence page that links back. On Pro it updates on every publish.

Streamlines: The wiki stops drifting from what was actually approved.

Google Docs export

Send the approved version of a doc to Google Docs in one click. Team+

  1. Connect: No setup. Each person signs in with their own Google account the first time.
  2. Choose where: Editors choose Export to… → Google Docs on a document.
  3. What happens: A Google Doc with the approved version is created in their Drive. Exporting again updates it.

Streamlines: Share approved text with people who live in Google Workspace.

Files & storage

Cloud folders

Approved docs as PDF or Word in the OneDrive, SharePoint, Google Drive or Dropbox folders people already use. Full guide. Team+

  1. Connect: Connect a OneDrive / SharePoint, Google Drive or Dropbox account.
  2. Choose where: Map a workspace or folder to a cloud folder and choose PDF, Word or both.
  3. What happens: Approved docs land there with the same file name, stamped with the version. On Pro they are rewritten on every publish.

Streamlines: Readers never need a VersoDocs account to find the current version.

Watch a folder

Turn files in a cloud folder into drafts, and their edits into proposals. Full guide. Pro

  1. Connect: Uses the accounts connected under Cloud folders.
  2. Choose where: Link a cloud folder to a workspace folder.
  3. What happens: New files become drafts and a changed file opens a proposal for its reviewers. Nothing is published automatically.

Streamlines: Teams keep editing files where they are while approvals stay controlled.

Office

Microsoft Word

Open approved versions in Word and send edits back as proposals. Full guide. All plans

  1. Connect: In Word, open Home → Add-ins, add VersoDocs and sign in.
  2. Choose where: Search a document and open it, or link the file you already have.
  3. What happens: Word shows when a newer version is approved. On Pro, Propose changes sends your edits for review.

Streamlines: Writers stay in Word; reviews and approvals stay in VersoDocs.

Google Docs add-on

Open approved versions in a Google Doc and send edits back as proposals. Full guide. All plans

  1. Connect: In a Doc, open Extensions → Add-ons → Get add-ons, install VersoDocs and authorize.
  2. Choose where: Search a document and open it, or link the Doc you already have.
  3. What happens: The Doc shows when a newer version is approved. On Pro, Propose changes sends your edits for review.

Streamlines: Drafting stays in Google Docs; the approved version stays in VersoDocs.

Email in

Forward an email to a workspace address to start a draft. Full guide. All plans

  1. Connect: A workspace admin turns on Email in for the workspace.
  2. Choose where: Share the workspace's private address with the team.
  3. What happens: Forwarded emails and their Word, Markdown or HTML attachments become drafts. Nothing is published until you do it.

Streamlines: Requirements buried in email threads become reviewable drafts.

Automation & AI agents

AI agents (MCP)

Let Claude, Cursor or Copilot read approved docs and propose changes for review. Full guide. All plans

  1. Connect: Each member connects their agent in one click from Personal settings. Admins can also use an API key.
  2. Choose where: The agent sees the workspaces the connecting member can open.
  3. What happens: Agents answer from the Current version and open proposals that people review.

Streamlines: Agents stop working from stale copies of your specs.

REST API

Read approved docs from scripts, CI and internal tools. Full guide. All plans

  1. Connect: An admin creates an API key in Developer settings.
  2. Choose where: Choose the key's scopes. On Pro, limit it to one workspace.
  3. What happens: Your tools fetch the Current version over HTTPS instead of copying files around.

Streamlines: Internal tools always quote the approved version.

versodocs CLI

Pull approved docs into a repo and check them in CI. Full guide. All plans

  1. Connect: Create an API key, then run versodocs login with it.
  2. Choose where: Track documents in versodocs.lock in your repo.
  3. What happens: versodocs pull writes approved docs into the repo; versodocs check flags outdated ones in CI.

Streamlines: Specs in the repo match what was approved, checked on every build.

Zapier

Start Zaps when proposals are opened, reviewed or published. Full guide. All plans

  1. Connect: Add the VersoDocs app in Zapier and paste an API key and your organization slug.
  2. Choose where: Pick a trigger and the workspace to watch.
  3. What happens: Review events start your Zaps (every event on Team). Actions read docs, propose changes or comment.

Streamlines: Hand-offs after an approval run themselves.

n8n

Run n8n workflows when proposals are opened, reviewed or published. Full guide. All plans

  1. Connect: Install the n8n-nodes-versodocs community node and add a VersoDocs API credential.
  2. Choose where: Pick a trigger and the workspace to watch.
  3. What happens: Review events start your workflows (every event on Team). Actions read docs, propose changes or comment.

Streamlines: Self-hosted automation around reviews and publishes.