GoShipFast logoGoShipFast

Publishing

Connecting Each Platform

Platforms fall into two camps: those with real publishing APIs, and those without. GoShipFast connects both, but the mechanics differ — OAuth for the first camp, a managed browser session for the second. Here's each one.

X

Click Connect and authorize in the browser; the redirect completes the connection automatically. Publishing, including thread splitting from the multi-platform preview, is fully automatic from then on.

LinkedIn

Same one-click OAuth flow as X. Variants adapted for LinkedIn's longer-form, whitespace-friendly conventions publish directly.

Bluesky

Enter your Bluesky handle; you're redirected to bsky.social to authorize, and publishing is automatic afterward.

Threads

Threads has no public publishing API, so the connection is a managed browser session:

  1. Paste your Threads profile URL.
  2. A managed browser window opens — log in to Threads once. The session is kept and reused for later publishes.
  3. An account picker lets you reuse an already-logged-in account, log in to a new one, bind an account to this brand, or remove one — useful when you run several brands with separate accounts.

At publish time, a helper drawer walks the final steps: copy the adapted content, download the images, open threads.com, post, then confirm "I've published it" (optionally saving the live URL so the post is tracked like any other).

Instagram

Same managed-browser pattern as Threads: log in once in the managed window, pick the account to bind to this brand, and follow the helper at publish time.

Xiaohongshu (小红书)

Xiaohongshu has no public API either. Connection:

  1. Paste your profile URL.
  2. Log in via QR code in the managed browser (rednote.com accounts work too). The session syncs and persists; the account picker manages multiple accounts across brands.

Publishing runs through the 3-step helper — copy all content, download all images, open the creator page — and on the desktop app it can drive the managed browser directly. Record the published URL and the post joins your tracked, published set.

Notes that apply everywhere

  • Sessions are stored server-side per brand and reused; you log in once per platform per brand, not per post.
  • Expiry is watched. When any platform ends a session, a notification tells you before it costs you a scheduled post. See Platform Connections.
  • Every platform's content is editable pre-publish in the multi-platform preview — connection determines where you can publish, never what gets published.

Your own blog is the remaining channel, and its git-based flow gets its own page: Publishing to Your Blog.