Building a Concert Radar with OpenClaw: Scraping Multiple Sources for Artist Shows

✍️ OpenClawRadar📅 Published: March 9, 2026🔗 Source
Building a Concert Radar with OpenClaw: Scraping Multiple Sources for Artist Shows
Ad

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
Ad

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

Ad

👀 See Also

Migrating from OpenClaw to Cowork + Claude Code: A Developer's Experience
Use Cases

Migrating from OpenClaw to Cowork + Claude Code: A Developer's Experience

A developer migrated from OpenClaw to Anthropic's Cowork with Claude Code sessions, citing better cron jobs, dispatch routing, and persistent memory. The setup uses a three-layer context design with Cowork handling orchestration and Claude Code executing code in repositories.

OpenClawRadar
Splitting AI Agents to Prevent Context Dropping
Use Cases

Splitting AI Agents to Prevent Context Dropping

A developer describes splitting a single AI agent into three specialized agents with separate memory and workspaces to prevent context window issues. The agents communicate through a simple mailbox system to coordinate tasks like trip planning.

OpenClawRadar
OpenClaw AI Agent Manages LinkedIn Ads Workflow with 2.65% CTR
Use Cases

OpenClaw AI Agent Manages LinkedIn Ads Workflow with 2.65% CTR

A developer built an AI agent named Patrick using OpenClaw to handle their entire LinkedIn Ads workflow, including data pipeline creation, ad copy generation, and approval via a custom review tool. One AI-generated ad achieved a 2.65% click-through rate, outperforming all manual ads.

OpenClawRadar
Building Non-Coding AI Agents with Claude Code: Three Practical Examples
Use Cases

Building Non-Coding AI Agents with Claude Code: Three Practical Examples

A Reddit user shares their personal setup for creating AI agents using Claude Code, detailing three specific implementations: an automated morning briefing agent pulling from emails, todos, and calendar; a tmux-based pipeline for capturing Substack articles; and a meeting summarization agent.

OpenClawRadar