How to Capture GST Portal Webpage Screenshots with Power Automate in India
Use Power Automate for desktop to save a GST Portal webpage as an image, with the account holder completing CAPTCHA and OTP prompts.
To capture a GST Portal webpage with Power Automate for desktop (PAD), launch or attach to a supported browser, let the authorized account holder complete the portal’s login checks, navigate to the page, then use the browser action Take screenshot of web page. Choose the entire page or a specific element, save it to a file, and inspect the image. Use the portal’s own download when you need an official certificate or the underlying return data; a screenshot is only an image of what was displayed.
What you need
- Power Automate for desktop and a desktop flow.
- A supported browser such as Microsoft Edge, Chrome, Firefox, or Internet Explorer. For an external browser, the required browser extension or a compatible WebDriver may need to be installed. Microsoft describes its built-in Automation browser as ready to work out of the box.
- An authorized GST Portal user to complete sign-in and any CAPTCHA or OTP prompts in the normal portal interface.
- A writable destination folder with enough space for the screenshot.
PAD cannot attach to a browser opened under a different system user. Some physical-interaction options also require the browser to remain visible and the target tab focused. See Microsoft’s webpage automation setup guide for browser setup details.
Capture a GST Portal webpage in Power Automate
- Create a desktop flow. Open Power Automate for desktop and create a new flow for this task.
- Launch or attach to a browser. Add Launch new Microsoft Edge (or the corresponding action for another supported browser) and navigate to the GST Portal. If using an already open browser, attach to the instance running as the same Windows user as PAD.
- Complete authentication manually. Have the taxpayer or authorized staff member enter credentials and handle CAPTCHA, OTP, and other prompts in the portal. GSTN describes CAPTCHA during login and OTP authentication in applicable situations. Design the flow to pause while the authorized user completes these checks; do not try to bypass them or assume unattended login will work.
- Navigate to the page to document. Use the normal portal menus and confirm that the intended page and relevant content are visible. For example, certificates are under Services > User Services > View/Download Certificates.
- Add the screenshot action. In the browser automation actions, add Take screenshot of web page. Select Entire web page for a long page or Specific element when only a particular page region is needed.
- Choose output settings. Select File as the destination, enter a full path and filename such as
C:\GST\captures\certificate-page.png, and choose an image format. PNG is a practical choice for text-heavy pages; it is one of the formats supported by the action, not a GSTN requirement. - Run and review. Run the flow with the intended page displayed. Open the saved file and check that it is not blank or clipped and that it shows the right page. Before sharing or filing it, check for GSTINs, taxpayer names, addresses, invoice details, OTPs, or other confidential information and redact where appropriate.
Microsoft’s browser automation actions reference documents the screenshot action, its full-page and specific-element choices, and its supported file formats: BMP, EMF, EXIF, GIF, JPG, PNG, TIFF, and WMF. The action can also save to the clipboard if that better fits a subsequent step in your desktop flow.
Choose the right capture scope and format
| Need | Setting or approach | Notes |
|---|---|---|
| Record a long webpage | Entire web page | Review the result for clipping and confirm that content loaded before capture. |
| Show one panel, table, or page region | Specific element | The target element must exist on the page when the action runs. If it cannot be found, confirm the correct page is open and inspect the element selection. |
| Keep text and layout crisp | PNG or another suitable image format | PNG is a practical option, especially for text. It is not an official portal document format. |
| Pass the image to another flow step | Clipboard destination | Use this when the next step consumes clipboard content; use a file when you need a persistent artifact at a known path. |
| Retain an issued certificate | GST Portal’s PDF download | GSTN documents certificate downloads as PDF. |
| Retain GSTR-2B statement data | GST Portal’s Excel and/or JSON download | GSTN documents viewing and downloading a generated GSTR-2B statement in those formats. |
A screenshot records the rendered page, not the original document or structured data. It does not by itself establish that a filing was submitted, make an image an official certificate, or guarantee acceptance as evidence.
Keep the portal authentication with the user
GSTN’s login guidance describes CAPTCHA and OTP checks in applicable situations. Keep the account holder or authorized staff member in control of credentials and complete those prompts through the regular portal. A desktop flow can automate navigation and capture after access is granted, but the workflow should accommodate interactive authentication instead of attempting to defeat it.
For sensitive pages, capture only what the task requires. Store the resulting image in an access-controlled location and review it before sharing. These are prudent handling steps; the cited GSTN screenshot-related guidance does not prescribe a specific redaction process.
Common problems and fixes
| Problem | Likely cause | Fix |
|---|---|---|
| PAD cannot find or attach to the browser | The browser belongs to another Windows user, or the external browser extension/WebDriver is missing or incompatible. | Open the browser under the same system user as PAD. Install or repair the applicable extension or compatible WebDriver, then retry. |
| Authentication blocks the flow | The portal is showing CAPTCHA, OTP, or another access check. | Pause the flow and have the authorized user complete the prompt normally, then continue after the intended page loads. |
| Screenshot is blank or shows the wrong page | The capture ran before navigation or page rendering completed, or the wrong tab was active. | Confirm the target page and tab before capture. Add a suitable wait in the flow and inspect the image after each run. |
| Selected element is not captured | The target element is absent, changed, or not selected correctly on the current page. | Reopen the intended page, verify the element selection, and use entire-page capture if a specific element is not necessary. |
| Image file is missing | The path is invalid, the folder does not exist, or the flow cannot write to it. | Use a full path, create the destination folder, and confirm the current user has write access. |
| Capture requires the browser to stay visible | A physical-interaction option needs the browser in the foreground with the target tab focused. | Keep the browser visible and focused during that step, or adjust the flow to use supported browser automation actions. |
Performance, reliability, and file handling
- Wait for the right state. Authentication and page loading can make fixed timing unreliable. Make sure the intended content is present before capturing, and review the output when portal pages change.
- Use the smallest useful scope. A specific-element capture can avoid recording unrelated page content; use full-page capture when the surrounding context or a long page matters.
- Keep the browser session predictable. Run PAD and the browser as the same system user, and avoid changing tabs or closing the browser during capture.
- Plan storage and retention. Screenshots are image files; choose a folder with appropriate access and retention for taxpayer information. Use the portal’s download for records that need to remain in the portal’s supplied document or data format.
- Do not treat image capture as portal verification. Inspect the output for clipping, stale content, or a failed page, and use the portal itself to verify filing or document status.
Or skip the browser setup
For a public webpage, ScreenshotNeo can return a screenshot with one GET request. Its API can return PNG, JPEG, WebP, or PDF, and the available parameters include full-page capture and other capture controls. Do not send GST Portal credentials or use this approach to bypass portal authentication; this example targets a public page.
See the ScreenshotNeo API documentation for the API and options.
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()
open("shot.webp", "wb").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 Bun.write('shot.webp', res);
ScreenshotNeo accepts cookie and consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each of those steps can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers report the page verdict and billing status. Its MCP server lets AI agents use take_screenshot, get_page_info, and capture_pdf. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots. See ScreenshotNeo and the docs. Sign up for 1,000 free screenshots a month, with no card required.
Frequently asked questions
Can Power Automate take a screenshot of only part of a webpage?
Yes. Choose Specific element in the webpage screenshot action and select the page element you need.
Does a screenshot replace downloading a GST certificate?
No. GSTN provides issued certificates as PDF downloads. A screenshot is an image of the displayed page.
Can I save a GSTR-2B screenshot instead of its data file?
You can capture the page for a visual record, but GSTN documents Excel and/or JSON downloads for the generated GSTR-2B statement. Use those downloads when you need the statement data.
Can the flow sign in without a person present?
The login guidance describes CAPTCHA and OTP prompts in applicable situations. Build the flow so the authorized user completes them in the portal.


