Resources · Make integration

Beamer Make integrationAutomate Beamer with Make.

Could your changelog update itself when a feature ships? The Beamer Make integration gives you 7 modules to watch, create, edit and find posts. This guide is for product and marketing teams: connect your account, then build a first scenario that turns a release into a Beamer post.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Beamer Make integration do for your team?

The Beamer Make integration links your Beamer account to Make, a visual tool where you build a scenario: a chain of steps that runs on a schedule or when an app calls Make. Each step is a module, one brick from one app. With Beamer you get one trigger, five actions and one search, all about the posts in your changelog.

Publish release notes from where the work happens. A scenario can start in the tool your developers use to mark a feature as done, then call Create a Post so the announcement lands in Beamer with the title and text you mapped. Nobody has to copy and paste between tabs.

Spread every new post beyond the widget. Watch Posts picks up each new post, and the next module can forward it to a newsletter tool, a chat channel or a spreadsheet that tracks what you shipped. Support hears about the change at the next check, without waiting for someone to pass it on.

Keep old announcements tidy. Search Posts finds the posts that match what you look for, Update a Post corrects them and Delete a Post removes the ones that no longer apply. Be careful with the last one: a deleted post does not come back.

Where the listed modules stop, Make an API Call reaches any endpoint of the Beamer API with the same connection. Want a second opinion on the platform first? Read our Make review, compare plans on Make pricing, or weigh the alternative in n8n vs Make.

Connect

How do you connect Beamer to Make?

  1. 01

    Copy your Beamer API key

    In Beamer, open Settings, click API and copy the key shown on screen. You need an active Beamer account for this; the key is what lets Make act on your posts, so keep it private.

  2. 02

    Open a Beamer module in Make

    Log in to Make, add any Beamer module to your scenario and click Create a connection. A connection is your Beamer account linked to Make once, then reused by every Beamer module you add.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you manage several Beamer accounts. Paste the API key you copied, or follow the on-screen instructions, and save. Make can now read your posts.

First scenario

Your first scenario: turn a release into a Beamer post

GoalWhen a feature is marked as released in the tool your team already uses, Make creates the matching post in Beamer.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. This first module is the trigger: the event that starts everything.

  2. 02

    Pick the release event

    Search the app where releases are tracked and choose its module for a finished item. Connect that account the same way you connected Beamer, then fill its fields from the lists Make shows you.

  3. 03

    Add Create a Post

    Click the + on the right of the first module, search Beamer and pick Create a Post. Map the release name into the title and its description into the post body.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Each module shows the bundles it received, meaning the items passed along, so you can check the draft post before your users see it.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and the Free plan cannot go faster. Save, then flip the scenario on.

Triggers

What starts a Beamer scenario

1 module starts a scenario when something happens in Beamer. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Beamer as soon as it happens.

Beamer1Watch Posts

Watch Posts

Scheduled trigger

In MakeTriggers when a new post is created.

Watch Posts notices every new post created in your Beamer account and hands it to the next module, so an announcement can travel further without anyone forwarding it by hand. Each post arrives as its own bundle.

How it fires
it is a scheduled trigger, marked with a clock badge. Make checks Beamer on the scenario's schedule, every 15 minutes by default, and picks up the posts that are new since then.
When to use it
when the product team writes in Beamer and support, sales or a newsletter tool should hear about each release too.
Watch out
avoid Create a Post after it in the same scenario: logically, the post it creates would count as new at the next check.
Modules

Everything Beamer can do in a scenario

Beamer gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Beamer1

Create a Post

Action

In MakeCreates a new post. Multiple translations are only available on the Startup plan (and up).

Create a Post publishes a fresh announcement in your Beamer changelog using data mapped from earlier modules, so release notes write themselves from the ticket or form where the details already live.

When to use it
right after the step that marks a feature as shipped in your project tool.
Watch out
posts in several translations need the Beamer Startup plan or a higher one.
Beamer2

Delete a Post

Action

In MakeDeletes an existing post.

With Delete a Post, an announcement disappears from Beamer as soon as the scenario reaches this step, which keeps your widget free of features you rolled back or offers that ended.

When to use it
when a rollback or a cancelled launch is recorded somewhere Make can watch.
Watch out
the deletion cannot be undone, so run a test on a throwaway post first.
Beamer3

Get a Post

Action

In MakeRetrieves an existing post by its ID.

Get a Post brings back one existing post from its ID, giving later modules its full content to reuse, quote or check before they act on it.

When to use it
when an earlier step already holds the post ID, for example a row in a sheet that logs each announcement.
Watch out
it needs the exact ID; if you only know a keyword, start with Search Posts instead.
Beamer4

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Make an API Call lets you reach any endpoint of the Beamer API from your scenario, reusing the connection you already set up, so a missing module does not block you.

When to use it
when the five actions and the search above do not cover the task you have in mind.
Watch out
you write the request yourself, so keep the Beamer API documentation open while you fill it in.
Beamer5

Update a Post

Action

In MakeUpdates an existing post by its ID.

Update a Post rewrites an existing announcement identified by its ID, so a correction made in your source tool also reaches the version your users read in Beamer.

When to use it
when a release date moves or a feature name changes after the post went live.
Watch out
pair it with Search Posts or Get a Post, because without the right ID it has nothing to edit.
Beamer6

Search Posts

Search

In MakeSearches posts.

Search Posts finds the Beamer posts that match your criteria and returns zero, one or many results, each as its own bundle for the next module to process.

When to use it
before an update or a cleanup, to gather the posts concerned and read their IDs.
Watch out
several results mean the following module runs once per post, and every run counts as an operation on your plan.
Need help

Need help automating Beamer with Make?

A person reads every message.

FAQ

Questions people ask about Beamer and Make

01Is the Beamer Make integration free?
Yes. Beamer is a standard app, so it is available on the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Make counts usage in operations, one per module run on one bundle. Your Beamer subscription is billed separately by Beamer.
02What do you need to connect Beamer to Make?
An active Beamer account and its API key. In Beamer, go to Settings, then API, and copy the key displayed there. In Make, add any Beamer module, click Create a connection, optionally give the connection a name, and paste the key. That single connection then serves every Beamer module in all your scenarios, so you only do this once per Beamer account. Give it a clear name if you run more than one Beamer account.
03Does the Beamer Watch Posts trigger react instantly?
No. Watch Posts is a scheduled trigger, not an instant one. Make asks Beamer for new posts on the schedule set on the first module, every 15 minutes by default. On the Free plan the shortest gap is 15 minutes; paid plans can go down to 1 minute. A new post therefore reaches the scenario at the next check, not the second it goes live. Choose a shorter interval if support needs to hear about releases sooner.
04What if the Beamer module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Beamer API with the connection you already have, so you can cover actions that the listed modules do not offer. You write the request yourself, so keep the Beamer API documentation at hand. Note also that the Make documentation for Beamer is flagged as AI-generated from the official Beamer docs and may contain mistakes, so double-check anything important with Beamer directly before relying on it.
05Should you pick Make or n8n for Beamer?
It depends on the tool your team already uses. On Make, Beamer comes with 7 ready-made modules around posts, plus Make an API Call for the rest, all driven from a visual editor where you test with Run once. The same app often has an n8n node as well, so check the n8n catalog before deciding. Compare which one covers the post actions you need, which editor your team is comfortable with, and where your other automations already run.