> For the complete documentation index, see [llms.txt](https://help.blotato.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blotato.com/social-accounts-and-platform-faqs/threads.md).

# Threads

For AI-agent and API publishing, use the [Threads guide](/platform-publishing/platforms/threads.md). For account setup, see [Connect Threads](/social-accounts-and-platform-faqs/threads/connect-accounts.md).

## Why did my multi-image Threads post fail? ("Threads only supports a single image or a video")

Blotato's Threads publisher accepts 1 image or video per post. A Blotato request with multiple media items in one Threads post fails with an attachment-count error. This describes Blotato's current publishing behavior, not every feature in the native Threads app or Meta's API.

To share multiple images, publish a thread instead: attach one image to each post in the thread (post 1 contains image 1, post 2 contains image 2, and so on). Follow the steps below.

## Post a Thread with Photos

1. Open the [Remix screen](https://my.blotato.com/remix)
2. Click **+ Add Post** and select Threads
3. Write your first post and attach photos via "Add Media"
4. Click "+ Add to Thread" to add more posts to the thread
5. Attach photos to each thread post as needed
6. Schedule or publish

For an automated thread workflow, see: [Email to Long Form Thread](/integrations-and-automation-templates/templates/2-email-to-long-form-thread.md)

For API thread posting, see: [Twitter Threads](/tips-and-tricks/twitter-threads.md) (the same `additionalPosts` field works for Threads)


---

# 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://help.blotato.com/social-accounts-and-platform-faqs/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.