Files
AutoGPT/docs/integrations/ayrshare/post_to_threads.md
Nicholas Tindle c1a1767034 feat(docs): Add block documentation auto-generation system (#11707)
- Add generate_block_docs.py script that introspects block code to
generate markdown
- Support manual content preservation via <!-- MANUAL: --> markers
- Add migrate_block_docs.py to preserve existing manual content from git
HEAD
- Add CI workflow (docs-block-sync.yml) to fail if docs drift from code
- Add Claude PR review workflow (docs-claude-review.yml) for doc changes
- Add manual LLM enhancement workflow (docs-enhance.yml)
- Add GitBook configuration (.gitbook.yaml, SUMMARY.md)
- Fix non-deterministic category ordering (categories is a set)
- Add comprehensive test suite (32 tests)
- Generate docs for 444 blocks with 66 preserved manual sections

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

<!-- Clearly explain the need for these changes: -->

### Changes 🏗️

<!-- Concisely describe all of the changes made in this pull request:
-->

### 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] Extensively test code generation for the docs pages



<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> Introduces an automated documentation pipeline for blocks and
integrates it into CI.
> 
> - Adds `scripts/generate_block_docs.py` (+ tests) to introspect blocks
and generate `docs/integrations/**`, preserving `<!-- MANUAL: -->`
sections
> - New CI workflows: **docs-block-sync** (fails if docs drift),
**docs-claude-review** (AI review for block/docs PRs), and
**docs-enhance** (optional LLM improvements)
> - Updates existing Claude workflows to use `CLAUDE_CODE_OAUTH_TOKEN`
instead of `ANTHROPIC_API_KEY`
> - Improves numerous block descriptions/typos and links across backend
blocks to standardize docs output
> - Commits initial generated docs including
`docs/integrations/README.md` and many provider/category pages
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
631e53e0f6. 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>
2026-01-19 07:03:19 +00:00

2.3 KiB

Ayrshare Post To Threads

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

Post To Threads

What it is

Post to Threads using Ayrshare

How it works

This block uses Ayrshare's API to publish content to Threads (Meta's text-based social platform). It supports text posts (up to 500 characters with one hashtag), images, videos, and carousels (up to 20 items), with automatic link previews when no media is attached.

The block authenticates through Meta's API via Ayrshare. Content can mention users via @handle syntax, be scheduled for future publishing, and include approval workflows for content review.

Inputs

Input Description Type Required
post The post text (max 500 chars, empty string allowed). Only 1 hashtag allowed. Use @handle to mention users. str No
media_urls Optional list of media URLs. Supports up to 20 images/videos in a carousel. Auto-preview links unless media is included. 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

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

Thought Leadership: Share quick insights, opinions, or industry commentary in a conversational format.

Cross-Platform Text Content: Automatically syndicate text-based content from other platforms to Threads.

Community Engagement: Post discussion prompts or responses to engage with your Threads audience.