Integrations overview

What Workover connects to, and what each connection is actually for.

WordPress

Not really an integration — it is the point. A project connects to a site and documents publish to it. Set up per project rather than per workspace, because a workspace usually has more than one site. See connecting your WordPress site.

GitHub

Read-only access to repositories, so technical drafts are written from the code rather than from what sounds plausible. Installed as a GitHub App on the organisation that owns the repositories. See GitHub.

Slack

Workover activity where your team already is. See Slack.

Support inboxes — Plain, Help Scout, Freshdesk

Read-only, and for one purpose: showing you which documentation your customers are missing. Connect the inbox and Workover reads the questions people ask, then tells you which pages would have answered them and which do not exist yet. See Plain, Help Scout and Freshdesk.

This is the integration that changes what you write next, rather than how you write it.

Google Docs

Import an existing document with its formatting intact, for the very common case of a draft that started somewhere else. See importing from Google Docs.

The CLI and MCP server

Not a third-party integration but the same idea: let a tool you already use — Claude Code, or another agent — read your documents and propose changes. Edits arrive as suggestions a person accepts. See the CLI and MCP server.

Where they are configured

Workspace settings → Integrations, except WordPress and screenshot connections, which are per project because they belong to a specific site.

What integrations never get

None of them can publish on your behalf, change your account security, or reach your billing. Those stay with people signed in through the browser. The one exception is deliberate and opt-in: a CLI token can be granted the publish scope at sign-in, and even then it cannot force past a sync conflict.