> For the complete documentation index, see [llms.txt](https://help.webhash.com/webhash-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.webhash.com/webhash-docs/how-to-edit-every-component-on-your-website/embeds-bringing-the-web-to-your-website/spotify.md). # Spotify🎵 {% embed url="" %} Integrating your favorite Spotify content on your Link Tree decentralized website is a breeze. Just follow these simple steps:

* In the 1W3 editor, navigate to the collection where you want to add the Spotify integration block. * Click on the "Add Blocks" button and select the Spotify block from the available options.

* Paste the link to your desired Spotify music into the provided field within the Spotify block. * once you have pasted your song link click on the submit. * Save the changes and preview your website to see the embedded Spotify content.

With the Spotify block, you can easily share and promote your favorite music albums, playlists, shows, or radio mixes directly on your Link Tree decentralized website. Visitors to your website will be able to enjoy the Spotify content you've curated without leaving your site. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.webhash.com/webhash-docs/how-to-edit-every-component-on-your-website/embeds-bringing-the-web-to-your-website/spotify.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.