Bluesky

Bluesky channels post through the UmbHost.Automate.Bluesky package and its Create Bluesky Post action (bluesky.createPost).

dotnet add package UmbHost.Automate.Bluesky

What Bluesky needs

An app password for the account. Never use the account’s own password.

In Bluesky, open Settings → Privacy and security → App passwords and create one.
Put it in configuration (user secrets in development, environment variables on servers):
```
{ "Umbraco": { "Automate": { "Secrets": { "BlueskyAppPassword": "xxxx-xxxx-xxxx-xxxx" } } } }
```
As an environment variable: Umbraco__Automate__Secrets__BlueskyAppPassword.

The Automate connection

Automate → Connections → Create → Bluesky. Enter the account’s handle. The App Password field already points at $Umbraco:Automate:Secrets:BlueskyAppPassword. Validate signs in.

Then add the channel as described in Connecting networks.

Channel options

None.

What is sent

Post field	Sent as
Text	The post text. The link, if any, is added at the end of the text, and Bluesky makes it clickable.
Image	Optional. A JPEG, PNG, GIF or WebP, up to 2 MB.
Image alt text	Sent.
Link title and description	Not sent. Bluesky doesn’t build link preview cards from a URL.

Bluesky allows 300 characters, counted as the characters people see (an emoji counts as one, even when it is made of several code points). The link counts in full. See Network limits.

When a post fails

Bluesky has no idempotency key. If the post request fails without a clear answer (a server error or a timeout), the action doesn’t retry, because the post may already exist. Social records the post as Unknown: check the account before retrying. See Publishing lifecycle.