"Auto post to TikTok and LinkedIn" is one of the most common shapes this search takes, and it deserves a direct answer instead of marketing hand-waving: native, one-click auto-posting is Instagram only. Everything else is possible, but it's a different kind of setup, and it's worth knowing the difference before you build around an assumption.
What's native
The Post node connects to an Instagram account (up to two) and publishes directly — caption, timing, and the image or reel itself, no extra credentials beyond the initial account connection. This is the fully automated, no-manual-step path, and it's the one covered in the exact Instagram node chain.
What reaching other platforms actually requires
TikTok, LinkedIn, and X don't have a dedicated Post node. Reaching them from a workflow means an HTTP Request node configured against that platform's own publishing API, using a developer app and credentials you register yourself — the same general pattern tools like n8n use for any third-party integration that doesn't have a pre-built connector. That means: creating a developer account on the target platform, working through its specific authentication flow, and matching its API's exact expected request format for a post. It's genuinely doable, but it's not the same one-click experience as the Instagram Post node, and it's worth budgeting real setup time for, not assuming it's a checkbox.
Why this gap exists instead of being papered over
A workflow tool that quietly treated "HTTP Request to a third-party API" as equivalent to a native, tested integration would be setting people up to hit an undocumented API change or a broken auth token with no warning. Being upfront that Instagram is the tested, native path — and everything else is you-own-the-integration — is the more honest version, even if it's a less flattering answer to "does this auto-post everywhere."
If your real need is importing, not posting
If what you actually want is TikTok content flowing into your workflow rather than out to it, that's a different and much simpler path: the repost-from-link flow pulls clean media from a TikTok, Instagram, or X link into your Content Sheet for captioning and scheduling — see reposting a TikTok link without the watermark. Import breadth and publish breadth are two separate things, and it's easy to conflate them if you only skim the feature list.
The honest recommendation
If Instagram is your primary channel, the native path is genuinely simple and worth building around first. If TikTok or LinkedIn auto-posting is a hard requirement from day one, plan for the HTTP Request setup as its own project — register the developer credentials, test the endpoint manually before wiring it into a Trigger, and treat it with the same caution as any first automation: manual runs until you trust it, not a timer from the start.