# Can Manus plan your X posts around a conference you are speaking at? > Source: https://tareno.co/agents/manus/x > Language: en > Last reviewed: 2026-10-24 > Use Manus with Tareno to read a conference's public agenda, plan before, during and after posts for your talk on X within 280 characters, and approve each draft 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: X · Hub: [Manus and Tareno](https://tareno.co/agents/manus) ## Short answer **Can Manus research a conference and prepare my X posts for the days around my talk?** Yes, over the tested custom MCP connection. Manus reads the public agenda, speaker list and your slot, drafts posts for before, during and after the event within 280 characters and saves them through Tareno. Every request waits for your approval in Tareno. A conference appearance is a few days of attention. Posts before the event bring people to your session, posts during it get lost in the noise unless they are specific, and posts after it decide whether the talk lives on. Preparing all three means reading the organizer's pages, which change, and tagging the right handles, which are easy to get wrong. Manus is made for this kind of research-first task, and Tareno turns the plan into drafts. This page follows a developer relations lead preparing for a talk, with the boundaries around handles and times, and with a plain statement of how Manus connects today. ## Example: a developer advocate prepares for a 25-minute conference talk Imagine a developer advocate with a Thursday 11:30 talk. She gives Manus the conference's agenda page, the speaker list and her abstract. Manus reads them, notes that the agenda lists the room as Hall B while an older page says Hall C, and asks which is current. It plans nine posts: three before the event, three for the day and three for the week after, each within 280 characters. It marks every post that tags someone and shows the handle it found. She corrects one handle, Manus saves the nine drafts through `create_drafts` for her X account, and she requests the first three slots in the dashboard. ## Step by step 1. **Connect Tareno as a custom connector.** Add the Tareno endpoint as a custom MCP connection with OAuth. 2. **Give the organizer's pages.** Provide the agenda, the speaker list and your abstract. Ask Manus to record the date it read each page, because conference pages change in the weeks before the event. 3. **Resolve conflicting details.** Where two pages disagree, such as a room or a start time, Manus asks. Fix the detail before any post uses it; a wrong room in a post sends people to the wrong hall. 4. **Plan the three phases.** Ask for posts before, during and after, each with a purpose: invite, point to a specific slide or moment, share the materials. A schedule of nine posts is only useful if each does a different job. 5. **Mark every tag.** Have Manus show each handle next to the name it belongs to and the page where it found it. Tagging the wrong account is a common and visible mistake. 6. **Save, request and approve.** Manus confirms the account with `list_accounts` and saves the drafts through `create_drafts`. Give times and an IANA time zone for each phase; you approve the requests in the Tareno dashboard. ## Prompts to copy ### Read the organizer's pages ```text Read the conference agenda [URL] as groundwork for Tareno drafts,, the speaker list [URL] and my abstract below. Record the date you read each page, list my session's time, room and format, and tell me every place where two pages disagree. Do not write posts yet. ``` ### Plan nine posts ```text Plan nine X posts for Tareno drafts around my talk: three before the event, three on the day and three in the week after. For each give the purpose, the draft text within 280 characters and any account it tags. Use only confirmed details from the organizer's pages. ``` ### Show every handle ```text List every account that appears in the plan next to the person it belongs to and the page where you found the handle. Remove any tag you could not source, and mark anything that depends on the organizer's hashtag so I can confirm it. ``` ### Save in order ```text Use Tareno to confirm my X account [handle] and save the nine approved posts as drafts, numbered in the order they should appear. Return a table with draft ID and phase, and request no time before I confirm the room and the start time. ``` ## X in Tareno - Tareno's configuration for X allows 280 characters with mentions and hashtags, so tagging a co-speaker and adding the conference hashtag usually leaves enough room for one clear sentence. - X's API documentation allows one video or up to four photos per post, so a clip of the rehearsal or a slide image can go with a post on the day. - Tareno does not read posts or replies on X, so Manus cannot see how the event hashtag is trending; it works from the pages you provide. - Quote-posting through the X API needs an Enterprise plan, so reposting another speaker's post with a comment has to be done by hand. Official rules ([X API documentation: create a post](https://docs.x.com/x-api/posts/creation-of-a-post), checked 2026-10-24): - A post may include up to 4 photos, 1 animated GIF or 1 video. - The allowed video length depends on the posting account, not on the API plan: 20 minutes and 8 GB by default, 125 minutes and 16 GB with X Premium or verified status. Tareno's configuration for X stops at 140 seconds. - Quote-posting through the API requires an Enterprise plan and is not available on self-serve tiers. ## Mistakes to avoid - Using an outdated agenda. Re-read the organizer's page the week before and again on the day. - Tagging from memory. A wrong handle tags a stranger, so source each one. - Writing nine posts that all announce the talk. Give each post a different job, or followers mute you. - Assuming a public listing exists. Manus connects to Tareno through a custom connection today. ## What does not work - Manus cannot confirm a room or a time that the organizer has not published, so you check the organizer's page before approval. - It cannot read the conference hashtag or replies on X through Tareno, because Tareno does not expose X posts or replies. - It cannot publish a post 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 find the right handles? It reads the speaker and organizer pages and shows each handle with the person and the source page. Handles it cannot source should be removed, and you confirm the rest before any draft is requested for a time. ### Can Manus watch the event hashtag during the talk? No. Tareno does not read posts or replies on X, so Manus cannot see the hashtag live. It prepares the posts beforehand, and you handle live conversation on X yourself. ### What if the schedule changes the day before? Give Manus the new details and ask it to list every draft that mentions the old ones. Update those drafts in Tareno, and cancel any pending request that still carries the outdated time. ### Does it 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 nine posts go out automatically? No. Each request is a pending action in Tareno, and X receives a post only after you approve it in the dashboard. `get_action_status` shows what happened to each one afterwards. ## 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) - [X with Tareno](https://tareno.co/channels/twitter) - [Post scheduling](https://tareno.co/features/post-scheduling) - [Approval workflows](https://tareno.co/features/approval-workflows) - [Remote MCP setup](https://tareno.co/docs/mcp)