How to Schedule Website Screenshots and Save Them to OneDrive in India

To schedule website screenshots and save them to OneDrive in India, use Power Automate to trigger a desktop flow that opens the site, captures the displayed page, and uploads the image to OneDrive for Business. For a cloud-managed schedule, create a recurring cloud flow and have it run the desktop flow on a registered machine. Select India Standard Time in the schedule and check the next run shown by Power Automate.

A screenshot action captures the webpage or element currently displayed in the browser. Confirm the action’s behavior for your page and desired capture; do not assume it produces a full-page image. Microsoft also documents scheduled triggers for desktop flows, but that feature is marked preview and may not be available in every region. Microsoft browser automation actions · Scheduled triggers for desktop flows

What you need

Power Automate and Power Automate for desktop access through an eligible work or school account.
A Windows machine registered with Power Automate and a desktop-flow connection if a cloud flow will invoke the desktop flow.
A browser available on that machine and permission to access the website.
A OneDrive for Business connection and a destination folder where the flow can create files.
An appropriate Power Automate entitlement. Cloud-triggered desktop flows have machine, account, connection, and licensing requirements. Unattended runs require the Power Automate Process plan according to Microsoft’s documentation; verify current entitlements and session constraints before deployment. Trigger desktop flows from cloud flows · Run unattended desktop flows

Choose attended execution if a person will be present to start or supervise the browser run. Choose unattended execution only after confirming the required plan and machine/session setup. The exact designer labels can vary by account and Power Automate interface version.

Recommended setup: scheduled cloud flow plus desktop flow

This pattern separates the recurring schedule from browser work. The cloud flow starts on a recurrence and invokes a desktop flow; the desktop flow opens the site and takes the screenshot. The cloud flow can then create a OneDrive file from the image content, or the desktop flow can save locally and pass the resulting file along according to the available actions in your environment.

1. Build the desktop flow

Open Power Automate for desktop and create a new flow, for example Capture website to OneDrive.
Add a browser-launch action and set it to open the target URL. Use the browser supported by your installed Power Automate actions.
Add a wait suited to the page. Prefer waiting for a reliable page element when possible; a fixed delay can be used for pages without a stable element. Pages with slow or dynamic content may need additional wait logic.
Add the browser screenshot action. Choose whether to capture the displayed webpage or a specific webpage element, where supported. Set the output to a file or clipboard as the action allows.
Use a repeatable filename that avoids overwriting prior runs. For example, include the site name and a date/time value. Ensure characters in the timestamp are valid in file names and that the timestamp reflects the intended time zone.
Close the browser when finished if it is no longer needed. Add error handling so a failed navigation or screenshot does not proceed as if a valid image exists.

The screenshot action is documented for a webpage or webpage element currently displayed in the browser, with output to a file or clipboard. Check the action configuration and the rendered result to establish whether it matches your required viewport or element capture. Browser automation actions reference

2. Register the machine and connection

For cloud-triggered execution, register the computer or machine group, create the desktop-flow connection, and confirm the account can sign in and access the target site. Microsoft’s cloud-to-desktop flow documentation describes these prerequisites. If the flow must run when nobody is signed in, verify unattended licensing and remote-session behavior before relying on it.

3. Create the recurring cloud flow

In Power Automate, create a scheduled cloud flow with the recurrence trigger.
Set the recurrence interval, such as daily or weekly, and choose the time that you want the screenshot run to start.
Select the India Standard Time time zone in the current time-zone selector. Review the next scheduled run shown in the designer. The start-time field may be represented in UTC, while the selected zone determines how the recurrence is interpreted.
Add the action to run a desktop flow. Select the registered machine or machine group, the desktop-flow connection, and the flow you created.
Configure the OneDrive for Business file action to create the image in the chosen folder. Supply the captured image’s file content, a unique filename, and the correct folder path.
Save the flow and run it manually once before depending on the recurrence.

Microsoft’s recurrence guide documents scheduling and time-zone selection. The OneDrive for Business connector provides file-management actions; confirm the signed-in account and target folder in your own flow. Run a cloud flow on a schedule · OneDrive for Business connector

Alternative: schedule a desktop flow directly

Microsoft documents a Scheduled triggers feature for desktop flows. It may be simpler when available, but Microsoft labels it preview and notes that regional rollout can affect availability. Check whether it appears in your environment, whether it meets your organization’s requirements, and which run mode and licensing apply before choosing it over the scheduled-cloud-flow pattern. Set the time zone to India Standard Time and verify the next run in the interface. Microsoft Scheduled triggers documentation

Save screenshots to OneDrive reliably

Use the right connector and account: choose the OneDrive for Business connection that owns or can write to the destination folder.
Pass image bytes: the create-file action needs the screenshot file content, not only the local file path. If the desktop flow writes locally, configure the cloud flow to obtain and pass the file content using actions available in your environment.
Make names unique: include a date/time component or another run identifier so scheduled captures do not silently overwrite each other.
Check folder paths: confirm the destination exists and the connection has permission to create files there.
Plan for failed runs: make the flow report or record navigation, capture, and upload failures separately so a missing image is visible.
Validate the artifact: open the image in OneDrive and confirm it is the expected page, is legible, and has the intended dimensions and capture area.

OneDrive’s former “Save screenshots to OneDrive” setting is no longer available in OneDrive settings. The documented backup option concerns screenshots already saved in the Pictures folder; it does not schedule visits to websites or take new captures. Microsoft Support: Save screenshots to OneDrive automatically

India time-zone and recurrence checklist

Choose India Standard Time in the schedule’s time-zone selector.
Set the desired daily, weekly, or other supported cadence.
Review the displayed next run rather than manually converting the time unless your workflow requires a UTC value.
Run once manually and confirm the actual local execution time and resulting OneDrive file.
Recheck schedule behavior if you change the recurrence, connection, machine, or flow owner.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. It returns a PNG, JPEG, WebP, or PDF from one request. You can call it from a scheduled job or workflow, then save the response bytes to OneDrive using the storage actions you already use. The API supports caching with a TTL you choose, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, and an API for usage. See the ScreenshotNeo API documentation.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
r.raise_for_status()
with open("shot.webp", "wb") as f:
    f.write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await require('node:fs/promises').writeFile('shot.webp', Buffer.from(await res.arrayBuffer()));

Replace YOUR_API_KEY with your key and change the target URL. Store the key in a secret or environment variable in a deployed workflow. Cookie banners, popups, and chat widgets are removed before capture; bot checks, blank pages, failed loads, timeouts, and cache hits are never billed, and response headers report the page verdict and billing status. An MCP server gives AI agents tools to take screenshots, get page information, and capture PDFs. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots.

Common problems and fixes

Problem	Likely cause	What to check or fix
The cloud flow runs, but the desktop flow does not start.	The machine is not registered or available, the connection is wrong, or the account lacks the needed entitlement.	Confirm machine registration and status, connection ownership, account eligibility, and run-mode licensing. Review Microsoft’s current prerequisites.
The schedule fires at an unexpected hour.	The recurrence time zone and intended local time do not match.	Select India Standard Time and inspect the next run displayed by the schedule. Check the configured start time as well as the recurrence zone.
The screenshot is blank or shows a loading state.	The capture occurs before the page or its key content finishes rendering.	Wait for a stable page element or add an appropriate delay; check whether sign-in, consent, or network access blocks the page.
The screenshot omits content below the fold.	The configured browser action captures the currently displayed page or viewport rather than a full-page rendering.	Check the screenshot action’s documented behavior and configuration. If full-page output is required, use a capture method that explicitly supports it.
The image is missing from OneDrive.	The wrong account or folder is selected, file content was not passed, or the connection cannot write to that location.	Check the OneDrive for Business connection, file content input, destination path, and folder permissions.
Each run replaces the previous image.	The flow reuses the same filename and the file action overwrites or targets the existing item.	Add a date/time or run identifier to the name and verify collision behavior in the file action.
The scheduled desktop trigger is unavailable.	The feature is in preview and may not have rolled out to the region or environment.	Use the scheduled cloud flow that invokes a desktop flow if its prerequisites are met, or check availability later.
An unattended run cannot create a desktop session.	The machine, account, session, or unattended plan requirements are not met.	Review unattended-flow prerequisites and current licensing; test on the intended machine and execution mode.

Performance, reliability, and cost considerations

Rendering time: waiting for a real content element is usually more dependable than guessing a fixed delay, but dynamic pages can still vary. Set a practical timeout and make a failed wait stop or flag the run.
Machine availability: a desktop capture depends on the registered machine, browser, network, and desktop-flow connection being usable at the scheduled time.
File growth: recurring captures accumulate. Pick an image format and cadence that fit your retention needs, and review OneDrive storage and retention policies for your account.
Licensing: Power Automate licensing depends on how the desktop flow is triggered and whether it runs attended or unattended. Verify current plan terms; unattended execution has the additional Process plan requirement documented by Microsoft.
Preview risk: the direct scheduled desktop-flow trigger is marked preview, so availability and behavior can change. The cloud-flow trigger pattern is the documented alternative when the preview feature is unavailable.
API workflow: ScreenshotNeo removes consent banners, popups, and chat widgets before capture, and failed, blank, timed-out, bot-check, and cached outcomes are not billed. Its plans are Free for 1,000 shots/month, Starter $5 for 3,000, Growth $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000, and Business $249 for 1,000,000; yearly billing gives two months free. Every feature is on every plan. Choose based on required volume and workflow rather than assuming a browser-based flow and an API have identical behavior.

Frequently asked questions

Can I take website screenshots automatically?

Yes. A recurrence trigger can start browser automation on a schedule. A screenshot action by itself does not establish a recurring schedule.

Does OneDrive automatically visit websites and take screenshots?

No. OneDrive stores or backs up files; it does not schedule website visits. The former screenshot backup setting is no longer available in OneDrive settings.

Can Power Automate take a screenshot of a webpage?

Power Automate for desktop documents a browser screenshot action for the displayed webpage or a webpage element. Confirm its capture behavior for your specific layout and full-page requirements.

Can I schedule a Power Automate desktop flow in India?

Use a scheduled cloud flow and select India Standard Time, or use the desktop Scheduled triggers feature if it is available in your environment. Check the next run and current licensing before relying on it.

Can I store the screenshot in personal OneDrive?

The cited connector is OneDrive for Business. Connector availability and account support vary; check the actions available for the account and environment you intend to use.