Ep. 37: Automating My Podcast Workflow with Claude Code
The podcast workflow automation is officially done! In this episode I walk through what the new process looks like end-to-end, how Claude Code was used to build a custom Node.js command line tool, and what APIs actually are and why they matter for making it all connect. This is a practical (and yes, somewhat techy) look at agentic AI doing exactly what it’s supposed to do: handling the repetitive stuff so the creative work stays yours.
WE DID IT!!!
WE DID IT. WE AUTOMATED THE PODCAST WORKFLOW!
So if you read last week’s episode (Ep. 36 – My AI Wishlist) you know I listed two things I wanted to build with AI:
- An automation for my podcast workflow, because I spend half my life copy and pasting.
- A custom dashboard for my messaging coaching services.
Item number 1 has been crossed off the list and the podcast workflow has been completed. It took about 7 hours, but it’s done, and the what, the why, the how is exactly what we’re diving into today.
What Got Automated (And What Didn’t)
Right off the bat: none of the actual creative portion of this podcast is being outsourced. Ever. I am not telling Claude to write my podcast outline for me or anything like that.
The whole podcast process starts with me writing a super detailed outline, and that’s what I read from to record the actual episode. What comes after that is what I’ve automated, and I managed to automate like 95% of it.
Remember, I turn each episode into a newsletter (which is what you’re reading right now) AND a blog post. That’s honestly the main reason I wanted to automate the workflow. It’s a ton of redundant file creation and copy-pasting.
Here’s what the old podcast workflow used to look like:
Write the outline → record the podcast → paste the outline into Claude → have Claude generate the show notes and Companion → copy show notes to a Google Doc → copy Companion to a Google Doc → edit both → copy show notes to an episode post on my website → upload the episode MP3, cover art, and schedule the episode → copy the Companion to an email template in Kit to go out as the newsletter and schedule it → copy the Companion to a blog post on my website → generate a featured image on Gemini (which has been sucking lately) → upload that to the blog post → schedule the blog post → copy the podcast episode link and blog post link to a master Google Sheet.
Lots of copy and paste. Annoying AF.
What Claude Code Built
The best way to complain is to create something, so I went ahead and used Claude Code (which is Anthropic’s agent tool) to create a custom Node.js command line tool (aka a bunch of files) that automates the workflow.
I realize your eyes might be starting to gloss over, stay with me.
I had Claude Code build a set of instructions that I run from the terminal of my computer that allow Node.js (a computer program) to access all the parts of my workflow, including Google Drive, my website, and ConvertKit, and execute tasks in all of those places.
Quick note on the terminal: The terminal is simply a text-based way to control your computer. We’ve all seen it at one point or another. It seems scary until you actually use it.
Now, the back end of this process is even more techy, so I don’t want to go super deep into it, but I do want to expose you to it generally, and quell your fears by pointing out that Claude Code builds, runs, executes, and debugs all of this. I’m not out here being a master coder or anything like that.
Yes, there were some steps I needed to do manually, but Claude Code walked me through everything. And the best part? I just talked to it in natural language (including talk to text which is my favorite way to get shit done way faster), and any time I got stuck I simply took screenshots, uploaded it to the chat window, explained my problem, and it would tell me exactly what to do. What a time to be alive.
The New Workflow
So, before I dive into how this automation works, I want to start at the end and share what my podcast workflow looks like now that I have the robots assisting me.
The new podcasting workflow:
Write outline in Google Doc in the episode folder → record the episode → run the command npm run generate — “Ep title” → Claude generates the show notes and Companion → Node.js creates a Google Doc for each in that episode folder → I review and edit each document → I create the featured image and upload it to the episode folder → run the command npm run publish — “Ep title” → Node.js creates a blog post draft on my website, creates a podcast episode draft on my website, uploads the featured image to my website, and creates a newsletter draft inside of Kit → I review everything, schedule it, pull the URLs and post them to the Google Sheet, and done.
The generate portion of the workflow (where Claude makes the show notes and Companion) takes about 2.5 minutes (I timed it), and I just let that run while I’m recording the episode. The actual publish command (where Node.js makes the google drive files and and also creates the drafts on my website and inside of Kit) takes just a few seconds to execute.
Alll of this is billed as part of my Claude Pro $20/month subscription. In reality, the only portion that actually uses Claude is generating the show notes and Companion. Claude isn’t involved for anything else.
I however, am still involved in the process somewhat, namely to check things, which is exactly how I wanted it. As you can see, there is so much less copying and pasting and creating documents, which for me is such a relief.
Some folks have no issue doing all that copy and pasting, and they absolutely wouldn’t spend 7 hours building out a tool to automate it. That’s completely valid and also speaks to what I believe to be one of the best use cases for AI: building custom solutions for personal problems.
Let’s Talk About APIs
As for how this thing works under the hood: ultimately, what Claude Code built is a bunch of files that have a specific set of instructions and allow Node.js to interact with my Google Drive, my website, and Kit via what is called an API.
That acronym right there, API, is what I want to expose you to. API stands for application programming interface, and it’s the way that applications are able to communicate with and interact with each other.
So as part of this workflow, I had to get Google Drive to talk to my website, and Google Drive to talk to Kit. In order to do that I had to set up those APIs. Setting up means getting a specific key for each (a long-ass string of numbers and letters) and then saving those keys inside of a file that the Node.js program reads.
So again, to summarize: I had Claude Code build a bunch of files that live on my computer, that a program called Node.js can read and execute, and is how Google Drive talks to my website and my Kit account.
Worth noting, for those of you who are techy and/or have good memories, last week I said I thought I’d build this workflow automation with MCPs and a CLAUDE.md file. That is absolutely another feasible way to build this, but after chatting with Claude and identifying that this process is deterministic (one input, one output, runs the same every time), it made more sense to build it this way. I might take that other approach for the custom dashboard buildout though, so stay tuned.
It’s More About Patience Than Anything Else
Overall, I just want you to understand that automations like this are possible, and that Claude Code can build them and will hold your hand through all the tasks it needs you to perform. Yes, a bit of tech tenacity is needed, but honestly, it’s more like patience than anything, because you just need to be willing to take screenshots and literally chat with Claude when you don’t understand things or when they don’t work.
I know this episode is a bit techy, but that’s because I do think there’s value to at least looking under the hood, but ultimately I really just hope you take away a glimpse of what is possible and start experimenting yourself. That truly is the best way to learn.
How I Used AI This Week
Each episode I share a quick example of how I used AI that week.
Clearly, this week I used AI to build out this podcast automation workflow.
I used Claude Code for 100% of this build, and I’m going to do a future episode on what exactly Claude Code is and how to install it, because I know it’s a pretty weird and intangible concept until you’ve actually dove in and played around.
So if you’re scared, I gotchu. If you’re feeling curious and brave, go for it.
Da Wrap-up
The podcast workflow automation is done and I’m honestly so stoked. Yes, it took 7 hours but for me it was absolutely worth it, and I hope that you see that building custom solutions to your own specific problems is one of the best (and coolest) uses for AI.
As always, endlessly grateful for you and your curiosity.
Catch you next Thursday.
Maestro out.