Works with Threads
Let each visitor connect their own Threads account in one click, then show their posts in your app and publish to their feed when they say so.
What you can build
Apps that work with the posts people already write: an archive of someone's Threads posts they can search, a drafts board that publishes the finished one, a journal that turns an entry into a post, a page that gathers what a group of friends has posted. Every visitor connects their own Threads account, so the same app works for everyone who opens it.
How it connects
A connection to the visitor's own account. Your app declares Threads in
backend.js with one sentence saying why, shows a Connect button, and the
platform does the rest: the consent card, the Threads sign-in, holding the
credential and refreshing it. Your app has no client id, no secret and no
token anywhere in its code. Your backend reads and posts through the
@vibes.diy/social library, as the visitor.
What it can read and do
| Scope | Your app can |
|---|---|
threads_basic |
Read the visitor's Threads profile and their own posts, newest first, with text, link and time |
threads_content_publish |
Post to the visitor's Threads feed: text, or text with an image |
Posting is its own scope. The visitor reads "Post to your Threads feed as you" on the consent card next to your reason, and decides.
Starter prompts
- Make a page that shows my latest Threads posts as a tidy archive I can search by word.
- Build a drafts board where I write Threads posts, polish them, and publish the best one straight to my Threads feed.
- Make a gratitude journal that turns each entry into a short Threads post I can publish with one tap.
Good to know
- Each visitor brings their own account. Nobody pastes a token, and the app owner never sees anyone's credential.
- Ask for posting when the app posts. An app that declares only the read scope reads; adding the publish scope and asking again is how it starts posting.
- Post on something the person did. A tap on Publish is the shape people trust; tell them when a post lands and when it needs another try.
- A post carries text, or text with an image. The image is a public link Threads fetches itself.
Go deeper
- Connect accounts — the connection lane, the consent card and every refusal reason.
- The connections skill — the builder's own recipe.
- All integrations