Automated Setlist and Lyrics Management with Spotify and Google Docs

somdn_product_page

This workflow streamlines the process of managing a band or artist’s setlist by automating the creation of a Spotify playlist, collecting song lyrics, and documenting details in Google Docs. Designed for musicians and event organizers, it helps quickly prepare for performances by automatically gathering song information, verifying artist and song titles, fetching lyrics, and organizing the data for easy reference.

Here’s how it works step-by-step:

1. **Trigger** – Initiated manually via the ‘Test workflow’ button.

2. **Get Data from Google Sheets** – Retrieves a list of songs with artist names and titles from a specified Google Spreadsheet called ‘Setlist_Manager’.

3. **AI Verification** – Uses an AI language model to verify and correct artist names and song titles for accuracy.

4. **Lyrics Retrieval** – Fetches lyrics from a lyrics API based on the verified artist and song title.

5. **Document Preparation** – Creates a Google Docs document named with the current date to store the final setlist.

6. **Populate Song Details** – Inserts song titles, artist names, and lyrics into the Google Doc, formatting the setlist for easy review.

7. **Spotify Integration** – Creates a new Spotify playlist with today’s date, searches for each song, and adds each track to this playlist.

This workflow is especially useful for live bands preparing setlists, playlist curators, or anyone needing an organized, automated way to gather and document music sets efficiently. It reduces manual effort, ensures data accuracy, and keeps all relevant information in one easily accessible location.

Node Count

11 – 20 Nodes

Nodes Used

@n8n/n8n-nodes-langchain.informationExtractor, @n8n/n8n-nodes-langchain.lmChatOpenAi, googleDocs, googleSheets, httpRequest, manualTrigger, spotify, stickyNote

Reviews

There are no reviews yet.

Be the first to review “Automated Setlist and Lyrics Management with Spotify and Google Docs”

Your email address will not be published. Required fields are marked *