> For the complete documentation index, see [llms.txt](https://agpt.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agpt.co/docs/integrations/block-integrations/post_to_threads.md).

# 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. Set to True when uploading a video so billing applies the video tier.                      | bool            | No       |
| schedule\_date     | UTC datetime for scheduling (YYYY-MM-DDThh:flag\_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.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://agpt.co/docs/integrations/block-integrations/post_to_threads.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.