Skip to main content

Connect your X account

WriteMars publishes to and engages from X through a channel you connect with OAuth. A channel is one connected X account, scoped to the workspace you connect it in.

Where to connect​

Open Settings -> Channels from the sidebar. Connections are split into tabs, and the tab you connect under decides what the channel is for:

  • Publishing accounts — used to publish variants; also usable for auto-engagement.
  • Engagement accounts — used only to like, comment, or repost after a post is live. No scheduling.

Each tab shows Connected accounts on the left and Available platforms on the right. Admins and Owners also see an Overview tab with per-channel health badges.

Connect the channel​

  1. Open Settings -> Channels and pick the tab you want — Publishing accounts to schedule from this channel, or Engagement accounts for likes and comments only.
  2. Under Available platforms, click the Connect your X (Twitter) account card.
  3. Read the panel note — Important: Login to your X (Twitter) account before connecting to WriteMars. — and sign in to the correct X account in your browser first.
  4. Click Connect.
  5. Approve the permissions on X. While WriteMars finishes linking, you'll see Connecting X / "We are securely linking this X account to your workspace."
  6. You land back on Channels with a green Account connected alert: "You can use this account when publishing or managing engagement from this workspace."

If it fails, you'll see a Couldn't connect warning — "If it keeps failing, confirm you're signed into the correct account on that network." The OAuth screen uses whichever X session is active in your browser, so log the wrong one out (or use another browser profile) and try again.

If you're an Admin or Owner, the panel also shows a Connect as choice — My personal account or Company account — that sets who in the workspace owns and manages the channel. It works exactly as it does for LinkedIn; see Sharing and permissions for the matrix.

Grant the media-upload permission​

Uploading images and video to X needs the media.write permission, which WriteMars added after some accounts were first connected. A channel connected before then can post text but not media, and you'll see this banner on a post with an attachment:

This X account can't upload media yet — reconnect it in Channels to grant the media-upload permission.

The fix is to reconnect the same account so it re-grants the permission:

  1. Sign in to the same X account in your browser.
  2. Open Settings -> Channels, click the Connect your X (Twitter) account card, and click Connect.
  3. Approve on X.

WriteMars matches on the platform account and updates the connection in place — no duplicate channel is created.

Premium and verified long-form​

Standard X posts are capped at 280 characters. When the connected account is an X Premium subscriber (Basic, Premium, or Premium+) or a verified organization, WriteMars unlocks long-form and lifts the ceiling to 25,000 characters. The composer shows an LF pill once a post runs past 280 characters, and the preview folds long-form the way X does — with a "Show more" after the first 280 characters or 10 lines. Nothing changes for standard accounts; they keep the 280-character limit.

Token status and reconnecting​

X issues a refresh token, so WriteMars renews the connection automatically right before a platform call — no routine reconnect is needed. Reconnect only when a refresh isn't possible (you revoked WriteMars' access, or the token repeatedly fails auth) or to grant a new permission such as media upload.

When a token can't be used, the channel pauses and publishing and engagement through it are blocked. A scheduled publish on a paused channel is never marked failed — WriteMars defers it and retries automatically, noting the deferral in the post's Activity, so it goes out once the channel is reconnected. On a paused channel you'll see:

Paused — the connection keeps failing. Reconnect the account to resume.

Reconnect by re-running the Connect flow for the same account (the steps above). A successful reconnect clears the auth-failure pause. The ⋯ menu's Disconnect / Reconnect toggle only soft-toggles the channel on and off — it does not fetch a new token.

Engagement accounts for auto-likes​

Connect an X channel under the Engagement accounts tab to use it only for likes, comments, and reposts after a post publishes — it never schedules. Any connected X channel can engage, including a publishing one, so a dedicated engagement channel is optional. You wire these up per variant from the post detail page with Auto Likes, Auto Comment, and Auto Repost; see Auto-engagement.

Where Admins see channel health​

Admins and Owners get the Overview tab, which lists every channel shared with the workspace with a status badge — Healthy, Token expiring, Token expired, Reconnect needed, Paused, or Disconnected — plus a Needs attention summary card that aggregates the ones needing a reconnect.