Can Lyro publish or schedule a Beamer announcement?

No. Every action in the connected toolkit reads - posts, categories, comments, reactions, notifications, and their counts. Writing or scheduling an announcement stays in Beamer, and Lyro's role is answering questions about what has already been published there.

How does Lyro decide what kind of update a post is?

Beamer uses a fixed set of categories - new, improvement, fix, comingsoon, announcement, and other - and Get Category returns the metadata for one by its ID. Lyro groups and filters posts on those values rather than inferring a type from the title.

Does Lyro see unread counts for the individual customer it is talking to?

Yes, where the conversation supplies the user context. Count Unread Posts and Get Notifications are user-scoped and return what that person would see on opening their feed. Worth knowing: Get Notifications marks the notifications it returns as read, so it is not a passive check.

How is this better than linking customers to the changelog?

A link makes the customer go and find the entry themselves. Lyro reads the posts, matches the one that covers what was asked, and answers in the conversation, falling back on the standalone feed URL from Get Feed when someone wants the full history instead.

Beamer MCP integration

Reads published posts and their categories, pulls the comments and reactions on them, and checks what a given user has not read yet.

Connect Beamer See all integrations

12actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Get notifications
Lyro fetches unread notifications for the user. Support agents see all pending updates without scrolling through archives.
Get posts
Lyro retrieves the list of posts from Beamer. Agents quickly reference company announcements and product updates during customer conversations.
Count unread posts
Lyro counts how many unread posts exist for the user. Agents know at a glance if there are new company updates to mention.

See all 12 actions

How businesses use Beamer + Lyro

Each card is one request a support team gets, and the Beamer actions Lyro runs to close it.

Answer what-changed-recently from the changelog
Lyro lists the published posts with their IDs and titles and resolves each one's category - new, improvement, fix, comingsoon, announcement, or other - so an update question is answered from what actually shipped.
Get PostsGet CategoryCount Posts
Report how an announcement landed
Lyro counts the reactions and comments on a post and pulls the comments themselves, so a question about whether a release resonated is answered with the responses rather than an impression.
Count Post ReactionsGet Post CommentsGet Post Reactions
Check what a specific user has not seen
Lyro counts the posts still unread in that user's Beamer feed and retrieves their outstanding notifications, so a customer can be pointed at the exact update that answers their question.
Count Unread PostsGet NotificationsGet Notification
Hand over the full update feed
When the answer runs longer than a chat reply, Lyro fetches the standalone feed URL to share, and confirms the API key is still authenticating before relying on any of it.
Get FeedPing API

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Beamer actions it has and picks the ones a request needs.

01
Connect Beamer
Authorize the Beamer account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Beamer actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Beamer · Lyro

Everything else about Beamer

Setup, permissions, and the limits of what Lyro can do inside Beamer.

No. Every action in the connected toolkit reads - posts, categories, comments, reactions, notifications, and their counts. Writing or scheduling an announcement stays in Beamer, and Lyro's role is answering questions about what has already been published there.

Every action available in Beamer

All 12 actions your agent can call on Beamer, straight from the live MCP connection.

Count post comments
Count existing comments on a specific post.
Count post reactions
Count existing reactions on a specific post.
Count posts
Count existing posts.
Count unread posts
Count unread posts for a user.
Get category
Retrieve metadata for a Beamer category by its ID.
Get feed
Retrieve the URL for your standalone feed.
Get notification
Retrieve details of a specific notification by its unique notification ID.
Get notifications
Fetch unread notifications.
Get post comments
Retrieve comments for a specific post.
Get post reactions
Retrieve all reactions associated with a specific post.
Get posts
Retrieve a list of posts.
Ping API
Ping the Beamer API.