Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Build an n8n workflow with three nodes: Schedule Trigger → HTTP Request → Telegram (Send Photo). The schedule starts each run, the HTTP Request captures the rendered page through a screenshot API, and Telegram sends the resulting image to a chat or channel. Browserless documents this pattern with an n8n template; ScreenshotNeo is another API option if you want consent banners, popups, and chat widgets removed before capture.
What you need before building the workflow
- An n8n instance and permission to create and activate workflows. n8n documents its core nodes and deployment options at Explore n8n Docs.
- A screenshot API account and token. Browserless documents a screenshot endpoint authenticated with a token; its n8n integration page provides HTTP Request examples. See Browserless Screenshot API and Browserless n8n integration templates.
- A Telegram bot credential configured for n8n, plus the destination chat ID or channel username. For a channel, add the bot and grant it permission to post.
- The page URL you want to capture. If it contains private or account-specific information, consider what the screenshot service and Telegram destination can access.
How to schedule a website screenshot and send it to Telegram
1. Add the Schedule Trigger
Create a workflow and add Schedule Trigger as its first node. Set the cadence you need, such as hourly or daily, using the options shown in your n8n version. Check the node’s current documentation and your workflow settings for timezone behavior and activation requirements: n8n documentation. Do not assume an inactive workflow will run on its schedule.
2. Configure an HTTP Request to capture the page
Add an HTTP Request node after the trigger and configure it to call your screenshot provider. Browserless’s documented screenshot API uses POST, accepts the target page URL and optional screenshot settings, and returns image data in the requested format. Authentication uses a token query parameter. Follow its current endpoint and request-body documentation rather than copying settings from an unrelated provider.
A request has this general shape; replace the endpoint and body fields with the exact values required by your Browserless account and API documentation:
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePOST https://production-sfo.browserless.io/screenshot?token=YOUR_BROWSERLESS_TOKEN
Content-Type: application/json
{
"url": "https://example.com",
"options": {
"fullPage": true,
"type": "png"
}
}This is an illustrative request shape, not a tested workflow export. Browserless supports optional screenshot settings and PNG, JPEG, or WebP output; consult its Screenshot API documentation for the current endpoint, accepted fields, and options. Store the token in n8n credentials or another supported secret mechanism and reference it in the request. Do not paste a live token into workflow text, shared exports, or screenshots.
#1 Best Overall
In the HTTP Request node, configure the response so n8n receives image data in a form the next node can use. Browserless’s n8n examples show image output as a buffer or base64. The exact binary property name and whether conversion is needed depend on your node configuration and output; inspect an actual run rather than assuming a universal field name.
3. Add Telegram Send Photo
Append the Telegram node, choose Message → Send Photo, select your Telegram credential, and set the destination chat ID or channel username. The operation can receive binary image data, a Telegram file_id, or an HTTP URL. For this workflow, binary data is usually the direct route when the screenshot is already in the n8n execution. Enable the binary-file option and enter the binary property name shown in the preceding node’s output. Add a caption only if useful. See the n8n Telegram node documentation and the Send Photo operation reference.
If you choose a Telegram file_id, use an image already stored by Telegram. If you choose an HTTP URL, ensure Telegram can fetch that image from the internet and that access controls do not block it. The n8n documentation notes that most channel message operations require the bot to be added to the channel; check its posting permissions if delivery fails.
4. Run once, inspect the data, and activate
- Run the workflow manually before relying on its schedule.
- Inspect the HTTP Request output. Confirm it contains a valid image and identify whether it is binary or base64 and, if binary, the property name.
- Match the Telegram node’s input to that output. If the screenshot is base64 rather than binary, use the appropriate conversion step before Send Photo.
- Check Telegram for the image in the intended chat or channel.
- Activate the workflow and verify the schedule and timezone in the current n8n UI and documentation.
This is documentation-based setup guidance, not a claim that a live workflow was executed or that delivery has a particular timing guarantee.
Choosing how the image reaches Telegram
| Input type | Use it when | Check before sending |
|---|---|---|
| Binary image data | The HTTP Request or a conversion node already holds the screenshot in the workflow. | Use the actual binary property shown in the execution output; convert base64 if necessary. |
Telegram file_id |
The image is already stored in Telegram and you want to reference that file. | Use a valid file ID for the image and destination. |
| HTTP URL | The screenshot is hosted somewhere Telegram can retrieve it. | Verify the URL is reachable by Telegram and is not private, expired, or blocked. |
These input options are documented for Telegram’s Send Photo operation. The best choice depends on where the image is at the point the Telegram node runs.
Browserless API or a managed screenshot API?
Browserless documents a hosted screenshot endpoint and an n8n template using HTTP Request, which can reduce the work of running a browser yourself. Managing browser rendering directly gives you more responsibility for the browser environment and its maintenance. Compare the setup effort, capture controls, credential and data handling, and ongoing infrastructure burden for your use case. The cited Browserless pages establish its API and integration examples, not comparative pricing or service-level performance.
Rank #3
For a managed option, ScreenshotNeo is a website screenshot API and MCP server. It accepts a URL in one GET request and can return PNG, JPEG, WebP, or PDF. Before capture, it can accept consent banners and remove 60+ known consent platforms, newsletter popups, and chat widgets; each step can be disabled. Only clean shots are billed: bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and responses identify the page verdict and billing status in headers. Its MCP server includes tools for AI agents to take screenshots, get page information, and capture PDFs.
Free tools Windows power users keep installed
One-click scans. No signup required.
Or skip the browser setup
Call ScreenshotNeo from an HTTP Request node and pass its image response to Telegram. For example, this cURL request captures a page as WebP; the endpoint and API details are in the ScreenshotNeo documentation:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpIn n8n, configure HTTP Request to make the equivalent GET request with access_key and url parameters, then make its image output available to Telegram’s Send Photo node as binary data. Check the response output to set the correct binary property in your workflow.
- Cookie banners, popups, and chat widgets are removed before the shot.
- Bot checks, blank pages, and failed loads are never billed.
- An MCP server lets AI agents take screenshots.
- 1,000 screenshots a month are free with no card; paid plans start at $5 for 3,000.
Sign up for ScreenshotNeo’s free plan.
Troubleshooting
Telegram sends no image or reports a photo-input error
- Check the HTTP Request output to see whether the response is binary or base64.
- If it is binary, make sure Send Photo uses the actual binary property name. If it is base64, convert it to binary before sending.
- If you use a URL, confirm it is publicly retrievable by Telegram and still valid when the workflow runs.
Posting to a channel fails
Add the bot to the channel and confirm it has permission to post. A chat ID or channel username must identify the intended destination.
The screenshot request fails
- Confirm the target URL is valid and reachable by the screenshot service.
- Check that the endpoint, HTTP method, token, and request body match the provider’s current API documentation.
- Keep the authentication token out of shared workflow exports and logs where possible; use n8n’s credential handling.
The page is incomplete or captured at the wrong moment
Page load timing, full-page capture settings, and interactions can change what appears in an image. Review the provider’s optional screenshot settings and verify the result against the target page. If the site renders content after initial load, adjust the provider’s supported wait behavior where available.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →The scheduled run does not happen
Confirm the workflow is active and review the Schedule Trigger’s timezone and cadence settings in the current n8n interface and documentation. Exact controls and behavior can vary by n8n version and workflow setup; check the current node reference rather than relying on an assumed menu path.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Privacy and operating costs
A scheduled capture may contain personal, confidential, or account-specific page data. Decide whether the screenshot API may process that page and whether the Telegram chat or channel is an appropriate destination. Do not treat a public image URL as private simply because it is difficult to guess.
Each workflow run makes a screenshot API request and sends an image through Telegram. Choose the cadence based on how often the page changes and how many captures you need; the available Browserless sources do not establish pricing or service-level guarantees. For ScreenshotNeo, the stated plans are Free with 1,000 shots per month and no card, Starter at $5 for 3,000, Growth at $15 for 15,000, Pro at $39 for 60,000, Scale at $99 for 250,000, and Business at $249 for 1,000,000; yearly billing gives two months free, and every feature is on every plan.
Frequently Asked Questions
Can n8n send a website screenshot to a Telegram channel?
Yes. Use Telegram’s Send Photo operation with the channel username or chat ID, and ensure the bot has been added with permission to post.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Does this workflow need a browser installed on the n8n host?
Not when you call a hosted screenshot API such as Browserless or ScreenshotNeo. If you manage browser rendering yourself, the browser environment becomes your responsibility.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
