Beamer
CMS & ContentPublish product changelog posts, run an ideas board, and collect NPS with Beamer, covering posts, comments, reactions, and segments. Agents turn shipped work into announcements and route feedback to the right team.
What This Integration Enables
Beamer is for teams who have stopped treating the changelog as a broadcast. Its posts carry a segment filter, its end users carry segment values, and its feed carries comments, reactions and votes back the other way, which turns a release note into a two-way surface instead of a wall. FlowRunner agents work that surface in both directions: create a post for a named cohort, read what that cohort said about it, and move a feature request's status when the thing they voted for actually ships.
The NPS side is where Beamer earns its place in an operations flow rather than a marketing one. An agent can check whether a specific user is due for a survey before showing one, send a survey at a moment that means something like the end of onboarding, and pick up the response through a trigger the same day it arrives. That is the seam where automation exceptions get made: most responses are numbers to aggregate, a handful are a customer telling you something specific, and only a person can tell the difference reliably enough to act on it.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Beta announcement to a named cohort
A capability goes live behind a flag for a beta cohort. The agent drafts a Beamer post with the segment filter set to the cohort's value and the category set to comingsoon, then resolves the filter before publishing: List Users returns each end user with their segment values, so the agent counts how many people the post would actually reach. That count goes to the release channel with the draft. If the number is the whole user base, the filter is wrong and everyone is about to be told about something they cannot have. If the number is zero, the value is misspelled and nobody will see it. Either way a person sees the number before the post exists.
Feature requests routed from the field to the roadmap
A Zendesk ticket or a HubSpot call note contains a request. The agent searches List Feature Requests for an equivalent entry, then either records a vote with Create Feature Request Vote attributed to that customer or files a new request with Create Feature Request. When engineering closes the corresponding issue in Linear, the agent moves the Beamer request's status with Update Feature Request and reads List Feature Request Votes to hand the customer success team the exact list of accounts to contact. The people who asked get told by a human, not by a status change they have to notice.
Detractor response the day it arrives
On New NPS Response fires with a score in the detractor band. The agent reads the written feedback, looks the user up with List Users to pull their segment values and last-seen date, and checks whether the complaint maps to a release that shipped in the last two weeks. It posts the score, the verbatim feedback and the account context into the owner's Slack channel. If the feedback names a missing capability, the agent proposes an ideas board entry and waits for the owner to confirm before filing it, because a frustrated customer's sentence is not automatically a roadmap item.
Human-in-Loop Highlight
Beamer's Segment Filter is a free-text expression, semicolon separated, and Beamer publishes no fixed vocabulary of segment values. That is a feature for flexibility and a hazard for automation, because a value that matches nothing does not raise an error. It just changes who sees the post, silently, in one of two directions. A typo narrows the audience to nobody. An omitted filter widens it to everybody, which means an unreleased capability gets announced to customers who cannot get it and who now have a reason to open a ticket. So the agent refuses to publish a segmented post on its own. It creates the draft, resolves the filter against List Users, and asks in Slack: "Post targets beta-flow-designer. 41 of 12,340 known users carry that value, which matches the flag rollout. Publish to those 41, or correct the filter?" The release manager answers, the agent publishes, and if the number had come back as the full user base, the whole point of this stop is that it never got that far. Human-in-the-loop here is not an approval rubber stamp. It is one number, put in front of one person, at the last moment it is still cheap.
Agent Capabilities
26 actionsChangelog Posts
6- List Posts Reads changelog posts with their view, click, feedback and reaction counters. Filterable by date range, category, language and published or archived state, and capped at ten posts per page.
- Count Posts Returns the total number of posts matching the supplied filters. Beamer's list endpoints carry no total, so this is how an agent knows how many pages to walk.
- Get Post Reads one post by ID with all translations and engagement counters. Automated reads send Save Views as false where supported, so monitoring does not inflate a post's view statistics.
- Create Post Publishes a post to the Beamer feed and widget, optionally scheduled, pinned, boosted as a top bar or popup, pushed to subscribers, or narrowed to a segment. Content accepts basic HTML. Set Publish to false to stage it as a draft.
- Update Post Replaces the content and settings of an existing post. Used to correct copy, publish a draft, pin an announcement or change its category.
- Delete Post Permanently removes a post and its comments, reactions and statistics. Use Update Post with Archive turned on when the history is worth keeping.
Comments and Reactions
3- List Post Comments Reads user comments on a post, including the commenter's identity and any custom attributes attached to them. Supports date filtering and free-text search.
- Create Post Comment Adds a comment on behalf of an end user. Used to mirror a discussion from another support channel into the feed so the conversation stays in one place.
- List Post Reactions Reads the reactions left on a post, optionally narrowed to positive, neutral or negative sentiment. Used to measure how a release actually landed.
Ideas Board
7- List Feature Requests Reads feature requests with vote and comment counts, filterable by category, status, visibility and free text. Beamer does not publish a fixed list of status or category values, so use whatever the board defines.
- Get Feature Request Reads one request with its full content, vote and comment counts, internal notes and the requesting user. Used to enrich an issue tracker ticket with the demand behind it.
- Create Feature Request Files a request on behalf of a customer so demand captured in a sales call or support ticket lands next to the roadmap. Requires either an internal user email or an end-user identifier.
- Update Feature Request Changes a request's status, category, visibility or internal notes. Moving the status is how roadmap progress gets communicated back to the customers who voted.
- Delete Feature Request Permanently removes a request with its votes and comments. Setting Visible to false is the reversible way to take something off the public board.
- List Feature Request Votes Reads the individual votes on a request, including who voted and when. Used to build the exact contact list for a launch announcement.
- Create Feature Request Vote Records a vote on behalf of an end user, so demand expressed outside Beamer still counts toward prioritization.
End Users and Segments
4- List Users Reads the end users known to Beamer with their identifiers, segment filters, language and first and last seen timestamps. Used to resolve a segment expression into a real audience before publishing to it.
- Create User Registers an end user so they can be targeted by segment filters and tracked across the changelog and NPS surveys. Segment filters are semicolon separated.
- Delete User Removes one or more end users by user ID, Beamer ID or email. Used to honor a data deletion request.
- Get Unread Count Returns how many posts a user has not yet seen, plus their personalized feed and popup URLs. Used to render an unread badge in your own navigation without embedding the widget.
NPS
4- List NPS Responses Reads survey responses with numeric score, written feedback and the responding user, filterable by score band and date range.
- Check NPS Prompt Decides whether a given user should be shown the survey right now according to your scheduling rules, and returns the survey URL if so. Called before rendering a survey in your own UI so the same person is not over-surveyed.
- Send NPS Email Survey Emails a survey to a single user. Used to ask at a moment that means something, such as after onboarding completes or a ticket resolves.
- Get NPS Survey Link Generates a shareable survey URL, optionally personalized to a user so the response is attributed correctly.
Team Access
2- Add Team Member Invites a colleague to the Beamer account at a specific permission level, from Admin down to read-only. Used to keep changelog access in step with identity provisioning.
- Remove Team Member Revokes a colleague's access. Paired with offboarding so departing staff lose publishing rights immediately.
Triggers
3 triggersEvent Triggers
3- On New Post Fires when a new changelog post is published, delivering the post with its translations and category. Used to fan a release note out to other channels, or to confirm to the release channel that the announcement is live. Beamer offers no webhook management API, so this trigger polls and compares against the previous cycle, with a configurable interval down to 30 seconds.
- On New Feature Request Fires when a request is submitted to the ideas board, delivering its title, content, category and the requesting user. Used to open a corresponding issue tracker ticket, or to route a request to the product owner for the area it touches. Polls on the same configurable interval.
- On New NPS Response Fires when a Net Promoter Score response is submitted, delivering the score, written feedback and the responding user. Used to escalate a detractor to the account owner the same day rather than the same month. Polls on the same configurable interval.
Frequently Asked Questions
What can FlowRunner do with Beamer?
FlowRunner agents can run List Posts, Count Posts, and Get Post in Beamer, plus 23 more actions.
Does connecting Beamer to FlowRunner require OAuth?
No. Beamer connects to FlowRunner with an API key, no OAuth flow required.
Can Beamer trigger a FlowRunner workflow automatically?
Yes. Beamer supports 3 triggers that can start a FlowRunner workflow automatically.
Start building with Beamer
$100 in credits. No card required. Connect in minutes.