The Jellypod Partner Program now pays 30% recurring commission for a year on every paid subscription you refer.
This is real revenue share, not a one-time credit. Refer someone who runs a training program, a course, or a newsroom, and once their team is paying you earn 30% of every invoice they pay Jellypod for their first 12 months as a customer.
How to apply
The program is application-gated. Apply at partners.dub.co/jellypod, or open the "Become a partner" card in the studio sidebar. Once you are approved, copy your unique partner link and start sharing, then track referred sign ups and payouts in the partner portal.
Commission is 30% of what each referred organization actually pays, for up to 12 months per customer. See the Referral Program docs for the full walkthrough.
Podcasts can now be generated via email. Automations now can have their own unique email address and anything sent is transformed into a podcast episode, generated from the email's content.
If you already write a newsletter or blog, email automations turn that content into a second channel. Subscribe your automation's address to your Substack, Ghost, or beehiiv, and every issue creates a new episode. Keep episodes as drafts to review, or enable Auto-Publish for a Public podcast you have connected to podcast directories.
Set up a new automation in the sidebar, then send a newsletter to the provided email address. Full documentation here in podcast automations.
How do you turn each newsletter issue into a podcast?
Open Automations, click New Automation, and choose Episode, then Continue.
Choose Inbound Email, then Continue. Name the automation, select the podcast that will receive episodes, and set the target duration.
Add standing instructions, such as the prompt below. Leave Auto-Publish off while you review the first episodes, then click Create Automation.
Copy the automation's Email address. Subscribe it to your newsletter or forward an issue from your inbox.
If the newsletter sends a subscription confirmation, Jellypod forwards it to your own inbox. Click the confirmation link there so future issues reach the automation.
Turn this newsletter into a podcast conversation for its readers. Preserve the author's main argument and supporting facts. Explain unfamiliar terms briefly. Skip navigation, subscription messages, and repeated footer text. Do not invent quotes or examples. Point listeners back to the original newsletter for the full article.
Each incoming email triggers its own episode; the automation does not collect several issues into a weekly digest. Review the draft against the original issue before publishing. Check names, numbers, and whether an opinion has been presented as a fact.
For automatic distribution, use a Public podcast, connect its RSS feed to your chosen podcast apps, and enable Auto-Publish after you are happy with the results. The automation guide covers private email addresses, confirmation emails, and daily run limits.
It is one of a few ways to trigger episode generation from tools you already use. Zapier and n8n can start the same run from a broader marketing stack.
We've added a new video template called Conversation that puts your hosts on screen side by side.
It's a natural fit for multi-host shows. Each host gets their own avatar, and that avatar pulses whenever they are the one talking, so viewers can always tell who is speaking.
How to use it
Open an episode in the editor and find the video player controls.
Click Template Library and pick Conversation in the "Choose a template" dialog.
Click "Use Conversation" to apply it, then generate your video.
We've made Conversation the default template for new episodes, so multi-host videos use it out of the box. It pulls in the hosts who actually speak in your script and renders their avatars, so add a photo to each host to get the most out of it.
You can now customize your podcast's brand and background color.
This color will apply to the background of your generated video and sets the accent on your podcast website. If a specific episode needs its own color, you can override the podcast-level color just for that episode without touching the rest of the show.
How to use it
To set a podcast-wide color:
Go to the podcast you'd like to edit.
Click through the "Edit Details" until the last step for "Additional Settings".
You'll see a Brand Color picker here. Drag the color wheel or type a hex value, and click "Save".
To edit the color per episode:
Open the episode you want to customize.
On the top navbar, next to the template and video orientation buttons, you'll see a new Color Picker.
Use that dropdown picker to set the episode color and click "Save as podcast default" to promote this color choice to the entire podcast, including future episodes.
If you don't manually choose a color, podcast episodes inherit the primary color from your cover art unless you override it.
You can now email someone a link to create a voice clone directly in your account, without them ever signing up for Jellypod.
Say you're producing an episode that needs your colleague as a subject matter expert. Invite them to record their voice as a Jellypod host, they upload a short sample from their phone, and a new host with their voice shows up in your library, ready to drop into the episode.
How to use it
On the Hosts page, click Create Voice Clone, select Invite a guest, and enter the guest's name and a short backstory.
Copy the invite link, or click Send email to deliver it from Jellypod.
Your guest opens the link, no Jellypod account required, and uploads or records voice samples directly.
When they submit, the new host lands on your Hosts page and you get an email letting you know it's ready.
Manage pending invites at Hosts → Invites: resend the email, copy the link again, or revoke it. Links are single-use and expire after 24 hours.
Your guest submits their own samples directly, and their acceptance is what authorizes the clone, not you uploading a recording on their behalf. See how AI voice cloning consent actually works for what that sequence looks like end to end.
You can now import an externally-generated script, letting Jellypod match script speakers to your account's existing host voices. If a speaker cannot be matched to an existing host, Jellypod will intelligently create a new host with a suitable voice from our Voice Library.
Say you wrote a multi-host interview in ChatGPT or a Google Doc. Import the script to Jellypod and as long as you put an existing host name on each speaker's lines, Jellypod will match it correctly. Any names where Jellypod can't find a match and only exist in the script are created automatically with a fitting voice and a short backstory. No setup beforehand required.
How to use it
Open the Home page and select Upload Existing Script.
Add your script. Paste it in, or upload a plain text, Markdown, Word (.docx, .doc), .rtf, or PDF file, up to 4 MB. Marking speakers in brackets like [Alex] gives the cleanest results, but plain prose works too - Jellypod detects who is speaking.
Review the preview. Every speaker it finds is listed, each tagged to show whether it matches an existing host or will be created as a new one.
Import. Jellypod matches speakers to your podcast's regular hosts first, then the rest of your account, and creates a new host for anyone left, picking a voice in the script's language and writing a backstory from their lines.
Audio generation starts automatically, the same as when the Podcast Agent writes a script from scratch. You don't need to click Generate Audio yourself.
Note: Newly created hosts don't impact your podcast's regular hosts and only apply for this specific episode. When this happens, a banner above the script editor will allow you to "Update Podcast" to sync your podcast's default cast to these hosts.
We've shipped a Jellypod skill that teaches an agent how to use your Jellypod account end to end: design hosts, attach sources, draft the script, and render audio against the real Jellypod API.
Hand the agent a prompt like "spin up a weekly podcast that summarizes my company's product updates" and it picks the voices, builds the hosts, pulls in your sources, and produces the episode in your library.
The skill is open source. Install instructions for your agent of choice (Claude Code, Claude.ai, ChatGPT, and others) are in the repo: github.com/Jellypod-Inc/skills.
We just added 30 new voices to the Jellypod Voice Library.
They sound more natural, more expressive, and more flexible across different podcast styles. Some episodes need a calm narrator. Others need a sharper editorial voice, a warmer co-host, or a more energetic presenter who can keep the conversation moving.
To try them, create a new host or edit an existing one, choose Voice Library, and browse the first three pages. Give a few samples a listen, compare the delivery, and pick the voice that feels right for your next episode.
They are live now. Give them a try the next time you are casting a host.
Click your avatar at the bottom-left of the sidebar and open Theme to choose Light, Dark, or System. Your choice is remembered the next time you sign in.
You write the prompt once. Jellypod takes it from there.
Automations let you put any podcast on a recurring schedule — daily or weekly — and have a fresh episode generated on its own. Each run kicks off an agent that researches the topic, outlines the script, generates the audio, and either drops it in your drafts for review or publishes straight to your feed.
It's the same pipeline that powers chat-based generation, just running for you on a clock.
What you configure
Prompt — what each episode should cover. e.g. "Cover the most important AI product launches and research from the past day."
Podcast — which show the episode posts to. Hosts and voices are inherited automatically.
Schedule — daily or weekly, the days of the week, time of day, and timezone. A live preview shows the next three runs.
Episode length — pick a duration preset.
Web Search — on by default, so the agent can pull current information before writing.
Auto-Publish — off by default. Runs save as drafts you can review, edit, and publish. Flip it on to ship every episode automatically.
What happens on every run
When the scheduled time hits, Jellypod spins up the episode in the background. You get an email when the draft is ready (or, with Auto-Publish on, when it's live). If a run fails, we email you with the reason and try again on the next tick. After three consecutive failures, we auto-pause the schedule so it doesn't burn credits silently — same if your account runs out of credits.
You can pause, resume, edit the prompt, or change the schedule any time from the Automations page in the sidebar.
Why we built it
Most podcasters who run a daily or weekly show are doing the same setup work over and over: open the app, paste the same prompt, generate, publish. Automations collapse that into a one-time setup. It's especially useful for news shows, recap formats, and any series where the topic is consistent but the content changes daily.
Find it on the Automations page in the sidebar.
Consistent publishing is also one of the strongest predictors of audience growth.
Automations is also the production step in a larger content pipeline: wire it to a schedule, an inbox, or a trigger from the rest of your stack, and audio becomes a channel that runs itself instead of a project someone has to remember to start.
