Integrations overview
Workover connects to other tools at three levels: the workspace, the project and your own account. Most confusion about integrations comes from looking for a setting at the wrong level, so this page explains where each connection lives and what it is for, then points you to the page that sets it up.
Three places a connection can live
| Level | Where you find it | What lives there |
|---|---|---|
| Workspace | Workspace settings → Integrations | Support tools, Slack, code hosts, Webflow, Help Scout Docs, Google Search Console & Analytics, and the app Workover signs in to for screenshots |
| Project | Project settings | The site a project publishes to (WordPress, Webflow, Mintlify or Help Scout Docs) and the code repositories linked to it |
| Account | Account settings → Developer | The tokens you approved for the Workover CLI and MCP server, listed by the device that signed in |
A workspace connection is shared: once it exists, every project in the workspace can use it. Any member of the workspace can connect one; only owners and admins can disconnect.
Workspace integrations, by group
The Integrations tab groups its cards under the headings below. Each card has a Connect button. A card marked Coming soon cannot be connected yet.
| Group | Integrations | What it is for | How you connect |
|---|---|---|---|
| Support | Plain, Freshdesk, Zendesk, Intercom, Help Scout, or a custom source | Read your support tickets and show, under Support signals, which topics your documentation is missing or answers badly | Paste an API key or token into the connect dialog (a custom source pushes conversations in instead) |
| Messaging | Slack | Send notifications about Workover activity to Slack | Approve the Workover app in Slack |
| Code | GitHub, GitLab, Bitbucket | Let Workover AI read the repositories you link to a project, so drafts and documentation review work from your code | Authorize Workover on the code host |
| Publishing | Webflow, Help Scout Docs | Publish documents to Webflow CMS collections, or edit your Help Scout knowledge base and publish back | Paste a Webflow Site API token or a Help Scout Docs API key |
| Reporting | Google Search Console & Analytics | See how your published pages rank and perform, alongside the changes Monitor detects | Sign in with Google |
| Screenshots | Your own app | Let Workover sign in to your product and capture screenshots for your docs | Connect your app and give it the address and a login |
See Connecting your support tool.
Project connections
A project syncs with one publishing destination, so that choice is made per project, in Project settings:
- WordPress: connect the project to a WordPress site and push documents to it. See Connecting your WordPress site. To publish images with the site’s own image styles, see How to apply your site’s image styles.
- Webflow: choose the Webflow site and CMS collections the project syncs with.
- Help Scout Docs: edit a Help Scout knowledge base in Workover and publish back to it.
- Mintlify: edit a Mintlify docs site in Workover and publish back to the GitHub repository Mintlify deploys from, either by opening a pull request or by committing to the deploy branch.
- Code repositories: the repositories a project’s AI drafts read. A code host has to be connected in the workspace first. See GitHub.
What connected tools can change
Reading is the default, but not every connection is read-only:
- Support tools only read. Workover never replies to a ticket or changes it.
- Code hosts only read, with one exception: publishing a Mintlify project commits to your docs repository or opens a pull request there.
- WordPress, Webflow, Mintlify and Help Scout Docs exist to publish, and do so when someone pushes or publishes from the project.
- CLI and MCP tokens can do only what you approved when the tool signed in. Some scopes let a tool publish. See Access tokens and scopes.
No token can reach your account security or your billing, whatever it was granted. Those need you, signed in to Workover in a browser.
Agents and the command line
The Workover CLI and MCP server let Claude Code or another agent search, read, and edit your documents. They are not a workspace integration: each token belongs to you and to the machine that signed in with it. See Set up your agent.
Find the page for your task
- Connect GitHub and link a repository: GitHub
- Connect Plain, Help Scout or Freshdesk: Connecting your support tool
- Get notifications and alerts in Slack: Slack
- Connect Claude Code or another agent: Set up your agent
- Look up token scopes: Access tokens and scopes
- Bring existing documents into Workover: Importing from Google Docs
- Connect a WordPress site: Connecting your WordPress site
Still need help?
Can’t find what you’re looking for? Our team is here to help.