GOG Games Scraper
Pricing
Pay per usage
GOG Games Scraper
Scrape GOG games, catalog search, new releases, discounts, coming soon titles, demos, and changelog updates with normalized metadata and prices.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Newbs
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Scrape GOG catalog data for game discovery, new releases, discounts, coming soon titles, demos, and product changelog signals. The actor returns normalized game metadata and price data for catalog monitoring, release tracking, and promotion analysis.
What it can scrape
- GOG catalog search by keyword.
- Latest GOG releases sorted by release date.
- Discounted GOG games and current deals.
- Coming soon titles and demo listings.
- Product changelog and metadata update signals where the public product API exposes them.
Useful inputs
mode:search,new_releases,deals,demos,coming_soon, orupdates.query: game title or catalog search text.category: GOG genre, tag, or feature filter such asrpg,strategy, orindie.gameId: GOG product ID for update checks.gameUrl: GOG product URL for update checks.maxItems: maximum records to return.
Output fields
Each result includes platform, platformGameId, title, url, matchSource, signalTypes, description, developer, publisher, releaseDate, lastUpdatedAt, coverImageUrl, tags, genres, supportedSystems, hasDemo, demoUrl, isComingSoon, isReleased, currentPrice, originalPrice, currency, discountPercent, isFree, sourceFetchedAt, and raw source data.
Rows also include sourceKind, sourceConfidence, and sourceNotes. Product changelog rows are high confidence; metadata-only update fallback rows are low confidence and should not be treated as full patch notes.
Billing result definition
One result is one normalized GOG game, discount, release, demo, coming-soon, changelog, or metadata update row written to the default dataset. The SUMMARY key-value record and optional Firebase cache writes are not dataset results. If you run this actor with Apify pay-per-event monetization, price the result-item event so pricing maps directly to delivered dataset rows.
MCP connector export
Optionally select outputConnectors to send delivered GOG rows to your own MCP-connected tools through Apify's MCP proxy. Auto mode can call common send/post/write/log tools with a markdown or JSON payload. For tools with strict schemas, set connectorToolName and connectorToolArgumentsJson, using template values such as {{markdown}}, {{records}}, {{summary}}, {{datasetId}}, and {{runUrl}}.
Example inputs
