Profile connection
The creator authorises one profile, and duplicate external mappings are rejected across workspaces.
Official Threads API integration
Threads publishing with a clear record of every step.
Novas maps one owner-authorised Threads profile through the official Threads API. Text and media workflows are validated, confirmed, processed, and measured without hiding the provider state.
What the connection is for
A narrow purpose for every provider permission.
Text and media publishing
Text, image, video, and carousel containers are published only after they finish processing.
Engagement snapshots
Views, likes, replies, reposts, quotes, and follower observations keep their exact capture time.
Permissions and formats
Only what the product needs. Nothing hidden in the background.
threads_basic
threads_content_publish
threads_manage_insights
threads_delete
Supported product formats
Text-only publishingSingle imageCarouselShort-form video
Safeguards that stay visible
- The current provider publishing limit is read before container creation.
- Queued or processing containers are never displayed as published.
- Remote deletion is separate from deleting the local content record.
- Unsupported and approval-blocked workflows stay manual or assisted.
Refreshable does not mean permanent
The long-lived grant is encrypted server-side and refreshed under a persisted lease. Provider removal, policy changes, or a missed refresh window still produce a visible reconnect state.
Provider state remains visible
Novas stores the returned post ID, processing state, provider metadata, permalink when available, and actual publication time. It does not infer completion from a queued job.
Your content stays yours.
Create a verified account, then connect only the profiles you own and choose to manage with Novas.