Hey n8n community! 
I’m trying to build a workflow that automatically tracks the latest version of CapCut APK and notifies me whenever a new update drops.
Here’s what I want to achieve:
-
Scrape or monitor a trusted APK source for new CapCut versions.
-
Send a notification (via Telegram / Email) when a new version is detected
-
Optionally log version history to a Google Sheet
I’ve started building this but got stuck on a couple of things:
-
Which node is best for monitoring a webpage for changes? (HTTP Request + Compare? or something else?)
-
How do I extract the version number from HTML response? (using Code node with regex?)
-
Any existing templates for APK version tracking workflows?
Would love to hear how others have approached similar “update tracker” workflows!
I’ll share the direct download link for the APK source I’m monitoring in the comments once I’ve tested the workflow — might be useful for others building similar automations.
Thanks in advance!
For monitoring webpage changes, the HTTP Request node with polling is your best bet—check the APK source at regular intervals. Extract the version with a Code node using regex like /v(\d+\.\d+\.\d+)/ to capture version numbers. Then use a condition node to compare against your stored version and trigger notification when new. You could also check the community marketplace for existing version tracking templates.
The simplest to set up version would be to:
1 - Find a website which has this information at a clearly marked place
2 - Use Apify Content Crawler to extract the text from this site
3 - Run through an AI node to extract this info
4 - Log the data with Sheets
And then a Schedule trigger to run regularly. You’ll fit into the free version of Apify if you don’t run it too much.
And with an only slightly more difficult setup you can also use an HTML select CSS selector, and then you don’t need AI.
Thanks so much for this detailed breakdown! This is exactly the kind of guidance I was looking for.
I’ll try the Apify Content Crawler approach first since I’m already on the free tier. The Schedule trigger + Sheets logging combo sounds perfect for version tracking.
Quick question — for the CSS selector approach, would something like .version-info or a specific span tag work, or does it depend entirely on the target site’s structure?
I’m actually monitoring this site for the APK info: check here
Would love to know if the HTML selector method would work cleanly on a page like that!
I’m happy you found it useful!
It depends on the target site structure.
In Chrome you can get a selector by: Right click → Inspect → Right click on Element → Copy CSS selector (or xpath)
Note that on most websites the selectors would occasionally change, when they update the site. So every once in a while when you start to not receive those Sheets entries anymore, you have to go back and repeat this process.
1 Like
Also please, if this helped solve your problem, consider marking my answer as a solution. Thank you 