# Can Manus compile a weekly industry digest and prepare it as Threads posts? > Source: https://tareno.co/agents/manus/threads > Language: en > Last reviewed: 2026-10-24 > Use Manus with Tareno to collect the week's public news and regulator updates for a trade association, write short sourced Threads posts and save drafts you approve in Tareno. ## Connection facts | Field | Value | | --- | --- | | Product surface | Manus (manus) | | Available connection | Custom MCP connection | | Connection evidence | tested | | Methods | mcp | | Authentication | oauth | | Setup | [Setup guide](https://tareno.co/docs/mcp) | | Install or connect | [Open setup](https://tareno.co/docs/mcp) | | Evidence observed | 2026-10-22 | | Facts reviewed | 2026-10-25 | Publication status and a working connection are separate facts. Evidence for one product surface does not establish installation or compatibility in another surface. Agent: Manus · Network: Threads · Hub: [Manus and Tareno](https://tareno.co/agents/manus) ## Short answer **Can Manus gather a weekly industry digest and prepare it as Threads posts?** Yes, over the tested custom MCP connection. Manus reads the public sources you list, picks the week's relevant items, writes a short post for each that names its source and saves drafts for your Threads profile through Tareno. Everything needs your approval in Tareno. Trade associations and professional bodies earn their members' attention by telling them what changed this week, and that means reading the regulator's pages, the trade press and a few mailing lists every Friday. It is real work, the sort that is skipped when things get busy. Manus is built for research that takes many pages, and Threads is a place where a short, sourced item gets read and discussed. This page follows an association for independent pharmacies through a weekly digest, with the sourcing rule that makes it trustworthy, the cap on how many items are worth posting, and the manual connector that Manus needs today. ## Example: a pharmacists' association posts its Friday digest Imagine an association that gives Manus a list of twelve public sources: the regulator's news page, two trade magazines and a ministry bulletin. On Friday morning Manus reads them, finds nineteen items from the week, and selects the five that affect pharmacies, such as a change in prescription forms. For each it writes a post within 500 characters that states what changed, from when, and names the source. It saves the five drafts with `create_drafts` for the association's Threads profile. The communications officer checks each against its source, drops one item that only repeats another, and requests the first slot. ## Step by step 1. **Connect Tareno as a custom connector.** Add the Tareno endpoint as a custom MCP connection with OAuth. 2. **Give the source list.** List the public pages Manus should read each week. A fixed list makes the digest comparable from week to week and keeps it from drifting toward whatever is loudest. 3. **Ask for relevance and dates.** Request the week's items with their dates and a one-line reason each matters to your members. Items outside the week are dropped. 4. **Cap the number of items.** Ask for five at most. A digest of fifteen posts trains members to ignore it, and Threads is a place for short items. 5. **Write sourced posts.** Request a post per item within 500 characters that states what changed, from when, and names the source. Claims go no further than the source. 6. **Save, request and approve.** Manus confirms the profile with `list_accounts` and saves the drafts through `create_drafts`. Give times and an IANA time zone, and approve each request in the Tareno dashboard after checking its source. ## Prompts to copy ### Collect the week ```text For a Tareno post series, read these sources for items published between [Monday] and [Friday]: [list of URLs]. For each item give the date, the source and a one-line reason it matters to independent pharmacies. Tell me how many sources you could read and which you could not reach. ``` ### Select five ```text Select the five items that most affect day-to-day pharmacy work and tell me why you left out the rest. If two items cover the same change, keep the one from the primary source and mention the other only as a note to me. ``` ### Write the posts ```text Write a Threads post of at most 500 characters for each selected item. State what changed and from when, name the source in the text and avoid advice on what members should do. Mark any item where the source is unclear about the date. ``` ### Save in order ```text Use Tareno to confirm the Threads profile [association handle] and save the five approved posts as drafts, numbered in the order they should appear. Return a table with draft ID and source, and request no times until the communications officer has checked each source. ``` ## Threads in Tareno - Threads limits text posts to 500 characters according to Meta's documentation, which suits one change per post and forces the source name to be short. - Links get an automatic preview on Threads in Tareno's configuration, so the source page itself can be linked and shown with its headline. - Threads is a network where Tareno reads replies, so members' questions on a digest item can be read the next week and answered in the following digest. - Meta's documentation limits a profile to 250 API-published posts within 24 hours, far above a weekly digest but worth knowing for an automated job. Official rules ([Meta: Threads API, posts](https://developers.facebook.com/docs/threads/posts), checked 2026-10-24): - A profile is limited to 250 API-published posts within 24 hours; a carousel counts as one post. - Text posts are limited to 500 characters, and emojis count by their UTF-8 bytes, not as single characters. - Carousels need 2 to 20 items. Single images may be JPEG or PNG up to 8 MB, and videos MOV or MP4 up to 5 minutes and 1 GB. ## Mistakes to avoid - Posting an item without its source. A digest is trusted because it names where each change comes from. - Giving advice. Say what changed, and leave interpretation to the member's own adviser or to a separate piece. - Posting all nineteen items. Select, or the digest becomes noise. - Assuming a public listing exists. Manus connects to Tareno through a custom connection today. ## What does not work - Manus cannot read pages that sit behind a login, so members-only sources are outside its weekly reading. - It cannot decide what counts as advice in a regulated field, so a person reads each post before approval. - It cannot publish the digest on its own, since a time request becomes a post only after you approve it in the Tareno dashboard. ## Frequently asked questions ### Is Tareno available in the Manus directory? Use the tested custom MCP connection in Manus with OAuth and your own Tareno account. Availability depends on your Manus plan and workspace permissions. After connecting your own Tareno account, run list_accounts and check the returned profiles before creating a draft or requesting a publishing time. ### How does Manus pick the five items? By the reason each matters to your members, using the sources and dates it read. It tells you what it left out, so you can disagree and swap an item before any draft is saved. ### Can the digest give advice to members? It should not. The posts state what changed, from when and from which source. Interpretation in a regulated field belongs to a qualified person, and Manus is told to avoid it. ### What if a source is unreachable? Manus reports which sources it could not read, and the digest says nothing about them. A missing source is better stated than silently skipped, so the officer can check it by hand. ### Does Manus need an API key? No. The custom connection uses OAuth with your Tareno account, and Manus stores the authorization. Do not paste a key or token into a task, because it would remain in the conversation. ### Will the posts go out on Friday by themselves? No. Each scheduling request is a pending action in Tareno, and Threads receives a post only after you approve it in the dashboard. `get_action_status` shows what happened afterwards. After connecting your own Tareno account, run list_accounts and check the returned profiles before creating a draft or requesting a publishing time. ## Tareno tools used - `list_accounts` - `create_drafts` - `get_action_status` Approval model: Tareno saves drafts directly. Scheduling, publishing, edits to scheduled posts and deletions become pending actions that a person approves in the Tareno dashboard; no agent can approve them. ## Related - [Manus × Tareno overview](https://tareno.co/agents/manus) - [Threads with Tareno](https://tareno.co/channels/threads) - [Post scheduling](https://tareno.co/features/post-scheduling) - [Approval workflows](https://tareno.co/features/approval-workflows) - [Remote MCP setup](https://tareno.co/docs/mcp)