Threads settings
What UseNadia does on Threads
Section titled “What UseNadia does on Threads”A Threads channel is your Threads profile. UseNadia publishes:
- a text on its own, up to 500 characters;
- an image, or a video;
- a carousel: several images or videos attached to the same part;
- extra parts, published as chained replies: each part replies to the previous one, forming a thread under your post. Each can carry its own media, like the first.
On a published post, UseNadia can also read the replies received, answer them and hide them, see Replies.
UseNadia reads the profile’s live analytics in Analytics: views, likes, replies, reposts and quotes. Each post has its own as well (the same five).
UseNadia keeps no history for Threads (no Videos or History tab). The Threads API has no private messages: no Threads inbox, and no comment → DM automation on this channel.
Connecting
Section titled “Connecting”In Add Channel, click Threads: you are sent to Threads and you allow UseNadia to read your profile, publish, read and manage the replies to your posts, and read your insights. The Threads profile must already exist: it is created from the Threads app.
The token renews in the background: there is nothing to redo unless you remove access from Threads.
Replies
Section titled “Replies”On a published post, View comments, in the action bar of the calendar, opens the post’s replies at every level, oldest first, read from Threads when it opens. On each one:
- Reply: a public reply from your profile, 500 characters max;
- Hide / Unhide: on a top-level reply only (hiding a reply also hides the ones under it), never on your own.
No deletion: the Threads API lets no app delete someone else’s reply. Hide
it instead. The same actions go through the public API
(Inbox) and the MCP
(commentsListTool, commentActTool): a deletion is refused there with a
400 error that says so.
Settings schema
Section titled “Settings schema”Threads has no settings of its own: settings only carries
__type: "threads", in posts[].settings of
creating a post:
{ "settings": { "__type": "threads" }}Fields
Section titled “Fields”| Field | Type | Required | Description |
|---|---|---|---|
__type |
string |
Yes | Must be threads |
What each part becomes depends on its media: none, a text; one, an image or a video (MP4); several, a carousel.
Limits
Section titled “Limits”- 500 characters per part, Threads’ limit.
- Threads fetches each media from its address: it must have been uploaded to UseNadia first.
Full example
Section titled “Full example”A carousel of two images, then a chained text reply:
{ "type": "schedule", "date": "2026-11-23T08:30:00.000Z", "shortLink": false, "tags": [], "posts": [ { "integration": { "id": "your-threads-integration-id" }, "value": [ { "content": "100 days, one video a day. Two images to sum it up.", "image": [ { "id": "media-id-1", "path": "https://…/before.jpg" }, { "id": "media-id-2", "path": "https://…/after.jpg" } ] }, { "content": "The details, numbers included: https://usenadia.com", "image": [] } ], "settings": { "__type": "threads" } } ]}Known errors
Section titled “Known errors”| Message | What happens |
|---|---|
The channel shows a red dot, or Threads access token expired |
The token could not be renewed (access removed from Threads, password changed): reconnect the channel from your channel list |
Post text exceeds 500 characters limit |
A part is over 500 characters: split it into two parts |
One of the media URLs is invalid or inaccessible, make sure it's being uploaded to UseNadia first |
Threads could not read a media: upload it to UseNadia, then use the address it returns |
Error from Meta: We restrict certain activity to protect our community |
Meta blocked publishing on this profile: try again later, or publish this post from the Threads app |
User restricted |
The Threads profile is restricted by Meta: check its status in the Threads app |
threads does not let an app delete a comment: hide it instead |
A reply deletion asked through the API or the MCP: hide the reply instead |
A failed post carries the message on its calendar tile (red badge) and in the failure notification.