WordPress integration for PodGlue
Connect WordPress and PodGlue turns an episode into a real post on the site you own — audio player embedded, cover image set as the featured image, show notes in the body — and you decide whether it goes out live, as a draft, or queued.
You connect with a WordPress Application Password, not OAuth. PodGlue posts to your self-hosted WordPress site over its own REST API.
Last updated
Connect your WordPress account
Create a WordPress Application Password
In WordPress, open Users → Profile → Application Passwords, add one named “PodGlue”, and copy the password it shows you. This is separate from your normal login password and can be revoked on its own.
Open Integrations settings in PodGlue
In PodGlue, open Settings → Integrations and find the WordPress card.
Enter your site URL, username, and Application Password
Type your site address (e.g. https://yourshow.com), your WordPress username, and the Application Password you just created. PodGlue checks the address before saving anything: only public http(s) sites are allowed — internal, loopback, and private network addresses are blocked.
PodGlue verifies the connection
PodGlue makes a test call to your site’s REST API (/wp-json/wp/v2/users/me) to confirm the credentials work and the API is reachable. If it succeeds, the WordPress card saves and shows your site’s domain and username.
What happens after you connect
Publish flow
Once WordPress is connected, publishing an episode creates a post on your site through the WordPress REST API. PodGlue assembles the post body from the episode’s show notes and assets, embeds the audio player at the top, and — when you choose to include the cover — uploads your episode artwork to your Media Library and sets it as the post’s featured image. You pick the status before it goes out: publish (live immediately), draft (lands in WordPress for you to review and publish yourself), or future (a scheduled status — you set the publish time in WordPress). Re-saving the same site never creates a duplicate connection; it updates the one you already have.
Media support
PodGlue writes a standard Gutenberg post. The episode audio is embedded as a native WordPress audio block (a wp-block-audio figure with an HTML5 player and a “Download Episode Audio” link), followed by your show notes. Your episode cover is uploaded to the WordPress Media Library and set as the featured image. There is also an optional companion plugin, the PodGlue Bridge, which you install on your site to store extra PodGlue metadata with each post — guest name, key themes, summary, transcript, audio URL, and a JSON-LD SEO block it injects into your page head — and to show a “PodGlue Intelligence” panel in the WordPress editor.
What it can do
What it won’t do
Privacy & security
Data accessed
Your WordPress site URL and username (to label the connection) and the Application Password you create for PodGlue, all kept server-side. PodGlue writes the posts you publish, uploads your episode cover to your Media Library when you include it, and — if you install the Bridge plugin — stores episode metadata with each post. It does not read your existing posts or visitors’ data.
Auth model
WordPress Application Password (HTTP Basic auth over your site’s REST API) — NOT OAuth. You create the Application Password in WordPress, PodGlue stores it server-side, and you can revoke it from your WordPress profile without changing your main login.
Disconnect
Open Settings → Integrations, find the WordPress site, and remove it. PodGlue deletes the stored credentials and stops publishing to that site. You can additionally revoke the Application Password from Users → Profile → Application Passwords in WordPress.
FAQ
Clear answers for searchers and AI assistants.
Does PodGlue use OAuth to connect to WordPress?
No. Unlike the OAuth-based integrations, WordPress connects with an Application Password — a special credential you create in WordPress (Users → Profile → Application Passwords) just for PodGlue. It is separate from your normal login password, can be revoked on its own, and PodGlue uses it to call your site’s REST API.
Can I point PodGlue at any address, like a local or staging site?
No. When you connect, PodGlue validates the site URL and only allows public http(s) addresses. Internal, loopback, and private-network addresses (and anything that resolves to them, even after a redirect) are blocked. This is an SSRF guard that keeps the integration from being pointed at internal systems.
Can I publish as a draft instead of going live?
Yes. You choose the status for each post: publish to go live immediately, draft to land it in WordPress for you to review and publish yourself, or future, the scheduled status. For a future post you set the actual publish time in WordPress.
How does the episode audio appear in the post?
PodGlue embeds the audio as a native WordPress audio block at the top of the post — a wp-block-audio figure with a standard HTML5 player and a “Download Episode Audio” link — followed by your show notes. It uses your existing episode audio URL; PodGlue does not re-host the file.
Will my episode cover become the featured image?
Yes, when you choose to include the cover. PodGlue uploads your episode artwork to your WordPress Media Library and sets it as the post’s featured image, so it shows up in your theme and in link previews.
What is the PodGlue Bridge plugin and do I need it?
The Bridge is an optional companion plugin you install on your WordPress site. With it, each published post also stores PodGlue metadata — guest name, key themes, summary, transcript, audio URL, and a JSON-LD SEO block it adds to your page head — and you get a “PodGlue Intelligence” panel in the post editor. Publishing works without it; the Bridge just adds the richer metadata and schema.
Will PodGlue ever publish a private or non-publishable conversation?
No. If an episode is marked not publishable — for example a discovery call or sales call — PodGlue refuses to publish it to WordPress, regardless of any other setting. Non-publishable conversations never reach public surfaces.
Can I connect more than one WordPress site?
Yes. You can connect multiple WordPress sites to the same workspace. Connecting the same site again updates the existing connection instead of creating a duplicate.
How do I disconnect WordPress?
Open Settings → Integrations, find the WordPress site, and remove it. PodGlue drops the stored credentials and stops publishing to that site. For extra safety you can also revoke the Application Password from your WordPress profile.
Keep Exploring