n8n workflow: post to X, Bluesky and LinkedIn at once

Set it up in four steps

1. 1

   Connect your accounts and create an API key

   In OpenTweet, connect X, Bluesky and LinkedIn. LinkedIn posts go to your personal profile. Then create an API key; it starts with ot_.

2. 2

   Import the workflow

   Copy the JSON below and paste it onto the n8n canvas. You get an RSS Feed Trigger wired to an HTTP Request node.

3. 3

   Set the feed and the key

   Put your feed URL in the RSS Feed Trigger. In the HTTP Request node, replace ot_your_api_key in the Authorization header, or move it into a Header Auth credential so it is not stored in the workflow.

4. 4

   Test, then activate

   Run the workflow once and read the results array in the HTTP Request output. When it looks right, activate the workflow and it polls the feed every hour.

Reading the per-network results

With publish_now, the response comes back after the post has been sent, and posts[0].results has one entry per network with a status of published, failed or skipped:

{
  "success": true,
  "count": 1,
  "posts": [
    {
      "id": "65f1a2b3c4d5e6f7a8b9c0d1",
      "status": "posted",
      "platforms": ["x", "bluesky", "linkedin"],
      "posted": true,
      "results": [
        {
          "platform": "x",
          "status": "published",
          "url": "https://x.com/you/status/1834000000000000000"
        },
        {
          "platform": "bluesky",
          "status": "skipped",
          "skip_reason": "This post is 312 characters, over the 300 Bluesky allows."
        },
        {
          "platform": "linkedin",
          "status": "published",
          "url": "https://www.linkedin.com/feed/update/urn:li:share:7300000000000000000/"
        }
      ]
    }
  ]
}

The HTTP Request node treats a non-2xx response as an error and stops the execution, so the 502, 409 and 402 cases show up as failed executions. A skip is a 201, so it does not. To catch skips, add an IF node after the HTTP Request node that checks whether this expression is not empty, and send its true branch to Slack or email:

{{ $json.posts[0].results
  .filter(r => r.status !== 'published')
  .map(r => r.platform + ': ' + (r.skip_reason || r.error))
  .join(', ') }}

Scheduling instead of posting now

Send an ISO 8601 scheduled_date in place of publish_now. The create response then confirms the post without results, because nothing has been sent yet. Read them after the scheduled time with GET /api/v1/posts/{id}, which returns the same results array.

{{ JSON.stringify({
  text: $json.title + ' ' + $json.link,
  platforms: ['x', 'bluesky', 'linkedin'],
  scheduled_date: '2026-10-01T15:00:00Z'
}) }}

No feed? Use a Schedule Trigger and Google Sheets

Replace the RSS Feed Trigger with a Schedule Trigger followed by a Google Sheets node that reads the next row. Point the body expression at the column that holds the text, for example $json.text, and keep the rest of the HTTP Request node as it is.

Frequently asked questions