**What I scheduled** I built a daily automation for my music group that finds potential booking contacts for me. Every morning at 7 AM it uses Claude's web search to research real booking agents and venues, checks my ClickUp "Potential Bookings" list so it doesn't repeat anyone, and adds each new contact as a task card. Each card includes who they are, their location, how to reach them, why they fit, and the source link. I also added a failure alert. If any run breaks, it comments on a ClickUp task so I hear about it. **Scheduled task or loop?** Scheduled task. I ran it on Trigger.dev with a cron schedule. A loop only lives as long as my Claude session is open, and mine would need to be running on my laptop. A scheduled task runs in the cloud, so it fires at 7 AM whether my computer is on or off. This job needs to run every day without me, so that mattered. **One surprise** The part that surprised me was how much of a "set it up" job turned out to be about the boring edges: no duplicates, what happens when something fails, and how I find out. ClickUp also doesn't notify you about your own comments, so my first alert would have been silent. I had to add one setting (`notify_all`) to make it actually ping me. The automation is easy to build. Making it trustworthy while I'm not watching takes the extra work.