Hourly

Collect each month's liked songs in their own playlist

Songs you like go into a playlist named for the month, created when the month starts.

Runs: Hourly
Apps: Spotify
AI: Not needed
Access: user-library-read, playlist-modify-private

Send this to your assistant

Create a ClickRuntime automation: every hour, add songs I just liked on Spotify to a playlist named after the current month, like 'October 2026', and create it if it doesn't exist.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

You like songs all month, and they pile into one long Liked Songs list with thousands of entries. It is hard to remember what you were listening to in March or to share what you liked last month with a friend. Some people make a playlist per month by hand, but it takes discipline, and it breaks the first time you forget to add a song. Over a year, the habit fades, and the months blur together.

Every hour, ClickRuntime checks for your recently saved tracks, skips ones it has already processed, creates a playlist for the current month if it does not exist, such as October 2026, and adds the new songs to it. Each month ends up with a playlist of what you liked then, built without any work from you.

Music lovers who like to look back on a period through its songs, and those who share monthly lists, use it most.

What you get out of it

Each month becomes a time capsule
Opening a playlist from last June brings back what you were listening to then. It works like a diary in music, and you never had to remember to keep it.
Sharing monthly picks is easy
Send a friend the playlist of this month's favorites with one link. Many people post these publicly each month, and it only needs the heart icon to build. A tidy playlist per month also gives friends something concrete to follow and enjoy.
Liked Songs stays usable
You can keep liking songs as before. The monthly playlists sit alongside the main list, giving smaller sets that are easier to browse and shuffle than thousands of tracks. Your existing habits remain the same, and nothing about how you listen has to change.
Nothing is added twice
Songs already processed are skipped, so a track you liked, unliked and liked again does not appear repeatedly in the playlist or take space in earlier months. A clean monthly list is easier to enjoy, and it keeps counts honest when you look back.
The habit costs nothing
Hand-made monthly playlists usually last a few weeks before they are forgotten. Automating the work means the series continues for years without any decision from you. The playlists simply appear, month after month, like a diary you never had to write.

How it works

What happens, step by step

Every hour, ClickRuntime checks the songs you've recently liked on Spotify.
It skips any it has already handled.
If this month's playlist, named like "October 2026", doesn't exist yet, it creates it.
The new liked songs are added to that month's playlist.

Before it runs live

Connect Spotify

What you get

RunsHourly

Collect each month's liked songs in their own playlisttoday, 9:00Succeeded

Spotify · October 2026Added 3 songs to October 2026: Harbour Lights, Acme Static, Northwind Drive

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Act only on the items that match your own rules, and skip the rest
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other Spotify steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

liked_songs_into_a_monthly_playlist.pyexample

from datetime import datetime
from clickruntime import on_trigger, credentials, http, state, report_fetched

API = "https://api.spotify.com/v1"

@on_trigger
def run(event):
    h = {"Authorization": f"Bearer {credentials.connection('spotify', 'personal')}"}
    since = state.get("last_added_at") or datetime.utcnow().isoformat() + "Z"
    saved = http.get(f"{API}/me/tracks", headers=h, params={"limit": 50}).json()["items"]
    new = [s for s in saved if s["added_at"] > since]
    report_fetched(len(new))
    if not new:
        return {"added": 0}
    name = datetime.utcnow().strftime("%B %Y")
    playlists = state.get("playlists") or {}
    if name not in playlists:
        playlists[name] = http.post(f"{API}/me/playlists", headers=h, json={"name": name, "public": False}).json()["id"]
        state.set("playlists", playlists)
    http.post(f"{API}/playlists/{playlists[name]}/tracks", headers=h,
              json={"uris": [s["track"]["uri"] for s in reversed(new)]})
    state.set("last_added_at", new[0]["added_at"])
    return {"added": len(new), "playlist": name}

FAQ

Common questions

What are the playlists called?

They are named after the month and year, for example October 2026, and are created the first time you like a song in that month. You can give another naming pattern, such as a prefix, if you want them grouped.

Why check hourly rather than instantly?

Spotify does not send an event when you like a song, so the run checks recent saves on a schedule. Hourly keeps the playlist reasonably current while staying within normal API limits. Hourly is a good balance.

Are the playlists public or private?

They are created as private by default, so only you see them. If you want to share a month, you can make that playlist public in Spotify, or tell your assistant to create them as public from the start.

What permissions does it need?

user-library-read, playlist-modify-private. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run each time it checks. Checks that find nothing new and stop right away aren't counted.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Hourly