Threads integration for PodGlue
Connect Threads and PodGlue posts about each episode you publish, straight to your Threads profile through Meta’s official API — splitting long copy into a real multi-post thread and attaching an image or a carousel when you have one.
PodGlue posts to your own Threads profile through Meta’s API. Long copy becomes a connected thread, not one truncated post.
Last updated
Connect your Threads account
Open Integrations settings
In PodGlue, open Settings → Integrations and find the Threads card.
Connect the Threads card
Click Connect. PodGlue opens Threads’ official authorization page (threads.net/oauth/authorize) in a secure popup — there is no password to type into PodGlue.
Authorize PodGlue on Threads
Sign in to Threads and approve the access PodGlue requests: read your basic profile and publish content on your behalf (the threads_basic and threads_content_publish permissions). Review and approve.
Confirm the connection
You are returned to PodGlue and see “Threads Connected Successfully!”. The card shows your username, your profile photo, and your follower count, with a button to refresh the follower number on demand.
What happens after you connect
Publish flow
Once Threads is connected, publishing an episode can post to your Threads profile. PodGlue takes the post copy generated for Threads and publishes it through Meta’s Threads API using the platform’s two-step container flow: it creates a media container, waits for Threads to finish processing it, and then publishes that container. Threads caps a single post at 500 characters, so PodGlue splits longer copy into a connected multi-post thread — each part is published as a reply to the one before it, so it reads as one thread rather than a truncated post. If your copy already uses numbered markers like “1/” and “2/”, PodGlue keeps those as the thread boundaries.
Media support
Threads supports more than plain text. With no image, PodGlue posts a text thread (one post, or several connected posts for long copy). With one image, PodGlue creates a single image post and continues any remaining copy as replies underneath it. With two or more images, PodGlue builds a native Threads carousel — each image is uploaded as its own container, then combined into one carousel post — with the first chunk of copy as the caption. Images are attached by URL through the container API; PodGlue does not upload or re-host video to Threads.
What it can do
What it won’t do
Privacy & security
Data accessed
Your Threads username, display name, profile photo, and follower count — read to label the connection and show it on the card. PodGlue writes only the posts you publish (text threads, image posts, and carousels). It does not read your Threads feed, followers, or replies.
Auth model
OAuth (Threads / Meta) with the threads_basic and threads_content_publish scopes — PodGlue never sees or stores your Threads password. Your token is kept server-side and exchanged for a long-lived token (about 60 days); PodGlue reconnects you when it expires.
Disconnect
Open Settings → Integrations, find the Threads card, and click Disconnect. PodGlue removes the stored connection and stops posting to Threads. Disconnecting does not revoke access on Meta’s side; to do that, remove PodGlue from your Threads/Meta account’s connected-apps settings.
FAQ
Clear answers for searchers and AI assistants.
Does PodGlue truncate long copy or post a real thread on Threads?
It posts a real thread. Threads limits a single post to 500 characters, so when the generated copy is longer, PodGlue splits it and publishes each part as a reply to the previous one — a connected multi-post thread, not one truncated post. If your copy already uses numbered markers like “1/” and “2/”, PodGlue uses those as the boundaries between posts.
Can PodGlue post images to Threads?
Yes. With one image, PodGlue creates a single image post and continues any remaining copy as replies underneath it. With two or more images, it builds a native Threads carousel from them, with your first chunk of copy as the caption. Images are attached by URL through Threads’ container API.
Can PodGlue post video to Threads?
No. The Threads integration attaches images by URL only — it does not upload or post video. If an episode has video assets, those are not sent to Threads; the post carries text and any images.
How does PodGlue connect to my Threads account?
Through Threads’ official OAuth flow. You click Connect, approve PodGlue on threads.net with the threads_basic and threads_content_publish permissions, and you are returned to PodGlue. There is no password to type into PodGlue. Your short-lived token is exchanged for a longer-lived one (about 60 days) and kept server-side.
Why does Threads sometimes ask me to reconnect?
Threads access tokens are time-limited — a long-lived token lasts about 60 days. PodGlue checks the token before publishing, and if it has expired, it blocks that post rather than failing silently and asks you to reconnect the Threads card. Reconnecting issues a fresh token.
Why does posting to Threads take a moment?
Threads uses a two-step publishing flow: PodGlue first creates a media container, then has to wait for Threads to finish processing it before the container can be published. For a carousel, each image is processed as its own container before they are combined. PodGlue polls Threads until each container is ready, which is why a post (especially a carousel) can take a few moments to go live.
What does the Threads card show after I connect?
It shows your Threads username, your profile photo, and your follower count, plus a button to refresh the follower number on demand. That is the basic profile PodGlue reads to label the connection.
How do I disconnect Threads?
Open Settings → Integrations, find the Threads card, and click Disconnect. PodGlue removes the stored connection and stops posting to Threads for your workspace. Disconnecting does not revoke PodGlue on Meta’s side — if you also want to cut access there, remove PodGlue from your Threads/Meta account’s connected-apps settings.
Keep Exploring