Manus social media digest — May 28, 2026
Manus published a deep-dive on its Notion connector — the first blog update since the May 25 mobile Projects tweet. The post details three workflow patterns: research library automation, history-informed client proposals, and live pipeline dashboards. Ongoing threads: @ManusAI still silent post-May 25, Japan chapter Zoom set for June 17, acquisition narrative unchanged.
Manus published a deep-dive resources post on its Notion connector today — the first official blog update since the May 25 "Projects on mobile" tweet. Community social signals remain hard to surface through platform APIs, but the official blog post gives a concrete look at what the Notion integration actually does.
The Notion connector post: more than a summary
The May 28 blog entry, "The Connector That Turns Notion Into a Workflow Engine," walks through three specific scenarios where the connector goes beyond read-access — writing structured rows, building dashboards, and pushing meeting action items back into team databases. 1
The framing is positioned against the traditional "copy-paste between documentation and execution" bottleneck. Three workflow patterns are documented:
| Pattern | What Manus does |
|---|---|
| Trend research library | Runs parallel web research, creates a matching Notion database schema, populates rows, creates a Gallery view, registers a weekly recurring task |
| Client proposal from history | Semantic search over historical Notion pages, synthesizes old and new context, outputs a formatted page with headers and callout blocks |
| Pipeline dashboard | Pulls data from a Notion sales database, embeds native charts, generates a live dashboard, writes an executive summary back to a Notion page |
These are "Resources" category posts — instructional content aimed at showing practitioners how to use existing features rather than announcing new ones. The Notion connector itself has been in the product for a while; what's new is the official deep-dive documentation with example prompts.
One detail worth noting: the connector uses granular access control. Users select exactly which workspaces, pages, and databases Manus can touch; anything outside that selection stays inaccessible, and access can be revoked at any time. The blog post emphasizes this at the end of each use case, which may be a response to the data-ownership concerns raised by @TBVNetwork back on May 22.
The week's ongoing context
A few threads carry over from earlier this week:
Official account posture: @ManusAI's profile description still reads "from @Meta" as of this writing. The account posted the "Projects on mobile" thread on May 25 (the first post after a five-day gap), and there has been no further activity since.
Japan chapter event: @KOJIRYUJI1 has a public Zoom event ("Manus AI ともまえ Nights") scheduled for June 17, 19:00–21:00 JST — free, beginner-friendly, credits provided. No public sign-up count visible yet.
Acquisition narrative: No new facts since the Bloomberg/QZ reporting on May 21–22. The founders' reported ~$1B raise at $2B+ valuation and the NDRC-ordered Meta deal unwind continue to circulate without updates.
Reddit r/manus_ai: Still inaccessible (banned for spam as of at least May 27).
Credit complaints: No new voices surfaced in today's scan, though platform API availability is limited.
What this pattern looks like
Since the Projects-on-mobile tweet on May 25, Manus has resumed its cadence of publishing connector deep-dives and resources posts — the same format used for Higgsfield, SimilarWeb, and Google Drive integrations in early May. Today's Notion post fits that mold: it's documentation of an existing connector, not a product launch.
The acquisition narrative has been running for a week without new material. Either an announcement comes from the founders, or the story starts to fade as a daily signal.
Add more perspectives or context around this Drop.