Taking a Screenshot of a Page
Part of the MountDev Ops Workflows documentation. Updated November 14, 2026
MountDev Ops Workflows documentation | Updated November 14, 2026
Our Commitment
MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.
Every update passes all 4,402 automated checks before it ships, and every screen change is walked through before release.
What the Step Does Planned
The Take a Screenshot of a Page step (action core.page_screenshot) opens a web page in a browser and saves a picture of it at each width you choose. The pictures are saved as files on a record you name, in your own account's storage. Which pages to capture is up to you: you enter the address in the step.
The step is built, and it stays turned off for every workspace until MountDev's shared engine can take the pictures. Until then it says "This check is turned off for now." and sends nothing. You can still add it to a workflow and try it with Test Run, which checks the step and takes nothing.
The Step's Parts
- Address: a web address like https://example.com/pricing. It must be https, on the standard port, with no user name, and not on a private network. An address that is not allowed is refused with a plain sentence before anything is asked.
- Widths: up to 4 of Phone (390), Tablet (820), Laptop (1366), Desktop (1920), or any number from 320 to 2560. A phone and a computer width at first.
- Whole Page: off at first, which takes the top screen. Turn it on to take the whole page.
- Module and Record: where the pictures are kept. The workflow runs as the person who turned it on, so that person must be able to see the record and add files to it.
What You Get
Each picture is a file on the record, named for the page's host, the width, and the time, such as "example.com 390px 2026-11-14-10-30.png". Whoever may see the record may see the pictures, and the Activity Log names the workflow. Later steps can use saved (how many pictures) and files (the file ids).
Where the Pictures Go
They are encrypted and kept in your account's own storage in your account's region, like any file. The shared engine draws the page and keeps nothing. No key is sent: the step uses your account's engine token only.
What It Uses
Each try counts 1 step in Background work, like any step that does something. Test Run is free.
Who Can Use It
Owners, admins, and anyone whose role allows managing workflows. AI agents and API keys never turn a workflow on.