Marketing Automation

Beamer
API integration

Ship Marketing Automation features without building the integration. Full Beamer API access via Proxy and 40+ MCP-ready tools for AI agents — extend models and mappings to fit your product.

Talk to us

Use Cases

Why integrate with Beamer

Common scenarios for SaaS companies building Beamer integrations for their customers.

Automate changelog publishing from your product

Let your customers auto-publish Beamer posts whenever they ship a feature, close an epic, or mark a project as done inside your app. This removes manual copy-paste work between engineering tools and Beamer.

Pipe NPS and feature votes into customer records

For CRM, CS, and analytics platforms, ingesting Beamer NPS scores and feature request votes gives account teams a real-time view of user sentiment before renewals or QBRs.

Sync feature requests into product management workflows

Roadmap and issue tracking tools can import Beamer feature requests, their statuses, and vote counts as backlog items so PMs can triage user demand alongside internal work.

Build native in-app notification centers

Portal builders and adoption platforms can pull unread Beamer posts and counts to render announcements inside their own UI, keeping branding consistent while staying in sync with Beamer's read state.

Segment announcements using your own user data

Billing, CDP, and analytics tools can push user attributes into Beamer so your customers can target changelog posts by plan tier, cohort, or lifecycle stage without engineering effort.

What You Can Build

Ship these features with Truto + Beamer

Concrete product features your team can ship faster by leveraging Truto’s Beamer integration instead of building from scratch.

One-click changelog publishing

Trigger create_a_beamer_post from your app so users can publish release notes to Beamer directly from a ticket, project, or CMS entry.

NPS sync to customer profiles

Continuously pull Beamer NPS responses and attach scores plus qualitative feedback to the matching user or account record in your product.

Feature request import with vote counts

List Beamer feature requests and their vote totals to surface top-voted user demand inside your roadmap, PM, or CS tool.

Custom in-app notification badge

Use unread post listings and counts (with markAsRead=false) to render a native announcement bell that mirrors Beamer's state inside your UI.

Bulk user attribute sync for segmentation

Push user identities and custom attributes into Beamer via bulk update so your customers can target posts to precise segments like plan tier or region.

Post engagement analytics

Aggregate reactions and comments per Beamer post to show which announcements resonated, feeding adoption dashboards or triggering follow-up walkthroughs.

SuperAI

Beamer AI agent tools

Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.

beamer_ping_ping

Verify your Beamer API key authentication by sending a ping request. Returns: name, url.

list_all_beamer_posts

List existing posts in Beamer with optional filtering by date, language, category, publication status, and segmentation. Returns each post's id, date, published, pinned, category, translations, filter, views, clicks, and reaction counts. Max 10 posts per page.

create_a_beamer_post

Create a new post in Beamer with one or more translations. Returns the created post including id, date, published, category, translations with title and content, and analytics fields such as views, clicks, and feedbacks. Required: title, content. Multiple translations require the Starter plan or above.

beamer_posts_count

Count existing posts in Beamer, optionally filtered by date range, language, category, publication status, segmentation, and user attributes. Returns: url.

get_single_beamer_post_by_id

Get a single Beamer post by id. Returns the full post object including id, date, translations, category, views, clicks, and reaction statistics. Required: id.

update_a_beamer_post_by_id

Update an existing Beamer post by id. Returns the updated post object including id, date, published, pinned, category, translations, and analytics fields such as views, clicks, and reactions. Required: id.

delete_a_beamer_post_by_id

Delete a Beamer post by id. Returns an empty 204 response on success. Required: id.

list_all_beamer_post_comments

List comments for a Beamer post. Returns each comment's id, date, text, postTitle, userId, userEmail, userFirstName, userLastName, url, and userCustomAttributes. Required: post_id.

create_a_beamer_post_comment

Create a new comment on a Beamer post. Returns the created comment including id, date, text, postTitle, userId, userEmail, userFirstName, userLastName, url, and userCustomAttributes. Required: post_id, text.

beamer_post_comments_count

Count existing comments on a Beamer post, optionally filtered by date range, language, or search text. Returns: url. Required: post_id.

get_single_beamer_post_comment_by_id

Get a single Beamer post comment by id. Returns the comment including id, date, text, postTitle, userId, userEmail, userFirstName, userLastName, url, and userCustomAttributes. Required: post_id, id.

delete_a_beamer_post_comment_by_id

Delete a Beamer post comment by id. Returns an empty 204 response on success. Required: post_id, id.

list_all_beamer_post_reactions

List existing reactions for a Beamer post, optionally filtered by date range and reaction type. Returns: id, url. Required: post_id. Max 10 results per page.

create_a_beamer_post_reaction

Create a new reaction on a Beamer post. Returns the created reaction including id, date, reaction, postTitle, userId, userEmail, userFirstName, userLastName, url, and userCustomAttributes. Required: post_id, reaction.

beamer_post_reactions_count

Count existing reactions for a Beamer post, optionally filtered by date range and reaction type. Returns: url. Required: post_id.

get_single_beamer_post_reaction_by_id

Get a single Beamer post reaction by id. Returns the reaction including id, date, reaction, postTitle, userId, userEmail, userFirstName, userLastName, url, and userCustomAttributes. Required: post_id, id.

delete_a_beamer_post_reaction_by_id

Delete a Beamer post reaction by id. Returns an empty 204 response on success. Required: post_id, id.

list_all_beamer_unread

List the unread posts in your Beamer feed for a user. Only posts visible in the feed are returned - draft, deleted, archived, expired and scheduled posts are excluded. Returns an array of posts with id, date, published, pinned, category, translations (title, content, language, images), filter, views, clicks and reaction counts - the same shape as posts list. IMPORTANT: markAsRead defaults to true, so calling this marks the returned posts as read; pass markAsRead=false (and saveViews=false) for a side-effect-free read. Pair userId with Pro+ plans for multi-device read sync. Max 10 posts per page; Truto paginates with page/maxResults.

beamer_unread_count

Count unread posts visible in your Beamer feed. Only posts visible in your feed are counted (draft, deleted, archived, expired, and scheduled posts are excluded). Returns: url.

list_all_beamer_feature_requests

List Beamer feature requests with optional filters by category, status, language, date range, visibility, or search text. Returns: id, url. Max 10 results per page.

create_a_beamer_feature_request

Create a new feature request in Beamer. Returns the created feature request including id, date, visible, category, status, translations, votesCount, commentsCount, notes, and filters. Title and content are string arrays supporting multiple translations simultaneously.

beamer_feature_requests_count

Count existing feature requests in Beamer. Returns the total number of matching feature requests. Accepts an optional filters parameter to narrow the count by segmentation filter.

get_single_beamer_feature_request_by_id

Get a single Beamer feature request by id. Returns: id, url. Required: id.

update_a_beamer_feature_request_by_id

Update a Beamer feature request by id. Returns the updated feature request including id, date, visible, category, status, translations, votesCount, commentsCount, and notes. Required: id.

delete_a_beamer_feature_request_by_id

Delete a feature request in Beamer by id. Returns an empty 204 response on success. Required: id.

list_all_beamer_feature_request_votes

List votes cast on a Beamer feature request. Returns: id, url. Required: feature_request_id.

create_a_beamer_feature_request_vote

Create a new vote on a Beamer feature request. Returns: id, date, featureRequestTitle, userId, userEmail, userFirstName, userLastName, userCustomAttributes, url. Required: feature_request_id.

beamer_feature_request_votes_count

Count existing votes on a Beamer feature request. Returns the total vote count as a count object. Required: feature_request_id.

get_single_beamer_feature_request_vote_by_id

Get a single Beamer feature request vote by id. Returns: id, url. Required: feature_request_id, id.

delete_a_beamer_feature_request_vote_by_id

Delete a Beamer feature request vote by id. Returns an empty 204 response on success. Required: feature_request_id, id.

list_all_beamer_feature_request_comments

List comments on a Beamer feature request. Returns: id, url. Required: feature_request_id.

create_a_beamer_feature_request_comment

Create a new comment on a Beamer feature request. Returns the created comment including id, date, text, visible, and user details. Required: feature_request_id, text.

beamer_feature_request_comments_count

Count existing comments from a Beamer feature request. Returns: url. Required: feature_request_id. Supports optional filters by date range, visibility, language, and text search.

get_single_beamer_feature_request_comment_by_id

Get a single comment from a Beamer feature request by id. Returns: id, url. Required: feature_request_id, id.

delete_a_beamer_feature_request_comment_by_id

Delete a comment from a Beamer feature request by id. Returns an empty 204 response on success. Required: feature_request_id, id.

list_all_beamer_nps

List NPS responses in Beamer, with optional filtering by date, score, and feedback text. Returns each response's id, date, score, feedback, userId, userEmail, userFirstName, userLastName, refUrl, and url. Supports filtering by dateFrom, dateTo, scoreFrom, scoreTo, and search.

beamer_nps_count

Count NPS responses in Beamer, with optional filtering by date, score, and feedback text. Returns a count object with the total number of matching responses. Supports filtering by dateFrom, dateTo, scoreFrom, scoreTo, and search.

beamer_nps_get_survey_url

Get the URL for your NPS survey in Beamer. Returns: url.

list_all_beamer_users

List Beamer analytics users with optional filtering by userId, beamerId, or userEmail. Returns: url. Max 100 per page.

create_a_beamer_user

Create a new user in Beamer Analytics. Returns: userId, userEmail, userFirstName, userLastName, url.

beamer_users_bulk_update

Update matching Beamer analytics users identified by userId, beamerId, or userEmail with new attribute values. Returns: userId, userEmail, userFirstName, userLastName, url.

create_a_beamer_team

Invite a new team member into your Beamer account. Returns: email, role, url. Required: email, role.

beamer_team_bulk_delete

Remove a team member from your Beamer account by email. Returns: email, url. Required: email.

list_all_beamer_feed

Get the URL for your Beamer standalone feed. Returns the feed url. Optional parameters support language selection, segmentation filters, URL filtering, user analytics details, and theme customization.

Why Truto

Why use Truto’s MCP server for Beamer

Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 800+ integrations.

Auto-generated, always up to date

Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.

Fine-grained access control

Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.

Multi-tenant by design

Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.

Works with every MCP client

Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.

Built-in auth, rate limits, and error handling

Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.

Expiring and auditable servers

Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.

How It Works

From zero to integrated

Go live with Beamer in under an hour. No boilerplate, no maintenance burden.

Link your customer’s Beamer account

Use Truto’s frontend SDK to connect your customer’s Beamer account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.

We handle authentication

Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.

Call our API, we call Beamer

Truto’s Proxy API is a 1-to-1 mapping of the Beamer API. You call us, we call Beamer, and pass the response back in the same cycle.

Unified response format

Every response follows a single format across all integrations. We translate Beamer’s pagination into unified cursor-based pagination. Data is always in the result attribute.

FAQs

Common questions about Beamer on Truto

Authentication, rate limits, data freshness, and everything else you need to know before you integrate.

How does authentication work for connecting end-user Beamer accounts?

Truto handles the Beamer credential exchange and storage for you. Your users connect their Beamer account through Truto's connect flow, and Truto injects the correct credentials on every API call so you never handle secrets directly.

What Beamer objects can I read and write?

The integration supports posts, post comments, post reactions, unread posts, feature requests, feature request votes and comments, NPS responses, users, teams, and the activity feed. Most objects support list, get, create, update, and delete where Beamer's API allows.

Does listing unread posts mark them as read?

Yes — by default, calling list_all_beamer_unread marks the returned posts as read in Beamer. If you're building a native notification center and want to preserve read state, pass markAsRead=false in the request.

How does Truto handle pagination and rate limits?

Truto normalizes Beamer's pagination so list endpoints return consistent cursors across calls, and it manages retries and backoff when Beamer rate-limits requests so your integration stays stable under load.

Can I keep data fresh in real time?

Truto supports scheduled polling of Beamer endpoints like list_all_beamer_nps, list_all_beamer_feature_requests, and list_all_beamer_feed to keep downstream systems in sync. Polling frequency is configurable per resource based on your freshness needs.

Can I update users in bulk instead of one at a time?

Yes. The beamer_users_bulk_update tool lets you upsert many users and their custom attributes in a single call, which is the recommended approach for syncing large audiences from a CDP or billing system into Beamer.

From the Blog

Beamer integration guides

Deep dives, architecture guides, and practical tutorials for building Beamer integrations.

Beamer

Get Beamer integrated into your app

Our team understands what it takes to make a Beamer integration successful. A short, crisp 30 minute call with folks who understand the problem.