notetweet_obsidian

Posting from a note

NoteTweet for Obsidian lets you post to X, formerly Twitter, without leaving your notes. The plugin offers a composer opened with the Post tweet command, where you choose a named X account and write a single tweet or a thread. If you have text selected, it is ported into the composer automatically: a block marked THREAD START and THREAD END opens as a pre split thread, and any other selected text is auto split when it passes 280 characters. A separate command posts the current selection immediately, and another command parses the first THREAD START and THREAD END block in the active note and posts it as a thread. Threads are separated by a line containing only three dashes, and only the first thread block in a file is detected. After posting, a modal lets you delete the tweets you just sent. The plugin also supports multiple named X accounts, so a team or a person with several identities can pick which one to use per post, and it can append an optional tag to the note after posting so you can track what has already been shared. The composer shows a post button and, when scheduling is enabled, a schedule button, keeping the writing and sending steps close together inside the editor.

Credentials and security

NoteTweet stores account names, IDs, and the default account in the plugin's data.json, but every account's API key, API secret, access token, and access token secret are kept in Obsidian's built in encrypted Secret Storage rather than in that file. Because it relies on Secret Storage, the plugin requires Obsidian 1.13.0 or newer. The setup walks through creating an app in the X Developer Portal, where new apps are placed inside a project that is required for the X API v2. The portal shows the API key and API key secret at creation, and you generate the access token and access token secret after enabling OAuth 1.0a with read and write permissions. The README is clear that credentials appear only once in the portal and must be regenerated if lost, and that changing app permissions after generating a token requires regenerating the token or it stays read only. Each account has its own connection test that shows the exact reason X returned when verification fails, such as the client not enrolled message. Upgrading from older versions migrates credentials automatically into a named Default account, and if you previously used password based Secure Mode the migration button first prompts for that password so it can decrypt the stored values before moving them.

Images, scheduling, and troubleshooting

The composer supports images. You can hover a post and click the image button to pick a file from your vault, or paste an image straight in, in which case it is saved to your vault and then uploaded. You can also embed an image by typing a wikilink to a supported file type, including gif, jpg, jpeg, png, webp, and bmp. Image uploads are desktop only. Scheduling is optional and advanced: it uses a self hosted scheduler that owns its own X credentials and therefore its own posting identity, and it requires the Natural Language Dates community plugin for entering times. The troubleshooting section covers the most common failure, a 403 Client Forbidden with a client not enrolled reason, which means the app is not attached to a project. It also explains that a green connection indicator uses a read call and can stay green even when the app cannot write, so a 403 on Post usually means a read only access token or a hit free tier write cap. Authentication errors such as 401 can come from an incorrect system clock, expired tokens, or missing project attachment. The plugin is listed in the Obsidian community plugin browser, so most users install it from there rather than downloading a release zip.

Editorial conclusion

NoteTweet is released under the MIT license and, at the time of writing, the repository recorded 80 stars and was last updated on 2026-08-24.