Files
AutoGPT/docs/integrations/block-integrations/ayrshare/post_to_bluesky.md
Nicholas Tindle 90466908a8 refactor(docs): restructure platform docs for GitBook and remove MkDo… (#11825)
<!-- Clearly explain the need for these changes: -->
we met some reality when merging into the docs site but this fixes it
### Changes 🏗️
updates paths, adds some guides
<!-- Concisely describe all of the changes made in this pull request:
-->
update to match reality
### Checklist 📋

#### For code changes:
- [x] I have clearly listed my changes in the PR description
- [x] I have made a test plan
- [x] I have tested my changes according to the test plan:
  <!-- Put your test plan here: -->
  - [x] deploy it and validate

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> Aligns block integrations documentation with GitBook.
> 
> - Changes generator default output to
`docs/integrations/block-integrations` and writes overview `README.md`
and `SUMMARY.md` at `docs/integrations/`
> - Adds GitBook frontmatter and hint syntax to overview; prefixes block
links with `block-integrations/`
> - Introduces `generate_summary_md` to build GitBook navigation
(including optional `guides/`)
> - Preserves per-block manual sections and adds optional `extras` +
file-level `additional_content`
> - Updates sync checker to validate parent `README.md` and `SUMMARY.md`
> - Rewrites `docs/integrations/README.md` with GitBook frontmatter and
updated links; adds `docs/integrations/SUMMARY.md`
> - Adds new guides: `guides/llm-providers.md`,
`guides/voice-providers.md`
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
fdb7ff8111. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: claude[bot] <41898282+claude[bot]@users.noreply.github.com>
Co-authored-by: bobby.gaffin <bobby.gaffin@agpt.co>
2026-01-23 06:18:16 +00:00

2.4 KiB

Ayrshare Post To Bluesky

Blocks for posting content to Bluesky using the Ayrshare social media management API.

Post To Bluesky

What it is

Post to Bluesky using Ayrshare

How it works

This block uses Ayrshare's social media API to publish content to Bluesky. It handles text posts (up to 300 characters), images (up to 4), and video content with support for scheduling, accessibility features like alt text, and link shortening.

The block authenticates through your Ayrshare credentials and sends the post data to Ayrshare's unified API, which then publishes to Bluesky. It returns post identifiers and status information upon completion, or error details if the operation fails.

Inputs

Input Description Type Required
post The post text to be published (max 300 characters for Bluesky) str No
media_urls Optional list of media URLs to include. Bluesky supports up to 4 images or 1 video. List[str] No
is_video Whether the media is a video bool No
schedule_date UTC datetime for scheduling (YYYY-MM-DDThh:mm:ssZ) str (date-time) No
disable_comments Whether to disable comments bool No
shorten_links Whether to shorten links bool No
unsplash Unsplash image configuration str No
requires_approval Whether to enable approval workflow bool No
random_post Whether to generate random post text bool No
random_media_url Whether to generate random media bool No
notes Additional notes for the post str No
alt_text Alt text for each media item (accessibility) List[str] No

Outputs

Output Description Type
error Error message if the operation failed str
post_result The result of the post PostResponse
post The result of the post PostIds

Possible use case

Cross-Platform Publishing: Automatically share content across Bluesky and other social networks from a single workflow.

Scheduled Content Calendar: Queue up posts with specific publishing times to maintain consistent presence on Bluesky.

Visual Content Sharing: Share image galleries with accessibility-friendly alt text for photo-focused content strategies.