Resources · Make integration

Bellbird Make integrationAutomate Bellbird with Make.

Need a meeting link ready each time something happens in another tool? The Bellbird Make integration gives you 2 action modules and no trigger. This guide is for teams who book calls often: it shows how to connect Bellbird, build a first scenario and test it safely.

Try the Bellbird integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Bellbird Make integration do?

The Bellbird Make integration lets Make act on your Bellbird account for you. You build a scenario, the automation you assemble in Make as a chain of modules, and Bellbird becomes one of its steps. Each module is a single brick: here, both Bellbird bricks are actions, so something else has to start the scenario.

A link ready when a lead signs up. Put a form or CRM trigger from another app first, then add Create Meeting Link. Every new entry becomes a bundle (one item passing from module to module), and Bellbird produces a link you can map into the following module, such as an email or a chat message. Browsing a form app like the 123FormBuilder Make integration gives you an idea of what can sit upstream.

Calls that go beyond the listed modules. Make an API Call reuses your Bellbird connection to reach any endpoint of the Bellbird API. It is the way out when Create Meeting Link does not cover what you need.

A scheduled run with no outside trigger. Since Bellbird has no trigger of its own, you can also start the scenario from Make's clock, which runs a new scenario every 15 minutes by default.

Know the limits before you start. Make's own documentation says it cannot fully document Bellbird yet because too little public information exists about the app, so the fields you will see come from the module itself, not from a guide. The same app often has an n8n node too; the n8n vs Make comparison lays out how the two tools differ, and our Make review covers the editor in depth.

Connect

How do you connect Bellbird to Make?

  1. 01

    Open the connection window

    Add any Bellbird module to your scenario, then click Create a connection. A connection is your Bellbird account linked to Make once, and every Bellbird module in your scenarios reuses it afterward.

  2. 02

    Name it if you like

    Giving the connection a name is optional, but it helps later when you juggle several accounts or a test workspace next to the real one. Pick something that tells you which Bellbird account sits behind it.

  3. 03

    Authorize and save

    Depending on what Bellbird asks for, either approve Make on the Bellbird page that opens, or paste the key Bellbird gives you into the field. Then click Save and the module is ready to fill.

First scenario

Your first scenario with Bellbird

GoalWhen a new request arrives in another app, Make creates a Bellbird meeting link and passes it on.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. This first module is the app where requests land, for example your form tool.

  2. 02

    Add Create Meeting Link

    Click the + on the right of that first module, search for Bellbird and pick Create Meeting Link. Select your connection or create it now with Create a connection.

  3. 03

    Map the incoming data

    Fill the module fields, dragging values from the first module into them where they fit. Make shows what it can read from Bellbird once the connection exists, so you do not type anything blind.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open each module's bubble to read the bundles it received and check that Bellbird returned the link you expected.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default, and never shorter than that on the Free plan), then switch the scenario on so it runs without you.

Modules

What the Bellbird modules do

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

Bellbird2

Make an API Call

ActionIn the docs only

This one lets you reach any endpoint of the Bellbird API from your scenario, using the connection you already created, which covers actions the listed module does not offer.

When to use it
when Create Meeting Link is not enough and you know which Bellbird endpoint does the job you need.
Watch out
you write the request yourself, so keep Bellbird's API reference open; Make's documentation cannot help much, as it describes the app as poorly documented.
Need help

Need help automating Bellbird with Make?

A person reads every message.

FAQ

Bellbird and Make: common questions

01Is the Bellbird Make integration free?
Yes, Bellbird is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Make counts each module run as an operation, and usage is billed in credits per month. Bellbird's own pricing is outside the scope of this page.
02What does the Bellbird Make integration need to connect?
A Bellbird account and a Make account. Make's documentation lists no prerequisites and no specific connection steps for Bellbird, so the standard flow applies: add a Bellbird module, click Create a connection, optionally name it, authorize Make on the Bellbird page or paste the key Bellbird provides, then click Save. The connection is stored once and reused by both Bellbird modules in any scenario you build afterward. Before you switch anything on, give it a quick test with Run once.
03Does the Bellbird Make integration react in real time?
No, because Bellbird has no trigger module in Make. The scenario has to start somewhere else. Either place a trigger from another app first, and the Bellbird action runs whenever that trigger fires, or let Make's own schedule start the scenario, which is every 15 minutes by default on a new scenario. How fast things happen depends on the trigger you choose, not on Bellbird. Run once lets you test it whenever you want.
04How do you cover a missing Bellbird module in Make?
Use Make an API Call. It sends a request to any endpoint of the Bellbird API with the connection you already set up, so you are not limited to Create Meeting Link. Be aware that Make describes its Bellbird documentation as limited because little public information about the app exists, which means you will rely on Bellbird's own API reference to build the request correctly. Test each request with Run once before relying on it.
05Is Make or n8n better for Bellbird?
It depends on the tool your team already works in. Make offers Bellbird as a native app with 2 modules, one of them a generic API call, and you build everything in a visual editor. The same app often has an n8n node as well. There is no general winner between the two for this app; compare the modules each side offers for Bellbird and pick the editor you are more comfortable maintaining.
Same platform

Other docs you might need on this stack.

Browse all integrations