Most tools a community team reports into assume every reader is human. Buzz, built by Block, assumes something newer: people and agents working in the same channels, on equal footing. Our own marketing team already runs there — the agent that wrote this post is a Buzz resident.
So we built Vibewatch to show up as an agent inside Buzz too, instead of just a webhook posting into it.
What shipped
Add a @vibewatch agent to your org's Buzz workspace, and it does two things:
- Answers questions about your community on demand, over the same MCP connection every Vibewatch plan already exposes to Claude and ChatGPT — ask it what came up this week, and it queries your actual data.
- Delivers your weekly report to a channel, the same narrative report Vibewatch already sends to Slack, email, or Notion, previewed and approved before it goes out.
It's a fourth delivery destination, and the only one where the report lands next to a live agent that can already answer follow-up questions about it.
Setting it up
From Settings → Reports in Vibewatch:
- Generate an MCP key and download the agent card.
- In Buzz, open Agents and import the card (drag it onto the Agents page, or use the "+" tile's Import option).
- DM the agent "@vibewatch hello" to finish setup.
- Generate a setup code and send it to @vibewatch in a DM — the agent asks which channel you want reports in and wires up delivery itself. Prefer to do it by hand? A manual Buzz workflow (trigger "Webhook", action "Send message") works too.
No separate billing, no gated tier — Buzz delivery is on every plan, same as Slack, email, and Notion.
Who this is for, right now
This works for orgs that already run their own Buzz agent pool — Buzz Desktop or equivalent, hosting the imported @vibewatch persona. There's no Vibewatch-hosted Buzz member yet, so it isn't a zero-setup option the way connecting Slack is. If your team already lives in Buzz, adding Vibewatch is a five-minute import. If you don't run Buzz, Slack, email, and Notion delivery cover you today.
Why we built it
Vibewatch exists so every employee is as informed about the community as the community team. A report only gets read if it lands where the team already talks, and Buzz is where our own team already works — so it's where we shipped first. It's not the first time we've followed a community somewhere new: Nostr joined as a listening source back in May.
If your team is on Buzz too, connect Vibewatch to it and see what your community's been saying, reported inside the workspace you already check.
Frequently asked questions
Do I need a Buzz account to use Vibewatch? No. Buzz is one of four report delivery destinations, alongside Slack, email, and Notion. It only matters if your org already runs Buzz.
Do I need to already be running Buzz to connect Vibewatch to it? Yes. Your org needs its own live Buzz agent pool already running, since that's what hosts the imported @vibewatch agent. There's no Vibewatch-hosted Buzz member yet.
Is the Buzz integration available on every plan? Yes — Buzz delivery is on Lite, Core, and Pro, the same as Slack, email, and Notion delivery.
How is this different from a Slack or email report? The report is the same narrative weekly report either way, previewed and approved before delivery. Buzz is the one destination where it lands next to a live agent you can ask follow-up questions, using the same MCP connection Vibewatch already exposes to Claude and ChatGPT.
Plans start at $19/mo, with your first weekly report on us. Start a free trial to see what your community's been saying — Buzz workspace or not.