Product screenshots in drafts

Workover can sign in to your own app and capture the screenshots a draft asks for, so a how-to arrives with pictures instead of a note saying a picture should go here.

How it works

Connect the app you want screenshots of — its URL and a login — and Workover keeps those credentials encrypted, scoped to the project. When a draft needs a screenshot, it drives a real browser: signs in, navigates to the screen, captures it, and puts the image in the document.

The captured images land in the document’s own media, so they behave like any other image from that point on — including being uploaded into your WordPress media library when you publish.

Connecting an app

Project settings → Screenshots → connect an app. You give it:

The URL to start from, usually your login page.
The credentials to sign in with.

Use a dedicated account rather than your own. It should have enough access to reach the screens you document and no more — this is an account that a browser will log into unattended.

The connection is stored encrypted and scoped to the project, so it is not reachable from your other projects or by other workspaces.

Capturing

Ask for a screenshot as part of a brief, or capture into an existing document. You can point at a specific screen, and capture either the whole page or a single element.

Set a viewport width if it matters. Product screenshots usually read better narrower than a full desktop window — a 2560px-wide capture shrunk into a docs column is unreadable.

Keeping them current

Screenshots go stale the moment the UI changes, and a stale screenshot is worse than none because it is confidently wrong. Re-capture rather than editing images by hand, and prefer capturing the smallest useful region — a cropped panel survives a redesign that a full-page shot does not.

What it will not do

Capture anything not behind your own connection. It drives a browser to a URL you configured with credentials you supplied; it is not a general web scraper.
Run from an API token. Capture is session-only by design, because the request carries login credentials.