tr Skip to content

When a new podcast episode is published in WordPress, transcribe audio in AssemblyAI

When a new post is published on your WordPress site, FlowMattic sends the episode’s audio file to AssemblyAI to be transcribed. It suits a podcast site where new posts are episodes.

WordPress AssemblyAI

2 steps Setup ~5 min Used on 2.7k sites Free to import

The When a new podcast episode is published in WordPress, transcribe audio in AssemblyAI workflow on the FlowMattic canvas, with 2 steps across WordPress, AssemblyAI
The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

A transcript makes a podcast episode searchable and gives you text for show notes, captions and quotes. Uploading each file to a transcription service by hand is a chore you have to remember. This workflow hands the audio to AssemblyAI as soon as the episode post goes live.

The WordPress trigger, New Post, fires when a new post is published. FlowMattic passes the post's data, including its custom fields, to AssemblyAI, where Transcribe Audio transcribes an audio or video file. Map the URL of the episode's audio file into that step. A test run shows which field holds it, for example a custom field your podcast plugin fills in.

Two things to know. The trigger fires for every newly published post of any type except pages, not only podcast episodes, so use this on a podcast-only site or add a Filter. And as imported, nothing uses the transcript. Add a step after AssemblyAI to save or publish it.

Show notes for a weekly podcast

Your podcast site publishes one post per episode. Each one goes to AssemblyAI, and you write show notes from the transcript.

Accessible episodes for listeners

Transcripts let listeners who are deaf or hard of hearing follow each episode once you add them to the episode page.

Quotes for social posts

With a transcript for every episode, finding the line worth quoting on social media takes a search, not a relisten.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

  1. Step 1Trigger
    WordPress New Post

    Fires when a new post is published, for any post type except pages. The post's title, content, permalink and custom fields are passed on, so you can find the audio file URL.

  2. Step 2Action
    AssemblyAI Transcribe Audio

    Sends the episode's audio file to AssemblyAI for transcription. Map the field that holds the audio URL and connect your AssemblyAI account. Check what the step returns in a test run.

What you need

  • FlowMatticCore
  • AssemblyAI AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

  • Add a Filter after the trigger that continues only when the post type or category marks a podcast episode, so blog posts aren't sent to AssemblyAI.
  • If the step returns a transcript ID instead of finished text, add AssemblyAI's Get Transcript action after it to fetch the transcript by that ID.
  • Add AssemblyAI's LeMUR Summarize action to turn the transcript into a short summary you can use as a starting point for show notes.

Questions about this workflow

Does the WordPress trigger only fire for podcast episodes?

No. New Post fires for every newly published post of any post type except pages. Add a Filter on post type or category if your site publishes other posts too.

Where does the AssemblyAI step get the audio file?

From the field you map. The trigger passes the post's custom fields, so an audio URL stored by your podcast plugin can be mapped. Run a test to find it.

Is the transcript added to the WordPress post?

Not as imported. The workflow ends at AssemblyAI. Add a step that updates the post or saves the text somewhere, using what AssemblyAI returns.

Will editing an already published episode start a new transcription?

No. The trigger fires on a post's first publish, not on later updates.

Import this workflow into your WordPress site

Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.

30-day money-back guarantee Unlimited workflows and runs Self-hosted

Customers who run it every day

Rated 4.8 out of 5 by customers
Read more reviews

Flowmattic is a noteworthy option for businesses looking for a self-hosted alternative to Zapier. With its user-friendly interface and a strong set of features, it is a top pick for those in need of a reliable WordPress automation solution.

Creative-Minded Multimedia

The main advantage of the plugin that it can turn your WordPress installation into a powerhouse, just imagine that you can replace all other integration with only this one.