> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to Beamer

The Beamer connector lets your AI agent act in each user's Beamer account. Each user connects their own Beamer API key once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 49 tools.

**Authentication:** API Key
**Categories:** Marketing, Customer Support
**Tools:** 49: 26 read, 14 write, 9 destructive
**Users sign in with:** API key
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=BEAMER)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Beamer connection

   In **AgentKit > Connections**, create a Beamer connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'beamer'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Beamer:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'beamer_feature_requests_count',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "beamer"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Beamer:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="beamer_feature_requests_count",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their Beamer credentials there. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'beamer_feature_request_comment_get',
  toolInput: {
    comment_id: 7654321,
    feature_request_id: 98765,
  },
  connector: 'beamer',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="beamer_feature_request_comment_get",
    tool_input={
        "comment_id": 7654321,
        "feature_request_id": 98765,
    },
    connection_name="beamer",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `beamer_feature_request_comment_get`

Get Feature Request Comment · Read-only

Get one comment on a feature request.
Returns the comment's id, text, visibility, date and author details.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `comment_id` (`integer`, required): ID of the comment, from the matching comments list tool. Example: 7654321.
- `feature_request_id` (`integer`, required): ID of the feature request, from beamer_feature_requests_list. Example: 98765.

Example input: `{"comment_id":7654321,"feature_request_id":98765}`

### `beamer_feature_request_comments_count`

Count Feature Request Comments · Read-only

Count comments on a feature request.
Returns the count.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `feature_request_id` (`integer`, required): ID of the feature request, from beamer_feature_requests_list. Example: 98765.
- `date_from` (`string`, optional): Count comments published after this date. The date must follow the ISO-8601 format. Example: 2026-01-01T00:00:00Z.
- `date_to` (`string`, optional): Count comments published before this date. The date must follow the ISO-8601 format. Example: 2026-01-31T23:59:59Z.
- `language` (`string`, optional): Count comments with translations in this language. The language must follow the ISO-639 two-letter code format. Example: en.
- `search` (`string`, optional): Count comments with content that contain this text. Example: dark mode.
- `visible` (`boolean`, optional): Count only visible (or not visible) comments. If unspecified, both types of comments will be retrieved. Example: true.

Example input: `{"feature_request_id":98765}`

### `beamer_feature_request_comments_list`

List Feature Request Comments · Read-only

List comments on a feature request, at most 10 per page.
Returns each comment's id, text, visibility, date and author details.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `feature_request_id` (`integer`, required): ID of the feature request, from beamer_feature_requests_list. Example: 98765.
- `date_from` (`string`, optional): Retrieve comments published after this date. The date must follow the ISO-8601 format. Example: 2026-01-01T00:00:00Z.
- `date_to` (`string`, optional): Retrieve comments published before this date. The date must follow the ISO-8601 format. Example: 2026-01-31T23:59:59Z.
- `language` (`string`, optional): Retrieve comments with translations in this language. The language must follow the ISO-639 two-letter code format. Example: en.
- `max_results` (`integer`, optional): Maximum number of items to return per page (Beamer returns at most 10). Example: 10.
- `page` (`integer`, optional): Page number to return, combined with max_results, starting at 1. Example: 1.
- `search` (`string`, optional): Retrieve comments with content that contain this text. Example: dark mode.
- `visible` (`boolean`, optional): Retrieve only visible (or not visible) comments. If unspecified, both types of comments will be retrieved. Example: true.

Example input: `{"feature_request_id":98765}`

### `beamer_feature_request_get`

Get Feature Request · Read-only

Get one feature request.
Returns its id, translations, status, category, notes, visibility, vote and comment counts.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `feature_request_id` (`integer`, required): ID of the feature request, from beamer_feature_requests_list. Example: 98765.

Example input: `{"feature_request_id":98765}`

### `beamer_feature_request_vote_get`

Get Feature Request Vote · Read-only

Get one vote on a feature request.
Returns the vote's id, date and voter details.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `feature_request_id` (`integer`, required): ID of the feature request, from beamer_feature_requests_list. Example: 98765.
- `vote_id` (`integer`, required): ID of the vote, from beamer_feature_request_votes_list. Example: 112233.

Example input: `{"feature_request_id":98765,"vote_id":112233}`

### `beamer_feature_request_votes_count`

Count Feature Request Votes · Read-only

Count the votes on a feature request.
Returns the count.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `feature_request_id` (`integer`, required): ID of the feature request, from beamer_feature_requests_list. Example: 98765.

Example input: `{"feature_request_id":98765}`

### `beamer_feature_request_votes_list`

List Feature Request Votes · Read-only

List the votes on a feature request, at most 10 per page.
Returns each vote's id, date and voter details.
Use beamer_feature_request_votes_count for the total.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `feature_request_id` (`integer`, required): ID of the feature request, from beamer_feature_requests_list. Example: 98765.
- `date_from` (`string`, optional): Retrieve votes created after this date. The date must follow the ISO-8601 format. Example: 2026-01-01T00:00:00Z.
- `date_to` (`string`, optional): Retrieve votes created before this date. The date must follow the ISO-8601 format. Example: 2026-01-31T23:59:59Z.
- `max_results` (`integer`, optional): Maximum number of items to return per page (Beamer returns at most 10). Example: 10.
- `page` (`integer`, optional): Page number to return, combined with max_results, starting at 1. Example: 1.

Example input: `{"feature_request_id":98765}`

### `beamer_feature_requests_count`

Count Feature Requests · Read-only

Count feature requests matching the same filters as beamer_feature_requests_list.
Returns the count.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `category` (`string`, optional): Count feature requests with this category. Example: new.
- `date_from` (`string`, optional): Count feature requests created after this date. The date must follow the ISO-8601 format. Example: 2026-01-01T00:00:00Z.
- `date_to` (`string`, optional): Count feature requests created before this date. The date must follow the ISO-8601 format. Example: 2026-01-31T23:59:59Z.
- `filters` (`string`, optional): Count feature requests with a matching segmentation filter. (Only available on the Pro plan (and up)). Example: beta.
- `language` (`string`, optional): Count feature requests with translations in this language. The language must follow the ISO-639 two-letter code format. Example: en.
- `search` (`string`, optional): Count feature requests with title or content that contain this text. Example: dark mode.
- `status` (`string`, optional): Count feature requests with this status. Example: under_review.
- `visible` (`boolean`, optional): Count only visible (or not visible) feature requests. If unspecified, both types of feature requests will be retrieved. Example: true.

Example input: `{}`

### `beamer_feature_requests_list`

List Feature Requests · Read-only

List feature requests (ideas) from the Beamer feedback board, filtered by date, category, status, visibility or text, at most 10 per page.
Returns each request's id, translations, status, category, vote and comment counts.
Use this to find a feature request ID. Use beamer_feature_requests_count for totals.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `category` (`string`, optional): Retrieve feature requests with this category. Example: new.
- `date_from` (`string`, optional): Retrieve feature requests created after this date. The date must follow the ISO-8601 format. Example: 2026-01-01T00:00:00Z.
- `date_to` (`string`, optional): Retrieve feature requests created before this date. The date must follow the ISO-8601 format. Example: 2026-01-31T23:59:59Z.
- `filters` (`string`, optional): Retrieve feature requests with a matching segmentation filter. (Only available on the Pro plan (and up)). Example: beta.
- `language` (`string`, optional): Retrieve feature requests with translations in this language. The language must follow the ISO-639 two-letter code format. Example: en.
- `max_results` (`integer`, optional): Maximum number of items to return per page (Beamer returns at most 10). Example: 10.
- `page` (`integer`, optional): Page number to return, combined with max_results, starting at 1. Example: 1.
- `search` (`string`, optional): Retrieve feature requests with title or content that contain this text. Example: dark mode.
- `status` (`string`, optional): Retrieve feature requests with this status. Example: under_review.
- `visible` (`boolean`, optional): Retrieve only visible (or not visible) feature requests. If unspecified, both types of feature requests will be retrieved. Example: true.

Example input: `{}`

### `beamer_feed_url_get`

Get Feed URL · Read-only

Get the URL of your standalone Beamer changelog feed, optionally personalized for one viewer.
Returns the feed URL.
Use this to share or link to the public changelog.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter` (`string`, optional): Retrieve posts with a matching segmentation filter. (Only available on the Pro plan (and up)). Example: beta;admin.
- `filter_by_url` (`boolean`, optional): Whether to apply URL filtering to the feed. (Only available on the Pro plan (and up)). Example: true.
- `force_filter` (`string`, optional): Only retrieve posts that match this segmentation filter. (Only available on the Pro plan (and up)). Example: beta.
- `language` (`string`, optional): Retrieve the URL for your feed in a specific language. The language must follow the ISO-639 two-letter code format. (Only available on the Starter plan (and up)). Example: en.
- `theme` (`string`, optional): Theme class to use for appearance customization via CSS. (Only available on the Pro plan (and up)). Example: dark.
- `user_email` (`string`, optional): Email of the user viewing the feed (for Analytics). Example: jane@example.com.
- `user_first_name` (`string`, optional): First name of the user viewing the feed (for Analytics). Example: Jane.
- `user_id` (`string`, optional): ID of the user viewing the feed (for Analytics). Example: user_123.
- `user_last_name` (`string`, optional): Last name of the user viewing the feed (for Analytics). Example: Doe.

Example input: `{}`

### `beamer_nps_check`

Check NPS Prompt · Read-only

Check whether an end user should be shown the NPS survey now, based on your NPS settings and their history.
Returns whether to show the prompt.
Identify the user with user_id, beamer_id or user_email.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `beamer_id` (`string`, optional): Beamer generated ID for the user. Example: 84391274.
- `created_at` (`string`, optional): Creation/signup date for this user. The date must follow the ISO-8601 format. Example: 2025-06-01T00:00:00Z.
- `filter` (`string`, optional): Segmentation filters applied to this user. Example: beta;admin.
- `language` (`string`, optional): Language of the user. Example: en.
- `mobile` (`boolean`, optional): Whether this user is coming from a mobile device. If unspecified, it will be considered false. Example: true.
- `multi` (`boolean`, optional): Only applicable if using the userId parameter. If true, Beamer will consider different userId s strictly as different users - even if the userIds are associated to the same browser or device. If unspecified, it will be considered false. Example: true.
- `url` (`string`, optional): Current URL (where the user is at now). Example: https://app.example.com/settings.
- `user_email` (`string`, optional): Email of the user. Example: jane@example.com.
- `user_first_name` (`string`, optional): First name of the user. Example: Jane.
- `user_id` (`string`, optional): ID of the user (as defined in the embedded script's user_id parameter). Example: user_123.
- `user_last_name` (`string`, optional): Last name of the user. Example: Doe.

Example input: `{}`

### `beamer_nps_link_get`

Get NPS Survey Link · Read-only

Get a personal NPS survey link for an end user, to send yourself.
Returns the survey URL.
Use beamer_nps_email_send to have Beamer email the survey instead.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `user_email` (`string`, optional): Email of the user to generate the NPS survey link for. Example: jane@example.com.
- `user_first_name` (`string`, optional): First name of the user to survey. Example: Jane.
- `user_id` (`string`, optional): ID of the user to generate the NPS survey link for. Example: user_123.
- `user_last_name` (`string`, optional): Last name of the user to survey. Example: Doe.

Example input: `{}`

### `beamer_nps_responses_count`

Count NPS Responses · Read-only

Count NPS survey responses matching date, score or text filters.
Returns the count.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `date_from` (`string`, optional): Retrieve NPS responses sent after this date. The date must follow the ISO-8601 format. Example: 2026-01-01T00:00:00Z.
- `date_to` (`string`, optional): Retrieve NPS responses sent before this date. The date must follow the ISO-8601 format. Example: 2026-01-31T23:59:59Z.
- `score_from` (`integer`, optional): Retrieve NPS responses with a score of this value or greater. Example: 0.
- `score_to` (`integer`, optional): Retrieve NPS responses with a score of this value or less. Example: 6.
- `search` (`string`, optional): Retrieve NPS responses with feedback that contains this text. The search value can also match the name of the user. Example: dark mode.

Example input: `{}`

### `beamer_nps_responses_list`

List NPS Responses · Read-only

List NPS survey responses, filtered by date, score range or text, at most 10 per page.
Returns each response's id, date, score, feedback text and user details.
Use beamer_nps_responses_count for totals.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `date_from` (`string`, optional): Retrieve NPS responses sent after this date. The date must follow the ISO-8601 format. Example: 2026-01-01T00:00:00Z.
- `date_to` (`string`, optional): Retrieve NPS responses sent before this date. The date must follow the ISO-8601 format. Example: 2026-01-31T23:59:59Z.
- `max_results` (`integer`, optional): Maximum number of items to return per page (Beamer returns at most 10). Example: 10.
- `page` (`integer`, optional): Page number to return, combined with max_results, starting at 1. Example: 1.
- `score_from` (`integer`, optional): Retrieve NPS responses with a score of this value or greater. Example: 0.
- `score_to` (`integer`, optional): Retrieve NPS responses with a score of this value or less. Example: 6.
- `search` (`string`, optional): Retrieve NPS responses with feedback that contains this text. The search value can also match the name of the user. Example: dark mode.

Example input: `{}`

### `beamer_ping`

Ping · Read-only

Check that the Beamer API key works.
Returns the name of your Beamer product.
Use this to confirm the connection.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `beamer_post_comment_get`

Get Post Comment · Read-only

Get one comment on a changelog post.
Returns the comment's id, text, date and author details.
Use beamer_post_comments_list to find the comment ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `comment_id` (`integer`, required): ID of the comment, from the matching comments list tool. Example: 7654321.
- `post_id` (`integer`, required): ID of the post, from beamer_posts_list. Example: 1234567.

Example input: `{"comment_id":7654321,"post_id":1234567}`

### `beamer_post_comments_count`

Count Post Comments · Read-only

Count comments on a changelog post, with the same filters as beamer_post_comments_list.
Returns the count.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `post_id` (`integer`, required): ID of the post, from beamer_posts_list. Example: 1234567.
- `date_from` (`string`, optional): Retrieve comments published after this date. The date must follow the ISO-8601 format. Example: 2026-01-01T00:00:00Z.
- `date_to` (`string`, optional): Retrieve comments published before this date. The date must follow the ISO-8601 format. Example: 2026-01-31T23:59:59Z.
- `language` (`string`, optional): Retrieve comments with translations in this language. The language must follow the ISO-639 two-letter code format. Example: en.
- `search` (`string`, optional): Retrieve comments with content that contain this text. Example: dark mode.

Example input: `{"post_id":1234567}`

### `beamer_post_comments_list`

List Post Comments · Read-only

List comments users left on a changelog post, at most 10 per page.
Returns each comment's id, text, date and author details.
Use beamer_post_comments_count for the total.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `post_id` (`integer`, required): ID of the post, from beamer_posts_list. Example: 1234567.
- `date_from` (`string`, optional): Retrieve comments published after this date. The date must follow the ISO-8601 format. Example: 2026-01-01T00:00:00Z.
- `date_to` (`string`, optional): Retrieve comments published before this date. The date must follow the ISO-8601 format. Example: 2026-01-31T23:59:59Z.
- `language` (`string`, optional): Retrieve comments with translations in this language. The language must follow the ISO-639 two-letter code format. Example: en.
- `max_results` (`integer`, optional): Maximum number of items to return per page (Beamer returns at most 10). Example: 10.
- `page` (`integer`, optional): Page number to return, combined with max_results, starting at 1. Example: 1.
- `search` (`string`, optional): Retrieve comments with content that contain this text. Example: dark mode.

Example input: `{"post_id":1234567}`

### `beamer_post_get`

Get Post · Read-only

Get one changelog post.
Returns its id, date, translations (title, content, link), category, flags and view, click and feedback counts.
Use beamer_posts_list to find the post ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `post_id` (`integer`, required): ID of the post, from beamer_posts_list. Example: 1234567.
- `ignore_request_details` (`boolean`, optional): Whether request-specific details should be ignored (this includes IP, browser/OS and geolocation details). Useful when sending requests from your backend, where the request's details aren't representative of the end user. Example: true.
- `language` (`string`, optional): ID of the user viewing these posts (for Analytics). Example: en.
- `traceable_links` (`boolean`, optional): Whether links in the post should be converted to a traceable format (both the CTA and links within the content). If true, the opened URL will be tracked and record a 'click' entry in your Analytics. Example: true.
- `user_email` (`string`, optional): Email of the user viewing these posts (for Analytics). Example: jane@example.com.
- `user_first_name` (`string`, optional): First name of the user viewing these posts (for Analytics). Example: Jane.
- `user_id` (`string`, optional): ID of the user viewing these posts (for Analytics). Example: user_123.
- `user_last_name` (`string`, optional): Last name of the user viewing these posts (for Analytics). Example: Doe.

Example input: `{"post_id":1234567}`

### `beamer_post_reaction_get`

Get Post Reaction · Read-only

Get one reaction on a changelog post.
Returns the reaction's id, type, date and user details.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `post_id` (`integer`, required): ID of the post, from beamer_posts_list. Example: 1234567.
- `reaction_id` (`integer`, required): ID of the reaction, from beamer_post_reactions_list. Example: 456789.

Example input: `{"post_id":1234567,"reaction_id":456789}`

### `beamer_post_reactions_count`

Count Post Reactions · Read-only

Count reactions on a changelog post, optionally of one type.
Returns the count.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `post_id` (`integer`, required): ID of the post, from beamer_posts_list. Example: 1234567.
- `date_from` (`string`, optional): Retrieve reactions published after this date. The date must follow the ISO-8601 format. Example: 2026-01-01T00:00:00Z.
- `date_to` (`string`, optional): Retrieve reactions published before this date. The date must follow the ISO-8601 format. Example: 2026-01-31T23:59:59Z.
- `reaction` (`string`, optional): Retrieve reactions with this reaction type (positive, neutral or negative). Example: positive.

Example input: `{"post_id":1234567}`

### `beamer_post_reactions_list`

List Post Reactions · Read-only

List reactions (positive, neutral or negative) users gave a changelog post, at most 10 per page.
Returns each reaction's id, type, date and user details.
Use beamer_post_reactions_count for totals.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `post_id` (`integer`, required): ID of the post, from beamer_posts_list. Example: 1234567.
- `date_from` (`string`, optional): Retrieve reactions published after this date. The date must follow the ISO-8601 format. Example: 2026-01-01T00:00:00Z.
- `date_to` (`string`, optional): Retrieve reactions published before this date. The date must follow the ISO-8601 format. Example: 2026-01-31T23:59:59Z.
- `max_results` (`integer`, optional): Maximum number of items to return per page (Beamer returns at most 10). Example: 10.
- `page` (`integer`, optional): Page number to return, combined with max_results, starting at 1. Example: 1.
- `reaction` (`string`, optional): Retrieve reactions with this reaction type (positive, neutral or negative). Example: positive.

Example input: `{"post_id":1234567}`

### `beamer_posts_count`

Count Posts · Read-only

Count changelog posts that match the same filters as beamer_posts_list.
Returns the count.
Use this for totals without fetching the posts.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `archived` (`boolean`, optional): Count only archived (or not archived) posts. If unspecified, both types of posts will be counted. Example: true.
- `category` (`string`, optional): Count posts with this category. Example: new.
- `date_from` (`string`, optional): Count posts published after this date. The date must follow the ISO-8601 format. Example: 2026-01-01T00:00:00Z.
- `date_to` (`string`, optional): Count posts published before this date. The date must follow the ISO-8601 format. Example: 2026-01-31T23:59:59Z.
- `expired` (`boolean`, optional): Count only expired (or not expired) posts; posts without an expiration date are considered not expired. If unspecified, both types of posts will be counted. Example: true.
- `filter` (`string`, optional): Count posts with a matching segmentation filter. (Only available on the Pro plan (and up)). Example: beta;admin.
- `filter_by_user_id` (`boolean`, optional): If true, single-user posts will be counted when matching the userId parameter. If false (or if no userId is provided), single-user posts will not be counted. (Only available on the Scale plan). Example: true.
- `filter_url` (`string`, optional): If URL segmentation is enabled, include posts with a matching segmentation URL. (Only available on the Pro plan (and up)). Example: https://app.example.com/dashboard.
- `force_filter` (`string`, optional): Only count posts that match this segmentation filter. (Only available on the Pro plan (and up)). Example: beta.
- `ignore_filters` (`boolean`, optional): If true, all posts will be counted, ignoring any segmentation they may have. This parameter should only be used for requests sent from the backend. [In order to user this parameter, the API key should have the 'Read posts (ignore filters)' permission enabled.]. Example: true.
- `language` (`string`, optional): Count posts with translations in this language. The language must follow the ISO-639 two-letter code format. (Only available on the Starter plan (and up)). Example: en.
- `published` (`boolean`, optional): Count only published (or draft) posts. If unspecified, both types of posts will be counted. Example: true.
- `user_id` (`string`, optional): For using with the filterByUserId parameter only. Example: user_123.

Example input: `{}`

### `beamer_posts_list`

List Posts · Read-only

List changelog posts, filtered by date, category, language, status or segment, at most 10 per page.
Returns each post's id, date, translations (title, content, link), category, flags and view counts.
Use this to browse or find a post ID. Use beamer_posts_count for totals, beamer_unread_posts_list for one user's unread posts and beamer_post_get for one post.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `archived` (`boolean`, optional): Retrieve only archived (or not archived) posts. If unspecified, both types of posts will be retrieved. Example: true.
- `category` (`string`, optional): Retrieve posts with this category. Example: new.
- `date_from` (`string`, optional): Retrieve posts published after this date. The date must follow the ISO-8601 format. Example: 2026-01-01T00:00:00Z.
- `date_to` (`string`, optional): Retrieve posts published before this date. The date must follow the ISO-8601 format. Example: 2026-01-31T23:59:59Z.
- `expired` (`boolean`, optional): Retrieve only expired (or not expired) posts; posts without an expiration date are considered not expired. If unspecified, both types of posts will be retrieved. (Only available on the Starter plan (and up)). Example: true.
- `filter` (`string`, optional): Retrieve posts with a matching segmentation filter. (Only available on the Pro plan (and up)). Example: beta;admin.
- `filter_by_user_id` (`boolean`, optional): If true, single-user posts will be retrieved when matching the userId parameter. If false (or if no userId is provided), single-user posts will not be retrieved. (Only available on the Scale plan). Example: true.
- `filter_url` (`string`, optional): If URL segmentation is enabled, include posts with a matching segmentation URL. (Only available on the Pro plan (and up)). Example: https://app.example.com/dashboard.
- `force_filter` (`string`, optional): Only retrieve posts that match this segmentation filter. (Only available on the Pro plan (and up)). Example: beta.
- `ignore_filters` (`boolean`, optional): If true, all posts will be retrieved, ignoring any segmentation they may have. This parameter should only be used for requests sent from the backend. [In order to user this parameter, the API key should have the 'Read posts (ignore filters)' permission enabled.]. Example: true.
- `ignore_request_details` (`boolean`, optional): Whether request-specific details should be ignored (this includes IP, browser/OS and geolocation details). Useful when sending requests from your backend, where the request's details aren't representative of the end user. Example: true.
- `language` (`string`, optional): Retrieve posts with translations in this language. The language must follow the ISO-639 two-letter code format. Example: en.
- `max_results` (`integer`, optional): Maximum number of items to return per page (Beamer returns at most 10). Example: 10.
- `page` (`integer`, optional): Page number to return, combined with max_results, starting at 1. Example: 1.
- `published` (`boolean`, optional): Retrieve only published (or draft) posts. If unspecified, both types of posts will be retrieved. Example: true.
- `save_views` (`boolean`, optional): Whether to save views for the posts retrieved (for Analytics). If unspecified, views are saved. Example: true.
- `traceable_links` (`boolean`, optional): Whether links in the post should be converted to a traceable format (both the CTA and links within the content). If true, the opened URL will be tracked and record a 'click' entry in your Analytics. Example: true.
- `user_email` (`string`, optional): Email of the user viewing these posts (for Analytics). Example: jane@example.com.
- `user_first_name` (`string`, optional): First name of the user viewing these posts (for Analytics). Example: Jane.
- `user_id` (`string`, optional): ID of the user viewing these posts (for Analytics). Example: user_123.
- `user_last_name` (`string`, optional): Last name of the user viewing these posts (for Analytics). Example: Doe.

Example input: `{}`

### `beamer_unread_posts_count`

Count Unread Posts · Read-only

Count the changelog posts one end user has not read yet.
Returns the count.
Identify the user with user_id or user_email.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `category` (`string`, optional): Count posts with this category. Example: new.
- `date_from` (`string`, optional): Count posts published after this date. The date must follow the ISO-8601 format. Example: 2026-01-01T00:00:00Z.
- `filter` (`string`, optional): Count posts with a matching segmentation filter. (Only available on the Pro plan (and up)). Example: beta;admin.
- `filter_url` (`string`, optional): If URL segmentation is enabled, include posts with a matching segmentation URL. (Only available on the Pro plan (and up)). Example: https://app.example.com/dashboard.
- `force_filter` (`string`, optional): Only count posts that match this segmentation filter. (Only available on the Pro plan (and up)). Example: beta.
- `ignore_filters` (`boolean`, optional): If true, all posts will be counted, ignoring any segmentation they may have. This parameter should only be used for requests sent from the backend. [In order to user this parameter, the API key should have the 'Read posts (ignore filters)' permission enabled.]. Example: true.
- `language` (`string`, optional): Count posts with translations in this language. The language must follow the ISO-639 two-letter code format. Example: en.
- `theme` (`string`, optional): Theme class to use for appearance customization via CSS. (Only available on the Pro plan (and up)). Example: dark.
- `user_email` (`string`, optional): Email of the user viewing these posts (for Analytics). Example: jane@example.com.
- `user_first_name` (`string`, optional): First name of the user viewing these posts (for Analytics). Example: Jane.
- `user_id` (`string`, optional): ID of the user viewing these posts (for Analytics). If single-user posts are enabled, posts with a matching userId will be counted. (Only available on the Scale plan) If multi-device synchronization is enabled, the dateFrom parameter will be overridden by this user's last date of viewing your feed - if any. dateFrom can be omitted in this case. (Only available on the Pro plan (and up)). Example: user_123.
- `user_last_name` (`string`, optional): Last name of the user viewing these posts (for Analytics). Example: Doe.

Example input: `{}`

### `beamer_users_list`

List Users · Read-only

List end users recorded in Beamer Analytics, optionally one user by ID or email, sorted by any attribute.
Returns each user's beamerId, userId, email, name, language, location, device and activity dates.
Use this to look up a user's Beamer ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `beamer_id` (`string`, optional): Beamer generated ID for the user. Example: 84391274.
- `max_results` (`integer`, optional): Maximum number of items to return per page (Beamer returns at most 10). Example: 10.
- `page` (`integer`, optional): Page number to return, combined with max_results, starting at 1. Example: 1.
- `sort` (`string`, optional): Sort users by this attribute (in ascending order). This parameter can contain any of the user attributes returned by this endpoint, including custom attributes. Adding a hyphen ('-') before the attribute will sort the results in descending order. For example, sort=lastSeen will first retrieve users with the oldest 'last seen' date, while sort=-lastSeen will retrieve users that were 'last seen' most recently. By default, users are sorted by firstSeen (oldest first). Example: -lastSeen.
- `user_email` (`string`, optional): Email of the user. Example: jane@example.com.
- `user_id` (`string`, optional): ID of the user (as defined in the embedded script's user_id parameter). Example: user_123.

Example input: `{}`

### `beamer_feature_request_comment_create`

Create Feature Request Comment · Write

Add a comment to a feature request on behalf of an end user.
Returns the created comment.
Identify the end user with user_id, user_email, user_firstname or user_lastname.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `feature_request_id` (`integer`, required): ID of the feature request, from beamer_feature_requests_list. Example: 98765.
- `text` (`string`, required): Content of the comment. Example: Love this update!.
- `user_email` (`string`, optional): Email of the end user who created this comment. Example: jane@example.com.
- `user_firstname` (`string`, optional): First name of the end user who created this comment. Example: Jane.
- `user_id` (`string`, optional): ID of the end user who created this comment. Example: user_123.
- `user_lastname` (`string`, optional): Last name of the end user who created this comment. Example: Doe.
- `visible` (`boolean`, optional): Whether this comment should be visible or not. Example: true.

Example input: `{"feature_request_id":98765,"text":"<text>"}`

### `beamer_feature_request_create`

Create Feature Request · Write

Create a feature request on the Beamer feedback board, as a team member or on behalf of an end user.
Returns the created feature request.
Send internal_user_email for a team member, or at least one of user_id, user_email, user_firstname or user_lastname for an end user.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `title` (`array`, required): Feature request title, as an array with one entry per translation, for example ["Add dark mode"]. Example: ["Add dark mode"]
- `category` (`string`, optional): Category of the feature request. Example: UI.
- `content` (`array`, optional): Feature request description, as an array with one entry per translation. Example: ["It would be great to have a dark theme."]
- `date` (`string`, optional): Publication date for this post in ISO-8601 format. [Future dates / post scheduling are only available on the Starter plan (and up)]. Example: 2026-02-01T09:00:00Z.
- `filters` (`string`, optional): Segmentation filters for the feature request. Example: beta.
- `internal_user_email` (`string`, optional): Email of the user in your account creating this feature request (if created by a team member). [Required if not sending userId , userEmail , userFirstname or _userLastname_] . Example: pm@example.com.
- `language` (`array`, optional): ISO-639 two-letter language of each translation, for example ["en"] (Starter plan and up). Example: ["en"]
- `notes` (`string`, optional): Notes for the feature request. Example: Planned for Q3.
- `status` (`string`, optional): Status of the feature request, for example under_review, planned, in_progress or complete (as configured in Beamer). Example: under_review.
- `user_email` (`string`, optional): Email of the end user creating this feature request (if created by an end user). [If not sending internalUserEmail , at least one of userId , userEmail , userFirstname or userLastname are required] . Example: jane@example.com.
- `user_firstname` (`string`, optional): First name of the end user creating this feature request (if created by an end user). [If not sending internalUserEmail , at least one of userId , userEmail , userFirstname or userLastname are required] . Example: Jane.
- `user_id` (`string`, optional): ID of the end user creating this feature request (if created by an end user). [If not sending internalUserEmail , at least one of userId , userEmail , userFirstname or userLastname are required] . Example: user_123.
- `user_lastname` (`string`, optional): Last name of the end user creating this feature request (if created by an end user). [If not sending internalUserEmail , at least one of userId , userEmail , userFirstname or userLastname are required] . Example: Doe.
- `visible` (`boolean`, optional): Whether this feature request should be visible in your feed. Example: true.
- `votes_count` (`integer`, optional): Number of votes to create for this feature request. Example: 3.

Example input: `{"title":["Add dark mode"]}`

### `beamer_feature_request_update`

Update Feature Request · Write

Update a feature request's text, status, category, notes or visibility.
Returns the updated feature request.
Only the fields you set are sent.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `feature_request_id` (`integer`, required): ID of the feature request, from beamer_feature_requests_list. Example: 98765.
- `category` (`string`, optional): Category of the feature request. Example: UI.
- `content` (`array`, optional): Feature request description, as an array with one entry per translation. Example: ["It would be great to have a dark theme."]
- `date` (`string`, optional): Publication date for this post in ISO-8601 format. [Future dates / post scheduling are only available on the Starter plan (and up)]. Example: 2026-02-01T09:00:00Z.
- `filters` (`string`, optional): Segmentation filters for the feature request. Example: beta.
- `language` (`array`, optional): ISO-639 two-letter language of each translation, for example ["en"] (Starter plan and up). Example: ["en"]
- `notes` (`string`, optional): Notes for the feature request. Example: Planned for Q3.
- `status` (`string`, optional): Status of the feature request, for example under_review, planned, in_progress or complete (as configured in Beamer). Example: under_review.
- `title` (`array`, optional): Feature request title, as an array with one entry per translation, for example ["Add dark mode"]. Example: ["Add dark mode"]
- `visible` (`boolean`, optional): Whether this feature request should be visible in your feed. Example: true.

Example input: `{"feature_request_id":98765}`

### `beamer_feature_request_vote_create`

Create Feature Request Vote · Write

Add an end user's vote to a feature request.
Returns the created vote.
Identify the end user with user_id, user_email, user_firstname or user_lastname.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `feature_request_id` (`integer`, required): ID of the feature request, from beamer_feature_requests_list. Example: 98765.
- `user_email` (`string`, optional): Email of the end user who created this vote. Example: jane@example.com.
- `user_firstname` (`string`, optional): First name of the end user who created this vote. Example: Jane.
- `user_id` (`string`, optional): ID of the end user who created this vote. Example: user_123.
- `user_lastname` (`string`, optional): Last name of the end user who created this vote. Example: Doe.

Example input: `{"feature_request_id":98765}`

### `beamer_nps_email_send`

Send NPS Email Survey · Write

Email an NPS survey to an end user.
Returns a confirmation.
Use beamer_nps_link_get to get a link without sending an email.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `user_email` (`string`, required): Email address to send the NPS survey to. Example: jane@example.com.

Example input: `{"user_email":"<user_email>"}`

### `beamer_post_comment_create`

Create Post Comment · Write

Add a comment to a changelog post on behalf of an end user.
Returns the created comment.
Identify the end user with user_id, user_email, user_firstname or user_lastname.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `post_id` (`integer`, required): ID of the post, from beamer_posts_list. Example: 1234567.
- `text` (`string`, required): Content of the comment. Example: Love this update!.
- `user_email` (`string`, optional): Email of the end user who created this comment. Example: jane@example.com.
- `user_firstname` (`string`, optional): First name of the end user who created this comment. Example: Jane.
- `user_id` (`string`, optional): ID of the end user who created this comment. Example: user_123.
- `user_lastname` (`string`, optional): Last name of the end user who created this comment. Example: Doe.

Example input: `{"post_id":1234567,"text":"<text>"}`

### `beamer_post_create`

Create Post · Write

Create a changelog post, published right away or saved as a draft, optionally in several languages.
Returns the created post with its id.
title, content, language, link_url and link_text are arrays with one entry per translation, in matching order.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `category` (`string`, required): Post category: new, improvement, fix, comingsoon, announcement or other (custom categories on paid plans). Separate several with semicolons. Example: new.
- `content` (`array`, required): Post body (HTML allowed), as an array with one entry per translation. Array with one entry per translation, in the same order as the other per-translation arrays (title, content, language, link_url, link_text). Example: ["You can now switch to dark mode from Settings.
"]
- `title` (`array`, required): Post title, as an array with one entry per translation, for example ["Dark mode is here"]. Array with one entry per translation, in the same order as the other per-translation arrays (title, content, language, link_url, link_text). Example: ["Dark mode is here"]
- `archive` (`boolean`, optional): Whether to archive this post or not. Example: true.
- `auto_open` (`boolean`, optional): Enable this to automatically open Beamer's sidebar the first time the user gets this post (Only available on the Starter plan (and up)) Deprecated. Example: true.
- `boosted_announcement` (`string`, optional): Type of boosted announcement to set for this post. (Only available with the Boosted Announcements add-on). Example: snippet. One of: `top-bar`, `popup`, `snippet`, `tooltip`.
- `date` (`string`, optional): Publication date for this post in ISO-8601 format. [Future dates / post scheduling are only available on the Starter plan (and up)]. Example: 2026-02-01T09:00:00Z.
- `due_date` (`string`, optional): Expiration date for this post in ISO-8601 format. (Only available on the Starter plan (and up)). Example: 2026-03-01T00:00:00Z.
- `enable_feedback` (`boolean`, optional): Whether to enable or disable user feedback for this post (Only available on the Pro plan (and up)). Example: true.
- `enable_reactions` (`boolean`, optional): Whether to enable or disable user reactions for this post (Only available on the Pro plan (and up)). Example: true.
- `enable_social_share` (`boolean`, optional): Enable this to show options for your users to share this post on social media . Example: true.
- `filter` (`string`, optional): Segmentation filter (or filters) for this post. (Only available on the Pro plan (and up)). Example: beta;admin.
- `filter_url` (`string`, optional): URL where the post is shown; * is a wildcard and several URLs are separated by semicolons (Pro plan and up). Example: https://app.example.com/dashboard.
- `filter_user_id` (`string`, optional): User ID to apply as a filter. This post will only be shown to users that have the same ' user_id ' parameter in the embedded script. Multiple IDs can be passed in, separated by semicolons (;). (Only available on the Scale plan). Example: user_123;user_456.
- `fixed_boosted_announcement` (`boolean`, optional): Enable this for the post to be shown as a fixed top-bar announcement. Example: true.
- `language` (`array`, optional): ISO-639 two-letter language of each translation, for example ["en", "es"]. Array with one entry per translation, in the same order as the other per-translation arrays (title, content, language, link_url, link_text) (Starter plan and up). Example: ["en"]
- `link_text` (`array`, optional): Call-to-action link text per translation. Array with one entry per translation, in the same order as the other per-translation arrays (title, content, language, link_url, link_text). Example: ["Read more"]
- `link_url` (`array`, optional): Call-to-action URL per translation, opened when the header or bottom link is clicked. Array with one entry per translation, in the same order as the other per-translation arrays (title, content, language, link_url, link_text). Example: ["https://example.com/blog/dark-mode"]
- `links_in_new_window` (`boolean`, optional): Whether to open links in a new window/tab (true) or in the same window/tab (false) for this post. Example: true.
- `pinned` (`boolean`, optional): Whether this post should be pinned to the top of the feed. (Only available on the Starter plan (and up)). Example: true.
- `publish` (`boolean`, optional): Whether to publish this post or save it as a draft. Example: true.
- `send_push_notification` (`boolean`, optional): Enable this to send a web push notification for this post to all your subscribed users. (Only available on the Pro plan (and up)). Example: true.
- `show_in_standalone` (`boolean`, optional): Whether this post should show up in the standalone feed . Example: true.
- `show_in_widget` (`boolean`, optional): Whether this post should show up in the embedded feed . Example: true.
- `user_email` (`string`, optional): Email of the user in your account creating this post. Example: jane@example.com.

Example input: `{"category":"<category>","content":["<p>You can now switch to dark mode from Settings.</p>"],"title":["Dark mode is here"]}`

### `beamer_post_reaction_create`

Create Post Reaction · Write

Record an end user's reaction (positive, neutral or negative) to a changelog post.
Returns the created reaction.
Identify the end user with user_id, user_email, user_firstname or user_lastname.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `post_id` (`integer`, required): ID of the post, from beamer_posts_list. Example: 1234567.
- `reaction` (`string`, required): Reaction type: positive, neutral or negative. Example: positive.
- `user_email` (`string`, optional): Email of the end user who created this reaction. Example: jane@example.com.
- `user_firstname` (`string`, optional): First name of the end user who created this reaction. Example: Jane.
- `user_id` (`string`, optional): ID of the end user who created this reaction. Example: user_123.
- `user_lastname` (`string`, optional): Last name of the end user who created this reaction. Example: Doe.

Example input: `{"post_id":1234567,"reaction":"<reaction>"}`

### `beamer_post_update`

Update Post · Write

Update an existing changelog post's translations, category, publish state, dates or segmentation.
Returns the updated post.
Only the fields you set are sent. Per-translation arrays follow the same order rules as beamer_post_create.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `post_id` (`integer`, required): ID of the post, from beamer_posts_list. Example: 1234567.
- `archive` (`boolean`, optional): Whether to archive this post or not. Example: true.
- `auto_open` (`boolean`, optional): Enable this to automatically open Beamer's sidebar the first time the user gets this post (Only available on the Starter plan (and up)) Deprecated. Example: true.
- `boosted_announcement` (`string`, optional): Type of boosted announcement to set for this post. (Only available with the Boosted Announcements add-on). Example: snippet. One of: `top-bar`, `popup`, `snippet`, `tooltip`.
- `category` (`string`, optional): Post category: new, improvement, fix, comingsoon, announcement or other (custom categories on paid plans). Separate several with semicolons. Example: new.
- `content` (`array`, optional): Post body (HTML allowed), as an array with one entry per translation. Array with one entry per translation, in the same order as the other per-translation arrays (title, content, language, link_url, link_text). Example: ["You can now switch to dark mode from Settings.
"]
- `date` (`string`, optional): Publication date for this post in ISO-8601 format. [Future dates / post scheduling are only available on the Starter plan (and up)]. Example: 2026-02-01T09:00:00Z.
- `due_date` (`string`, optional): Expiration date for this post in ISO-8601 format. (Only available on the Starter plan (and up)). Example: 2026-03-01T00:00:00Z.
- `enable_feedback` (`boolean`, optional): Whether to enable or disable user feedback for this post (Only available on the Pro plan (and up)). Example: true.
- `enable_reactions` (`boolean`, optional): Whether to enable or disable user reactions for this post (Only available on the Pro plan (and up)). Example: true.
- `enable_social_share` (`boolean`, optional): Enable this to show options for your users to share this post on social media . Example: true.
- `filter` (`string`, optional): Segmentation filter (or filters) for this post. (Only available on the Pro plan (and up)). Example: beta;admin.
- `filter_url` (`string`, optional): URL where the post is shown; * is a wildcard and several URLs are separated by semicolons (Pro plan and up). Example: https://app.example.com/dashboard.
- `filter_user_id` (`string`, optional): User ID to apply as a filter. This post will only be shown to users that have the same ' user_id ' parameter in the embedded script. Multiple IDs can be passed in, separated by semicolons (;). (Only available on the Scale plan). Example: user_123;user_456.
- `fixed_boosted_announcement` (`boolean`, optional): Enable this for the post to be shown as a fixed top-bar announcement. Example: true.
- `language` (`array`, optional): ISO-639 two-letter language of each translation, for example ["en", "es"]. Array with one entry per translation, in the same order as the other per-translation arrays (title, content, language, link_url, link_text) (Starter plan and up). Example: ["en"]
- `link_text` (`array`, optional): Call-to-action link text per translation. Array with one entry per translation, in the same order as the other per-translation arrays (title, content, language, link_url, link_text). Example: ["Read more"]
- `link_url` (`array`, optional): Call-to-action URL per translation, opened when the header or bottom link is clicked. Array with one entry per translation, in the same order as the other per-translation arrays (title, content, language, link_url, link_text). Example: ["https://example.com/blog/dark-mode"]
- `links_in_new_window` (`boolean`, optional): Whether to open links in a new window/tab (true) or in the same window/tab (false) for this post. Example: true.
- `pinned` (`boolean`, optional): Whether this post should be pinned to the top of the feed. (Only available on the Starter plan (and up)). Example: true.
- `publish` (`boolean`, optional): Whether to publish this post or save it as a draft. Example: true.
- `send_push_notification` (`boolean`, optional): Enable this to send a web push notification for this post to all your subscribed users. (Only available on the Pro plan (and up)). Example: true.
- `show_in_standalone` (`boolean`, optional): Whether this post should show up in the standalone feed . Example: true.
- `show_in_widget` (`boolean`, optional): Whether this post should show up in the embedded feed . Example: true.
- `title` (`array`, optional): Post title, as an array with one entry per translation, for example ["Dark mode is here"]. Array with one entry per translation, in the same order as the other per-translation arrays (title, content, language, link_url, link_text). Example: ["Dark mode is here"]
- `user_email` (`string`, optional): Email of the user in your account creating this post. Example: jane@example.com.

Example input: `{"post_id":1234567}`

### `beamer_team_member_invite`

Invite Team Member · Write

Invite someone to your Beamer team with a role.
Returns the invited team member.
Roles: admin, manager, writer, designer, reader or billing.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `email` (`string`, required): Email address of the person to invite. Example: teammate@example.com.
- `role` (`string`, required): Role to give: admin, manager, writer, designer, reader or billing. Example: writer. One of: `admin`, `manager`, `writer`, `designer`, `reader`, `billing`.

Example input: `{"email":"<email>","role":"admin"}`

### `beamer_team_member_role_update`

Update Team Member Role · Write

Change the role of a member of your Beamer team.
Returns the updated team member.
Roles: admin, manager, writer, designer, reader or billing.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `email` (`string`, required): Email address of the team member. Example: teammate@example.com.
- `role` (`string`, required): New role: admin, manager, writer, designer, reader or billing. Example: writer. One of: `admin`, `manager`, `writer`, `designer`, `reader`, `billing`.

Example input: `{"email":"<email>","role":"admin"}`

### `beamer_unread_posts_list`

List Unread Posts · Write

List the changelog posts one end user has not read yet, and by default mark them as read.
Returns the unread posts with their translations and links.
Identify the user with user_id or user_email. Set mark_as_read=false to only peek. Use beamer_unread_posts_count for a badge count.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `category` (`string`, optional): Retrieve posts with this category. Example: new.
- `date_from` (`string`, optional): Retrieve posts published after this date. The date must follow the ISO-8601 format. Example: 2026-01-01T00:00:00Z.
- `filter` (`string`, optional): Retrieve posts with a matching segmentation filter. (Only available on the Pro plan (and up)). Example: beta;admin.
- `filter_url` (`string`, optional): If URL segmentation is enabled, include posts with a matching segmentation URL. (Only available on the Pro plan (and up)). Example: https://app.example.com/dashboard.
- `force_filter` (`string`, optional): Only retrieve posts that match this segmentation filter. (Only available on the Pro plan (and up)). Example: beta.
- `ignore_filters` (`boolean`, optional): If true, all posts will be retrieved, ignoring any segmentation they may have. This parameter should only be used for requests sent from the backend. [In order to user this parameter, the API key should have the 'Read posts (ignore filters)' permission enabled.]. Example: true.
- `ignore_request_details` (`boolean`, optional): Whether request-specific details should be ignored (this includes IP, browser/OS and geolocation details). Useful when sending requests from your backend, where the request's details aren't representative of the end user. Example: true.
- `language` (`string`, optional): Retrieve posts with translations in this language. The language must follow the ISO-639 two-letter code format. (Only available on the Starter plan (and up)). Example: en.
- `mark_as_read` (`boolean`, optional): Whether to mark the posts retrieved as 'read' for the specified user. By default, posts are marked as read and not retrieved again in subsequent calls. Example: true.
- `max_results` (`integer`, optional): Maximum number of items to return per page (Beamer returns at most 10). Example: 10.
- `page` (`integer`, optional): Page number to return, combined with max_results, starting at 1. Example: 1.
- `save_views` (`boolean`, optional): Whether to save views for the posts retrieved (for Analytics). If unspecified, views are saved. Example: true.
- `traceable_links` (`boolean`, optional): Whether links in the post should be converted to a traceable format (both the CTA and links within the content). If true, the opened URL will be tracked and record a 'click' entry in your Analytics. Example: true.
- `user_email` (`string`, optional): Email of the user viewing these posts (for Analytics). Example: jane@example.com.
- `user_first_name` (`string`, optional): First name of the user viewing these posts (for Analytics). Example: Jane.
- `user_id` (`string`, optional): ID of the user viewing these posts (for Analytics). If single-user posts are enabled, posts with a matching userId will be retrieved. (Only available on the Scale plan) If multi-device synchronization is enabled, the dateFrom parameter will be overridden by this user's last date of viewing your feed - if any. dateFrom can be omitted in this case. (Only available on the Pro plan (and up)). Example: user_123.
- `user_last_name` (`string`, optional): Last name of the user viewing these posts (for Analytics). Example: Doe.

Example input: `{}`

### `beamer_user_create`

Create User · Write

Create an end user in Beamer Analytics so posts and NPS can be targeted to them.
Returns the created user.
user_id and user_email are required.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `user_email` (`string`, required): Email for this user. Example: jane@example.com.
- `user_id` (`string`, required): Unique identifier for this user. Example: user_123.
- `browser` (`string`, optional): Browser from where this user accessed. Example: Chrome.
- `city` (`string`, optional): City from where this user accessed. Example: Lisbon.
- `country` (`string`, optional): Country from where this user accessed. Example: PT.
- `filter` (`string`, optional): Segmentation filter(s) for this user, separated by semicolons. Example: beta;admin.
- `ip` (`string`, optional): IP from where this user accessed. Example: 203.0.113.7.
- `language` (`string`, optional): Language for this user. The language must follow the ISO-639 two-letter code format. Example: ["en"]
- `latitude` (`string`, optional): Latitude from where this user accessed. Example: 38.7223.
- `longitude` (`string`, optional): Longitude from where this user accessed. Example: -9.1393.
- `os` (`string`, optional): Operating system from where this user accessed. Example: macOS.
- `user_first_name` (`string`, optional): First name for this user. Example: Jane.
- `user_last_name` (`string`, optional): Last name for this user. Example: Doe.

Example input: `{"user_email":"<user_email>","user_id":"<user_id>"}`

### `beamer_users_update`

Update Users · Write

Update the Beamer Analytics users that match a user ID, Beamer ID or email.
Returns the updated users.
Set match_user_id, match_beamer_id or match_user_email to choose the users; the other fields are the new values.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `browser` (`string`, optional): Browser from where this user accessed. Example: Chrome.
- `city` (`string`, optional): City from where this user accessed. Example: Lisbon.
- `country` (`string`, optional): Country from where this user accessed. Example: PT.
- `filter` (`string`, optional): Segmentation filter(s) for this user, separated by semicolons. Example: beta;admin.
- `ip` (`string`, optional): IP from where this user accessed. Example: 203.0.113.7.
- `language` (`string`, optional): Language for this user. The language must follow the ISO-639 two-letter code format. Example: ["en"]
- `latitude` (`string`, optional): Latitude from where this user accessed. Example: 38.7223.
- `longitude` (`string`, optional): Longitude from where this user accessed. Example: -9.1393.
- `match_beamer_id` (`string`, optional): Update the user with this Beamer-generated ID. Example: 84391274.
- `match_user_email` (`string`, optional): Update the users with this email. Example: jane@example.com.
- `match_user_id` (`string`, optional): Update the users with this user ID. Example: user_123.
- `os` (`string`, optional): Operating system from where this user accessed. Example: macOS.
- `user_email` (`string`, optional): New email. Example: jane@example.com.
- `user_first_name` (`string`, optional): First name for this user. Example: Jane.
- `user_id` (`string`, optional): New user ID. Example: user_123.
- `user_last_name` (`string`, optional): Last name for this user. Example: Doe.

Example input: `{}`

### `beamer_feature_request_comment_delete`

Delete Feature Request Comment · Destructive

Delete a comment from a feature request.
Returns an empty success response.
This cannot be undone.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `comment_id` (`integer`, required): ID of the comment, from the matching comments list tool. Example: 7654321.
- `feature_request_id` (`integer`, required): ID of the feature request, from beamer_feature_requests_list. Example: 98765.

Example input: `{"comment_id":7654321,"feature_request_id":98765}`

### `beamer_feature_request_delete`

Delete Feature Request · Destructive

Delete a feature request with its votes and comments.
Returns an empty success response.
This cannot be undone.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `feature_request_id` (`integer`, required): ID of the feature request, from beamer_feature_requests_list. Example: 98765.

Example input: `{"feature_request_id":98765}`

### `beamer_feature_request_vote_delete`

Delete Feature Request Vote · Destructive

Remove a vote from a feature request.
Returns an empty success response.
This cannot be undone.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `feature_request_id` (`integer`, required): ID of the feature request, from beamer_feature_requests_list. Example: 98765.
- `vote_id` (`integer`, required): ID of the vote, from beamer_feature_request_votes_list. Example: 112233.

Example input: `{"feature_request_id":98765,"vote_id":112233}`

### `beamer_post_comment_delete`

Delete Post Comment · Destructive

Delete a comment from a changelog post.
Returns an empty success response.
This cannot be undone.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `comment_id` (`integer`, required): ID of the comment, from the matching comments list tool. Example: 7654321.
- `post_id` (`integer`, required): ID of the post, from beamer_posts_list. Example: 1234567.

Example input: `{"comment_id":7654321,"post_id":1234567}`

### `beamer_post_delete`

Delete Post · Destructive

Delete a changelog post with its comments and reactions.
Returns an empty success response.
This cannot be undone; to hide a post instead, set archive=true with beamer_post_update.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `post_id` (`integer`, required): ID of the post, from beamer_posts_list. Example: 1234567.

Example input: `{"post_id":1234567}`

### `beamer_post_reaction_delete`

Delete Post Reaction · Destructive

Delete a reaction from a changelog post.
Returns an empty success response.
This cannot be undone.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `post_id` (`integer`, required): ID of the post, from beamer_posts_list. Example: 1234567.
- `reaction_id` (`integer`, required): ID of the reaction, from beamer_post_reactions_list. Example: 456789.

Example input: `{"post_id":1234567,"reaction_id":456789}`

### `beamer_privacy_user_data_delete`

Delete User Data (Privacy) · Destructive

Permanently delete all data Beamer holds about an end user, for privacy requests such as GDPR erasure.
Returns a confirmation.
Identify the user with user_id, beamer_id or user_email. This cannot be undone.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `beamer_id` (`string`, optional): Beamer generated ID of the user to delete. Multiple IDs can be passed in, separated by semicolons (;). Example: 84391274.
- `user_email` (`string`, optional): Email of the user to delete. Multiple emails can be passed in, separated by semicolons (;). Example: jane@example.com.
- `user_id` (`string`, optional): ID of the user to delete (as defined in the embedded script's user_id parameter). Example: user_123.

Example input: `{}`

### `beamer_team_member_remove`

Remove Team Member · Destructive

Remove a member from your Beamer team.
Returns a confirmation.
They lose access to the Beamer dashboard.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `email` (`string`, required): Email address of the team member to remove. Example: teammate@example.com.

Example input: `{"email":"<email>"}`

### `beamer_users_delete`

Delete Users · Destructive

Permanently delete the Beamer Analytics users that match a user ID, Beamer ID or email.
Returns a confirmation.
At least one identifier is required. This cannot be undone.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `beamer_id` (`string`, optional): Beamer generated ID of the user to delete. Multiple IDs can be passed in, separated by semicolons (;). Example: 84391274.
- `user_email` (`string`, optional): Email of the user to delete. Multiple emails can be passed in, separated by semicolons (;). Example: jane@example.com.
- `user_id` (`string`, optional): ID of the user to delete (as defined in the embedded script's user_id parameter). Multiple IDs can be passed in, separated by semicolons (;). Example: user_123.

Example input: `{}`

## Related

Other Marketing connectors ([all 190](/agentkit/connectors/?category=marketing)):

- [HubSpot](/agentkit/connectors/hubspot/): Scalekit connector, OAuth, 457 tools
- [Mailchimp](/agentkit/connectors/mailchimp/): Scalekit connector, OAuth, 73 tools
- [Twitter / X](/agentkit/connectors/twitteroauth/): Scalekit connector, OAuth, 92 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
