uplika Upload Helper

uplika lets an AI agent publish to your social channels. Some channels have no official publishing API, or can only be written to while you are logged in through a browser. This extension covers that case: it takes a post you asked uplika to publish and writes it through the channel's own editor, in your browser, using the login you already have. Naver Blog is supported today and more channels will follow. How it works: connect a channel that needs this extension in the uplika dashboard and the extension pairs with your workspace. There is nothing to paste. After that, when an agent publishes to that channel, uplika queues the post, and the extension opens the channel's editor in a tab, fills in the title, body, images and tags, and publishes. If your browser is closed, the post waits until it is open again. The same way, when you ask your agent to reply to a comment, like a post or a comment, or add a blog as a neighbor, the extension opens that page and does it as you would, one action at a time. If you turn on a comment-reply automation, the extension reads that blog's comment management page every five minutes, reports new comments to uplika, and posts the reply the automation chose. Turn the automation off and it stops reading. What it does not do: it never asks for or handles your channel passwords, and nothing about your channel login is ever sent to uplika or anyone else. Publishing uses the login already present in your browser. What stays on this computer is the uplika workspace pairing token, the workspace name, and the channel id it discovered. When you connect Naver Blog, the extension also keeps your own Naver sign-ins here so it can put the right account back before publishing, because Naver allows only one sign-in at a time. Removing an account or the extension deletes them. A uplika account (uplika.com) is required. The extension is not useful on its own. Permissions and why: storage keeps the pairing on this computer. tabs opens the channel editor tab and reads that tab's address. alarms reconnects after the browser wakes the service worker. The code that fills the post in is a content script that runs only on blog.naver.com. Access to blog.naver.com is where it publishes for the channel supported today; access to api.uplika.com is where it receives jobs and reports results. Attached images are fetched from inside the page that fills the post, so there is no permission for that address. Contact: support@uplika.com. Privacy policy: https://uplika.com/en/privacy