> 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/production/content-hub/generate-text-content-from-an-episode.md). # Generate text content from an episode Turn one episode into a blog article, LinkedIn post, newsletter block, or other text with Text Composer. Use this task to create a written piece from one episode with Text Composer. The text follows the podcast language and your brand guardrails. You can edit, copy, and download the result. Each text is a draft that Podigee AI proposes. Check the facts, the names, and the tone before you use the text. ## Before you start * You need Content Hub access. See [Get started with Content Hub](/documentation/create-and-publish/production/content-hub/get-started-with-content-hub.md). * The episode needs audio or video. ## Choose a format In the classic view, Text Composer offers these formats. SEO means search engine optimization. | Format | Available lengths | Default length | | ------------------------- | ----------------- | -------------- | | **SEO Blog Article** | Medium, Long | Long | | **LinkedIn Announcement** | Short, Medium | Medium | | **Newsletter Block** | Short, Medium | Short | | **Internal Comms** | Short, Medium | Short | | **Landing Page Copy** | Medium | Medium | | **Expert Thread** | Medium, Long | Medium | | **FAQ Article** | Medium, Long | Medium | | **Conference Abstract** | Short, Medium | Short | | **Webinar Outline** | Medium, Long | Medium | **SEO Blog Article** is the default format in the classic view. The Podigee workspace offers three formats: **LinkedIn post**, **Newsletter block**, and **SEO article**. **LinkedIn post** is the default format there. For the other formats, use the classic view. {% tabs %} {% tab title="Classic view" %} Before you start in the classic view: * The source picker must show **Ready for AI** for the episode. * Optional: set your tone, audience, and banned phrases in [Set brand guardrails](/documentation/create-and-publish/production/content-hub/set-brand-guardrails.md). Text Composer shows **Brand voice active** when guardrails exist and **Set Up Brand Voice** when not. ### Generate the text 1. In the sidebar, select **Text Composer**. You can also open a text card such as **SEO Blog Article** on the Content Hub home page. 2. Select the **Podcast** and the **Episode**. The episode list shows the 50 newest episodes. 3. Check **From This Episode**. It lists up to 10 texts that already exist for this episode, so you do not generate a duplicate. 4. Select the format and **Content length**. 5. Optional: add **Custom instructions**. Text Composer uses up to 2000 characters of your instructions. 6. Optional: set **Tone override**. Keep **Use brand default** or choose **Professional**, **Conversational**, **Formal**, **Inspiring**, or **Technical**. 7. Optional: enter a **Call-to-Action** button text and URL. 8. Start the generation. Text Composer creates a draft asset named after the format and the episode title. The status moves from **Queued** to **Generating** to **Completed**. If the generation fails, the status shows **Failed**. ![Text Composer in the classic view with the Source picker, the Format list with SEO Blog Article selected, Custom instructions, Tone override, and Content length](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-217fef919b67c4c4f1f018474c07a2f3a91766aa%2Fdoc-production-014-classic-text-composer-source.png?alt=media) Text Composer combines the source, the format, and the generation options on one page. ![Lower part of Text Composer in the classic view with the Call-to-Action fields, the Brand Settings panel, and the Generate Content button](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-d6cf54812789bc428ce477572c24103c376f2c7c%2Fdoc-production-015-classic-text-composer-generate.png?alt=media) The Call-to-Action fields and the Brand Settings panel sit above Generate Content, which needs a selected episode. Text Composer uses up to 40,000 characters of the episode transcript. The output language follows the podcast language. ### Edit the result 1. Read the text in the **Editor** tab. 2. Open the **Preview** tab. **Platform Preview** shows how the text looks on each platform. The platforms are an X thread, a website, internal communication, a blog post, a newsletter, and LinkedIn. 3. Change the text and select **Save**. 4. To let the tool rewrite the text, select **Regenerate Content**. Enter what you want to change, for example "Make it shorter" or "More formal tone". The tool uses the current version as context. While a generation runs, you cannot save, delete, regenerate, or download the asset. The page shows **This asset is currently being generated. Please wait until it is finished.** ### Use the result * **Approve** marks the text as **Ready**. * **Copy** copies the text. * **Markdown** downloads a `.md` file with the title, podcast, episode, format, and dates at the top. * **PDF** downloads a `.pdf` file. * **Delete** removes the text after you confirm **Are you sure you want to delete this text?**. ### Expected result The text appears in the content pack of the episode with status **Draft**, or **Ready** after you approve it. The Text Composer list shows 20 texts per page. ### If you cannot complete the task * The episode shows **Content not ready**: Podigee still prepares the episode content. Wait and reload. * The message **AI features are not available. Please upgrade your plan.** appears: the podcast owner's plan does not include Content Hub for this podcast. * The message **Failed to generate PDF. Please try again.** appears: repeat the PDF download. * The status stays **Failed**: select **Regenerate Content** to start a new generation. {% endtab %} {% tab title="Podigee workspace" %} In the Podigee workspace you create text on the **Create text** page of an episode. The page offers three formats: **LinkedIn post**, **Newsletter block**, and **SEO article**. There you create a draft, check it, edit it, copy it, and export it. The workspace does not include the other formats, **Content length**, **Tone override**, **Platform Preview**, the approval of a text, and the setup of brand guardrails. It also does not include the Content Hub dashboard, Ask Podie, outlines, the catalog, and content packs. Use the classic view for these. Drafts in the other formats show only in the classic view. The plan of the podcast owner decides if you can use the tool, also when you are a team member. A team member other than the owner or an admin also needs the organization permission **Content Hub**. The owner or an admin gives this permission in the classic view. To change the plan, you go to the plan page of the classic view. The tool works from the episode content. Podigee prepares this content from the recording. Each draft is a proposal from Podigee AI. Check it before you use it. ### Open the tool 1. Open the episode and go to the **Amplify** section. The section shows **Amplify this episode**. You can also select the quick action **Repurpose:** with the episode title on the **Overview** page. It opens the same section. 2. Find the **Create text** card. The pill **Ready** shows that you can use the tool. 3. On the **Create text** card, select **Open tool**. The **Create text** page opens. To go back to the episode, select **Back to episode**. ### Create a draft 1. On the **Create a draft** card, read the pill in the card head: * **Content ready**: the episode content is ready. Continue with step 2. * **Preparing content** or **Content queued**: Podigee prepares the episode content. Come back later. * **Content needed**: select **Prepare episode content**. Wait until the pill shows **Content ready**. * **Recording needed**: the episode has no recording. Add a recording in the classic view. 2. Under **Format**, select **LinkedIn post**, **Newsletter block**, or **SEO article**. 3. Optional: in **What should this draft focus on?**, add the audience, the angle, or the tone. 4. Optional: enter a **Call to action** and a **Call to action link**. 5. Select **Create draft**. While Podigee sends the request, the button shows **Creating draft**. The page shows the hint "Usually ready in a couple of minutes." The **Create draft** button stays available when the content is not ready. A draft that you start before the pill shows **Content ready** can fail. ### Check and use the draft 1. Find the draft in **Your drafts**. The status shows **Preparing**, **Queued**, **Creating**, **Ready**, or **Needs attention**. The list updates automatically while a draft is created. 2. When the status shows **Ready**, read the draft. Check the facts, the names, and the tone. 3. To change the draft, select **Edit**. The **Preview and edit** dialog opens. 4. On the **Edit** tab, change the text in **Draft**. On the **Preview** tab, see how the text looks. 5. Select **Save**. Copy and the exports use the saved version. 6. To copy the draft, select **Copy**. The button shows **Copied**. 7. To download the draft, open **More actions** and select **Export Markdown** or **Export PDF**. 8. To let the tool write the draft again with the same options, open **More actions** and select **Regenerate**. 9. To remove the draft, open **More actions** and select **Remove**. The dialog **Remove this?** shows "This removes the draft. Creating it again starts a new generation." Select **Remove**. ### Try a failed draft again 1. Find the draft with the status **Needs attention** in **Your drafts**. 2. Read the failure line and the band under it. The band tells you what to do. 3. If the band shows **Prepare episode content**, select it. Wait until the pill shows **Content ready**. 4. Select **Try again**. ![The Create text page in the Podigee workspace with a draft that shows Needs attention, its failure line, the remedy band, and the Try again button](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-a39f21d9248e86252bb9358a29d5da348eaacd33%2Fdoc-production-015-workspace-text-draft-failed.png?alt=media) A failed draft shows why it failed, what to do, and the Try again button. ### Expected result * After **Create draft**, **Try again**, or **Regenerate**, the page shows "Content generation started." * The draft shows in **Your drafts** with the status **Ready**. It also shows under **Created from this episode** in the **Amplify** section of the episode, with **Open in Text**. * After **Save**, the page shows "Draft saved." * After **Remove**, the page shows "Text removed." * After **Prepare episode content**, the page shows one of these notices: * "The episode content is being prepared. This can take a few minutes." * "The episode content is already being prepared." * "The episode content is ready." ### If you cannot complete the task When Podigee refuses to start a draft, the page shows "Content generation could not start." Under it, a band tells you what to do. A failed draft shows one of these lines, then the band and **Try again**: * "The episode content was not ready yet. Try again once it is.": start the draft again when the pill shows **Content ready**. * "The draft could not be written. Try again.": select **Try again**. The band shows one of these texts: * "This episode has no recording yet.": add a recording in the classic view. * "The episode content has not been prepared yet.": select **Prepare episode content**. Then try again. * "The episode content is still being prepared. Try again when it shows "Content ready".": wait, then try again. * "Your plan or your access did not include this tool when it ran. Try again.": try again. If it fails again, ask the podcast owner about the plan and your access. * "This is already being created. It appears here when it is ready.": wait for the draft that runs. * "The service behind this tool did not answer. Try again in a few minutes.": wait, then try again. * "If it fails again, contact support.": try again. If it fails again, select **Contact support**. **Prepare episode content** can show one of these alerts: * "You cannot prepare content for this episode.": the plan or your access does not include Content Hub for this show. * "Add a recording to this episode first.": the episode has no recording. Add a recording in the classic view. A transcription that failed stays in preparation. **Prepare episode content** then shows "The episode content is already being prepared." and starts nothing. Contact Podigee Support. Other messages on the **Create text** page: * "Copy did not work. Try again.": select **Copy** again. * "Your session ended. Reload the page and copy again.": reload the page, then select **Copy**. * "The export did not work. Try again.": select the export again. * "The draft could not be saved.": open **Edit** again and select **Save**. * "The preview could not be updated. Your text is still in the editor.": continue on the **Edit** tab. * "Automatic updates have paused. Reload the page to check again.": reload the page to see the status. When the tool is not available to you, the **Create text** card shows the reason and no **Open tool** button. When you open the page from a link, the page shows the tool name and the same reason. In the texts below, \[owner] is the name of the account owner. * "Your plan does not include written posts." with "Upgrade to create them.": the plan of the podcast owner does not include Content Hub. Select **See plans** to open the plan page. * "This account's plan does not include written posts." with "\[owner] decides the plan." or "The account owner decides the plan.": you are a team member, and the plan of the owner does not include Content Hub. Select **Ask \[owner]** or **Ask the show owner** to write an email to the owner. When the owner has no email address, the card shows no button. * "You do not have access to written posts." with "\[owner] can give you access." or "The account owner can give you access.": you do not have the organization permission **Content Hub**, or Content Hub does not work on this show. Select **Ask \[owner]** or **Ask the show owner**. When you are a collaborator on the show of a different account, the card shows no button. Ask the podcast owner for access. * "Not available yet" with "We are still building this": the tool is not available for your account yet. There is no action. * The **Amplify** section shows no tool cards: your account has no subscription. Content Hub needs an active subscription. {% endtab %} {% endtabs %} ## Next step [Organize generated content](/documentation/create-and-publish/production/content-hub/organize-generated-content.md) shows where to find your texts and how to mark them ready or archive them. Agents can list the same texts. See [Find generated content assets](/documentation/start-here/ai-agents/search-and-repurpose-episode-content/find-generated-content-assets.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/production/content-hub/generate-text-content-from-an-episode.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.