Weekly community roundup
Sarah Chen, community manager at Acme Ltd, asked what people had posted about this week. Memtro read the newest posts and their comments. Most threads were about the new export feature, and two posts had no comments yet.
What is our community talking about, and which events are coming up?
Circle connects Memtro to your community. It reads spaces, posts with their text, comments with who wrote them, members by name, and published events with times, venue and host. When asked, and once an administrator has granted the action by name, it can publish posts and comments members see at once, send chat messages that cannot be recalled, create events and invite people, which may email them, add or tag members, deactivate a member, which cancels their paid subscriptions, and delete posts and comments. Every call counts against Circle's Admin API allowance. Emails and profile fields are never read.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Circle tool, reads what it needs, and answers with the source cited.
These tools change something in Circle. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Circle is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
What were people posting about in the community this week?
Which posts in the Announcements space got the most comments?
What did people say in the comments on the pricing update post?
What events do we have next month, and are they in person?
Create the March meetup as a draft event with this Zoom link
Sarah Chen, community manager at Acme Ltd, asked what people had posted about this week. Memtro read the newest posts and their comments. Most threads were about the new export feature, and two posts had no comments yet.
Tom Reilly, head of events at Northwind, asked Memtro to create the March meetup as a virtual event with the meeting link he gave. Memtro created it as a draft in the Events space, so only admins saw it. Once he had checked it, he published it in Circle for members to RSVP.
The teams that lean on Circle most, a question each of them asks, and what they connect beside it.
A record in Circle is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Circle admin, open Settings → Developers → Tokens.
Create a token of type "Admin V1 or V2", ideally from a dedicated admin account, as posts and messages Memtro makes appear as that admin, and copy it.
In Memtro, open Connections → Circle and paste it into Admin API token.
Ask: what were people posting about in the community this week?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Circle tools are the same everywhere.
Only when you ask, and only what it has been granted: create a post in a space (draft, published or scheduled; notifies members only when asked); edit a post's title, text, topics, pin or comment settings; delete a post; comment on a post or reply to a comment (no notifications unless asked); delete a comment and its replies (permanent); send a chat message to a member, a group of members or a chat room; create a virtual or to-be-decided event in an event space (draft or published); invite a member to an event (emails them if the event is published); invite a person to the community by email (no invitation email unless asked); add a person to a space by email; apply a member tag to a member; deactivate a member (cancels their running paywall subscriptions). Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded. An hourly sync anchors recently changed Circle records into memory as entities.
Admin API token. In Circle admin, open Settings → Developers → Tokens.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time