> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/create-and-publish/publishing-and-distribution/submit-to-spotify.md). # Submit to Spotify Submit your podcast to Spotify, link a podcast that is already on Spotify, or remove it. Use this task to list your podcast on Spotify. Podigee sends your feed to Spotify, waits until Spotify lists the podcast, and then informs the podcast owner by email. ## Before you start * You need the owner, admin, or editor role for the podcast, with permission to edit the podcast. * Automated submission needs a paid plan on the account of the podcast owner. The free Launch plan does not include it. * The podcast must be published and must not be restricted to invited listeners. * At least one episode must be published and publicly available. * The podcast needs a cover image and a description. {% tabs %} {% tab title="Classic view" %} ### Submit the podcast 1. Open the podcast and select the **Exports** tab. 2. In the **Audio** section, select the **Spotify** tile. 3. Select **Submit**. Podigee sends the podcast title and the MP3 feed URL to Spotify. The tile shows **Pending**. Podigee checks at regular intervals whether Spotify lists the podcast. When the podcast is available, the tile shows **Published**, and the podcast owner receives the email **The podcast "\[podcast title]" has been published on Spotify** with the button **Go to Spotify**. The tile shows a warning when the podcast has no author name. Add the author in the podcast details before you submit. ### Link a podcast that is already on Spotify 1. Open the **Spotify** tile. 2. Select **If your podcast is already on Spotify, click here**. 3. Enter the podcast link in **Spotify URL**. The link has the form `https://open.spotify.com/show/<22 characters>`. 4. Select **Save**. ### Remove the podcast from Spotify 1. Open the **Spotify** tile of a published connection. 2. Select **Remove this podcast from Spotify**. Podigee asks Spotify to remove the feed and clears the connection. ### Expected result The **Spotify** tile shows **Published**. The web player and the podcast website can show a Spotify button. ### If you cannot complete the task * The tile shows a lock icon: the account of the podcast owner is on a plan without automated submissions. * **Submit** is disabled: add the cover image and the description, and publish one episode. * The status stays **Pending**: Spotify did not list the podcast yet. Podigee continues to check. Do not submit again. {% endtab %} {% tab title="Podigee workspace" %} The workspace offers Spotify only while you publish the first episode of a new podcast. The flow has the steps **Recording**, **Show**, **Episode**, and **Publish**. For an existing podcast, the workspace has no Spotify action. Submission, the link to a listed podcast, and the removal from Spotify happen in the classic view. ### Complete the task 1. In the show selector, select **Add a new show**. The page **Drop your recording.** opens. 2. Drop the file on **Drop your video or audio file here**, or select **Choose a file**. 3. Wait until the page shows **Draft progress** and **Prepare destinations**. The note reads **Nothing publishes or submits externally until you review and confirm.** 4. Find the **Spotify** card. It shows **Needs action** and **Set up Spotify from your podcast feed. This will not publish this episode.** 5. Select **Set up Spotify**. The card shows **In progress** and **Spotify setup is being prepared.** 6. To skip Spotify for now, select **Connect later** instead. The card reads **You can set up Spotify after the draft review.** Select **Set up** to open the card again. 7. Select **Review draft details** and complete the **Show** and **Episode** steps. 8. In the **Publish** step, select **Publish episode** or **Schedule episode**. **Set up Spotify** sends the same submission as **Submit** on the **Spotify** tile in the classic view. The conditions under "Before you start" apply. The **Spotify** tile in the classic view shows **Pending** and later **Published** for this submission. ### Expected result The **Spotify** card shows **Connected** and **Spotify is set up for this show.** ### If you cannot complete the task * The card shows **Needs attention** and **Spotify could not be prepared. Try again when you are ready.**: the account of the podcast owner is on a plan without automated submissions, or Spotify did not accept the feed. Complete the publication, then submit the podcast on the **Exports** tab in the classic view. * The card shows **Coming later** and **Spotify setup will be available here soon.**: the show does not exist yet. Continue with the flow. * The sidebar marks **Reach** as **Not yet**, and the **Channels** page shows **We are still building this**: the podcast already exists. The workspace has no Spotify action for it. Use the **Spotify** tile on the **Exports** tab in the classic view. * You need the **Spotify URL** field or **Remove this podcast from Spotify**: these parts of the job exist only in the classic view. {% endtab %} {% endtabs %} ## Next step [Submit to Deezer, Listen Notes, and Amazon Music](/documentation/create-and-publish/publishing-and-distribution/submit-to-deezer-listen-notes-and-amazon.md) --- # 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://docs.podigee.com/documentation/create-and-publish/publishing-and-distribution/submit-to-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.