Help
Help
Loading help article
When you post a message on InterlinedList you can optionally send a copy to one or more external social platforms at the same time. This is called cross-posting (or syndication). The post originates on InterlinedList; the platforms receive a copy. This page covers the feed labels, supported platforms, setup, LinkedIn destinations, X details, failures, and keeping connections active.
Cross-posting is a Subscriber feature. You also need a connected account for each platform you post to.
When you browse the Home feed you may notice small platform labels on some posts: Mastodon, Bluesky, or LinkedIn. These labels indicate that the author chose to syndicate that message to that platform when they posted it. The post lives on InterlinedList first; the label is a record of where else it was sent.
You do not need accounts on those platforms to read labeled posts on InterlinedList. The label is informational only.
| Platform | Notes |
|---|---|
| Mastodon | Decentralized; you can connect one or more Mastodon accounts from different instances. When cross-posting you choose which connected instance(s) to send to. |
| Bluesky | One linked account; the post is sent automatically when you enable it for a message. |
| Post to your personal profile, an assigned organization page, or a personal company page, selectable per post. Availability depends on whether this instance has LinkedIn OAuth configured. | |
| X (Twitter) | One linked account; long messages are automatically split into a thread with reply-chained tweets. |
mastodon.social), then redirected to authorize.To unlink a platform, find it in Connected Accounts and click Disconnect.
You choose cross-posting targets per message, so you can syndicate some posts and not others.
LinkedIn can post to more than one destination. You can post as your personal LinkedIn profile, to a company page you administer through your own LinkedIn account, to a page connected through an organization you belong to, or any combination. When you have more than one enabled LinkedIn destination, a LinkedIn destinations checkbox list appears in the advanced options; tick every destination that should receive the post. Each destination is labelled so you can tell them apart:
If one LinkedIn destination fails, the others still receive the post. You control which destinations appear from the Posting targets section of the LinkedIn card on the Integrations page.
Post link(s) as first comment. If your message contains a URL, an extra option becomes available: Post link(s) as first comment (LinkedIn). Checking it places the URL in the first comment rather than the body, which can improve how LinkedIn presents the content.
Formatting on LinkedIn. Long messages post to LinkedIn in full, so a longer cross-post won't be cut short. LinkedIn does not support the same text styling as InterlinedList, so a few characters show up as plain text there: #, *, _, ~, and parentheses appear exactly as typed. This means hashtags in a LinkedIn cross-post are shown as ordinary text rather than being turned into clickable links. This is expected: your post still publishes in full; only LinkedIn's display of those characters differs.
Permissions requested. When you connect X, InterlinedList requests read access (to verify the account and avoid duplicate posts), write access (to post and to create a thread when a message is long), profile access (to show your username and avatar), and offline access (so scheduled posts can publish later without the connection expiring). InterlinedList does not read your direct messages or follow or unfollow anyone on your behalf.
Long posts become threads. A message longer than 280 characters is automatically split into a numbered thread on X so none of your content is cut off.
"Coming soon" instead of Connect. If the X card shows a "Coming soon" label instead of a Connect button, the X integration has not been enabled for your InterlinedList instance. Contact your site administrator.
Disconnecting. On the Integrations page, find the X card and click Disconnect. All stored authorization tokens are removed; tweets you already posted are not deleted. Reconnecting later restores the toggle in the compose toolbar automatically.
Troubleshooting. If posts aren't appearing on X:
X enforces its own rate limits, so many posts in a short period may be delayed or rejected; wait a few minutes and try again. If the card shows "Not connected" shortly after you connected it, your authorization may have expired or been revoked (for example, after a password change); reconnect to restore the link.
The post appears as a native post from your account on that platform. It is not a link card: it is a full post with your message content. The length and formatting are subject to each platform's limits; very long messages may be truncated or rejected depending on the platform's rules.
If your message includes a URL, it appears in the cross-posted content. Attached images (and video, on platforms that support it) are forwarded to the target platform as native media, subject to each platform's per-post media limits.
When you reply to a message that was originally cross-posted and you follow the original author on the same external platform, your reply may be sent to that platform automatically. This behaviour is platform-dependent and is not guaranteed. If automatic cross-posting of a reply fails, a brief error toast appears for five seconds; your reply still appears on InterlinedList.
A failed syndication does not prevent the message from being published on InterlinedList. If one platform fails, the others still receive the post. In the web app, failures surface as a short error toast. (If you are building on the API, the response from POST /api/messages includes a crossPostResults array that reports success or failure per platform.)
Common causes of failure:
Each platform you connect for cross-posting stays linked through a secure authorization. Some of these connections last indefinitely; others expire after a while and need to be refreshed by reconnecting. This is normal and expected: it's how the platforms protect your account.
How long a connection lasts depends on the platform. LinkedIn connections, for example, generally expire after a couple of months and can't be refreshed automatically, so you'll need to reconnect from time to time. Other platforms may need refreshing more or less often. You don't have to track any of this yourself.
InterlinedList watches your connections for you. When a connection is about to expire or has stopped working, InterlinedList tells you ahead of time so a cross-post doesn't quietly fail. You'll see:
How to fix it. When you see one of these reminders:
Reconnecting doesn't change any of your settings or remove past posts; it simply renews the connection.
A note about LinkedIn. Because LinkedIn can't renew its connection automatically, you'll be asked to reconnect LinkedIn periodically (roughly every couple of months). This is expected behaviour, not a bug: just reconnect when you see the reminder and you're good to go.
Turning the reminders on or off. These reconnect reminders are controlled by the Integration reconnect reminders setting in your notification preferences (Settings). They're on by default; leaving them on is the easiest way to make sure your cross-posts keep going through.
Open the Integrations page from Settings at any time to:
Disconnecting an account does not delete posts already cross-posted to that platform.