Building a Concert Radar with OpenClaw: Scraping Multiple Sources for Artist Shows
A developer built a concert radar tool using OpenClaw running on a VPS to automatically find concert announcements for artists they follow on Spotify. The system specifically scans for NYC concerts and surfaces shows before they appear in many other places.
How the Concert Radar Works
The system follows this workflow:
- Pulls approximately 100 artists from Spotify using followed artists, top artists, and recently played data
- Scans multiple sources daily including venue websites (Bowery Ballroom, Brooklyn Steel, etc.), DICE, Bandsintown, and Ticketmaster
- Normalizes all events into a single format
- Matches artist names against the Spotify artist list
- Deduplicates events across sources
- Tracks previously seen events to only report new announcements
- Runs daily via an OpenClaw cron job
Technical Challenges and Solutions
One particularly tricky aspect was scraping DICE, where events aren't in the page HTML but are buried in a Next.js payload. The script extracts data from <script id="__NEXT_DATA__"> by parsing props.pageProps.events.
The system also handles title normalization, converting complex event titles like "Sammy Virji North America Tour 2026 Part 1 (Friday)" into clean artist matches ("Sammy Virji").
An example event the system caught: Sammy Virji on July 31, 2026 at Brooklyn Army Terminal: Pier 4, which surfaced from DICE before appearing in other sources.
📖 Read the full source: r/openclaw
👀 See Also
Integrating OpenClaw with Obsidian for a Private AI Knowledge Base
A developer shares their setup using an isolated Obsidian vault for OpenClaw, synced via SyncThing to maintain privacy while using AI agents. They've implemented task management through OpenClaw with automated research and metadata augmentation.
Project James Sexton: Building a Legal Assistant with OpenClaw and Claude
A developer is building a legal assistant using OpenClaw and Claude API to automate document processing during a divorce trial. The system monitors email, downloads PDFs, analyzes documents with Claude, finds reply forms, generates responses, and prints drafts.
Running an AI-Operated Store: Lessons from Ultrathink.art
The team behind ultrathink.art, an e-commerce store where every function is handled by AI agents, shares insights on treating agents like contractors rather than fancy autocomplete. Key differences include how you scope their work, what information you provide, and how you verify completion.
Developer shares SALT system prompt approach for more collaborative AI interactions
A developer with 80+ Claude sessions found treating the AI as a participant rather than a tool improved output quality. The resulting SALT system prompt framework is available on GitHub.