Why isn't my link clickable when Make.com posts to Bluesky?

What a facet looks like

A facet sits next to the text in the post record. It names a byte range inside the text and what that range is: a link, a mention or a hashtag. For the URL to be clickable, the record Make sends has to look like this:

{
  "text": "Release notes are up: https://example.com/changelog",
  "facets": [
    {
      "index": { "byteStart": 22, "byteEnd": 51 },
      "features": [
        { "$type": "app.bsky.richtext.facet#link", "uri": "https://example.com/changelog" }
      ]
    }
  ]
}

The offsets are UTF-8 bytes, not characters. That is why building facets by hand in a no-code tool is fragile: one emoji or accented letter before the URL shifts every byte count after it, and the link lands on the wrong text or fails validation.

Fix 2: one HTTP module calling OpenTweet

Replace the Bluesky module with a single HTTP module. OpenTweet finds the URLs and @mentions in your text and adds the facets before posting, so you map a title and a URL into the text and they arrive clickable. Connect Bluesky to OpenTweet once in the dashboard over atproto OAuth; no App Password goes into Make.

The JSON body, with module 1 as your trigger (an RSS item, a sheet row, a webhook):

{
  "text": "{{1.title}} {{1.url}}",
  "platforms": ["bluesky"],
  "publish_now": true
}

To send the same post to X and LinkedIn and schedule it instead of posting now, change platforms and swap publish_now for a date:

{
  "text": "{{1.title}} {{1.url}}",
  "platforms": ["bluesky", "x", "linkedin"],
  "scheduled_date": "2026-09-21T09:00:00Z"
}

The response has a results array with one entry per network. A published Bluesky entry carries the url of the post, so a later module can log it or send it to Slack. Full field list in the cross-posting docs.