Skip to main content

Social Media Automation

Connect Bluesky with an app password and publish a post

Use a dedicated Bluesky app password, verify the account identity and publish supported text or a small image.

Reviewed 13 November 20262 minute read4 steps

Where to start
Social accounts → Bluesky; Configuration where applicable

Fields and options

Access needed
Manage connections; administrator for app credentials; Create posts + Publish posts for a live test
Destination and scope
The current integration uses bsky.social; it is not a general connector for an arbitrary personal data server. It creates encrypted session credentials and does not retain the supplied app password.
Publishing format
Keep the complete composed post within 300 characters. Use a supported image no larger than 2 MB; video is not supported by this adapter.

Before you begin

A dedicated Bluesky account on bsky.social and an app password created in that account’s security settings. Use an app password rather than the main account password.

Follow these steps

  1. In Social accounts, choose the Bluesky connection form. Enter the account handle and app password, then connect and verify the returned identity.
  2. In Social accounts, choose Verify connection and compare the account or destination identity with the intended test account.
  3. Keep the complete composed post within 300 characters. Use a supported image no larger than 2 MB; video is not supported by this adapter.
  4. When a controlled test is authorised and the direct gate is enabled, select only this destination, choose Post Now once and inspect its existing receipt.

Check the result

Open the Bluesky account and check the final post, image and available link/reference. Match the actual provider outcome to the destination receipt, remote reference and intended visibility.

If something does not look right

If identity or session renewal fails, verify the handle and app-password status at Bluesky, then reconnect deliberately. A different account is not silently accepted as the original destination. Do not repeat Post Now after an ambiguous result until the original provider outcome has been checked.

Fields, rules and limits

  • Saving credentials or passing connection verification does not prove that a live publication succeeded.
  • Use a dedicated test destination and the most restrictive appropriate visibility. Provider consent, app review and organisational approvals remain separate requirements.

Questions and answers

Does a connected account mean publishing is approved?

No. Connection identity, app publishing entitlement, content eligibility and the separate direct-publishing gate are independent checks.

What is a complete first test?

Official consent, correct destination discovery, successful verification, one deliberate test publication, a destination receipt and direct verification in the actual provider account.

Related technical reference: Britixo's detailed product guide (opens in a new tab). The screens available to you depend on your configured modules, company and permissions.

Contact the Proplix team if you need help with your setup. Include the page or record reference and a description of the issue; leave passwords and private access tokens out of the message.