Docs / Publish

Threads

Connecting a Threads profile, the video and words a Threads post carries, its one topic tag, daily limits, and keeping the 60-day connection fresh.

ChannelForge posts each episode to your Threads profile as a video post with a few lines of text and one topic tag, on the channel's slots. Threads is in every paid plan.

Before you connect#

You need a Threads profile — the one made from your Instagram account.
Connecting needs the editor role or above. Disconnecting needs an admin or owner.

Connect#

Open Settings → Connections and press Connect on the Threads card.
Threads asks you to sign in with your Instagram account.
It asks to read your profile and to publish posts. Allow both.
Back on Connections, the profile shows with its name, @username and when its connection expires. Link it to a channel under Which account each channel posts as.

Permission	Why
`threads_basic`	To know which profile connected, and to find a post whose answer was lost
`threads_content_publish`	To publish the posts

What is posted#

Part	What Threads receives
Video	The episode as a 720 × 1280 copy. Threads fetches it from a private link that works for an hour; the copy is deleted once the attempt is over.
Text	The title, the hook line when it fits, and the channel's call to action only if it asks for one — at most 500 characters (an emoji counts as several)
Topic	One topic tag: the channel's own Threads topic, else the episode's first hashtag, else the channel's lead hashtag — never "shorts" or "reels"
Never	A hashtag in the text, a link, an @mention that would tag a stranger

Threads takes videos of up to 5 minutes and 1 GB, so every episode goes whole.

When it posts#

On the channel's slots, after YouTube, Facebook, Instagram and LinkedIn and before Bluesky and X — or with Post now on the episode page. A channel that chose no platforms under Post to posts to Threads too, once a profile is linked.

Threads lets a profile publish 250 posts through apps in 24 hours. ChannelForge keeps each profile to 25 a day, well below that, so a busy channel never floods it.

Never twice#

When Threads may have published a post but the answer was lost, the attempt keeps its Threads container and is marked may be live. The next try reads the profile first: a post that went out is recorded; a container that never published is published then — never a second one. A slot looks again after 15 minutes; Look for it, then retry on the episode page does it at once.

When Threads asks the profile to wait#

Threads says	The profile waits
Too many requests	About an hour
The day's posts are used up	It is looked at again after an hour
The profile is temporarily blocked	A day

None of these uses a try: the episode waits, and the post's line on the episode page says why.

Reconnecting#

A Threads connection lasts 60 days. ChannelForge renews it by itself when it posts, once fewer than 30 days are left (and the connection is at least a day old), and the Connections page shows the new expiry. A profile that does not post for 60 days runs out, and is marked expired: reconnect the next time it is used. Press Add on the Threads card and sign in again — the same profile is updated, and its channel link stays.

To remove ChannelForge's access at Threads, use Settings → Apps and Websites in Meta's settings, where Facebook and Instagram are too.

Good to know#

Threads posts are counted, but their numbers are not read: the Analytics page shows "no metrics yet" for them.
Threads can post a channel's photo carousels, with one topic tag and no hashtags.

Troubleshooting#

"Threads would not exchange the code … — a code works once, so start again." The connection took too long or the page was reloaded. Connect again.

The profile is marked expired. It did not post for 60 days, or Threads refused the connection. Reconnect it.

"Threads refused the post". Threads' reason follows. The post is marked failed and the next slot tries again, up to three tries.

Something missing or unclear? Tell us and we will improve this page.