Resources · Make integration

Bluebarry Make integrationAutomate Bluebarry with Make.

Can Make react when someone answers a question in Bluebarry? Yes: the Bluebarry Make integration offers 4 modules, 2 of them triggers. This page shows how to link your account, build a first scenario and pick the right module, with no code.

Try the Bluebarry integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Bluebarry Make integration do for you?

The Bluebarry Make integration links your Bluebarry account to Make so a scenario, the automation you build in Make, can start when a question gets answered or a result gets viewed, then pass that item to the rest of your tools. Each brick of that chain is called a module, and you set it up without writing code.

Hand answered questions to your team. Put Watch Answered Questions first: each new answer becomes a bundle, one item that flows to the next module, which you can map into another app your team already reads.

Follow who looks at results. Watch Viewed Results picks up viewed results at each scheduled check, a useful signal for a marketing follow-up handled in the tool of your choice.

Reach what the list does not cover. Make an API Call reuses your Bluebarry connection to call any endpoint of the Bluebarry API, and Get the Connection Metadata is there when a scenario needs details about the linked account.

Be aware of one limit: Make itself says its Bluebarry documentation is incomplete because little public information exists about the app. Test each module with Run once before you rely on it, and keep the Make troubleshooting guide nearby. Bluebarry may also have an n8n node; the n8n vs Make comparison explains how the two tools differ. To learn the editor step by step, see the Make training.

Connect

How do you connect Bluebarry to Make?

  1. 01

    Add a Bluebarry module

    In your scenario, click the + and search for Bluebarry, then pick any of its modules. The field for your account shows a button: click Create a connection. A connection is your Bluebarry account linked to Make once, then reused by every Bluebarry module.

  2. 02

    Name the connection

    Make offers a name field for the connection. This step is optional, but a clear name such as your workspace or client name helps later when several accounts sit side by side in the same Make organization.

  3. 03

    Authorize and save

    Depending on what Bluebarry supports, either approve Make on the Bluebarry page that opens, or paste the key Bluebarry gives you. Then click Save. The connection appears in the module and stays available for the next ones.

First scenario

Build your first scenario with Bluebarry

GoalWhen a question is answered in Bluebarry, Make picks it up and calls the Bluebarry API to fetch the extra data you need.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the large + in the middle of the editor. That empty circle is where your first module, the trigger, will sit.

  2. 02

    Add Watch Answered Questions

    Search for Bluebarry, choose Watch Answered Questions and select your connection, or click Create a connection if this is your first Bluebarry module. Fill the fields Make shows you.

  3. 03

    Add Make an API Call

    Click the + on the right of the trigger, pick Bluebarry again and choose Make an API Call. Map data from the answered question into the request so the call targets the right item.

  4. 04

    Test with Run once

    Answer a question in Bluebarry, then click Run once. Open the bubble above each module to read the bundles it received and check that the API call returned what you expected.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set how often Make checks Bluebarry; a new scenario runs every 15 minutes by default. Then switch the scenario on so it keeps running without you.

Triggers

Bluebarry triggers in Make

2 modules start a scenario when something happens in Bluebarry. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Bluebarry as soon as it happens.

Bluebarry1Watch Answered Questions

Watch Answered Questions

triggerIn the docs only

Your scenario gets every newly answered question as its own bundle, ready to be passed to the next module, so an answer no longer waits in Bluebarry until someone opens it.

How it fires
the Make documentation gives no type, but a Watch module name usually means a scheduled trigger: Make checks the app on the scenario's schedule, every 15 minutes by default on a new scenario, and never on its own in real time.
When to use it
pick it when the answer itself is the event that should start the work, for example routing it to the person who handles that topic.
Watch out
each module run on a bundle counts as one operation on your Make plan, so test with Run once before switching the scenario on.
Bluebarry2Watch Viewed Results

Watch Viewed Results

triggerIn the docs only

This trigger tells your scenario that a result has been viewed in Bluebarry, which gives you a clear moment to react instead of guessing who looked at what.

How it fires
its type is inferred from the name only, as a scheduled trigger: Make checks the app on the scenario's schedule, so a view shows up at the next check, not the second it happens.
When to use it
choose it over Watch Answered Questions when the signal you care about is attention to a result rather than a new answer, such as a follow-up after someone reads their outcome.
Watch out
Make's own Bluebarry documentation is incomplete, so read the first bundles in Run once before mapping fields further down the scenario.
Modules

Bluebarry modules in Make

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

Bluebarry1

Get the Connection Metadata

ActionIn the docs only

You get details about the Bluebarry account behind your connection, handy when a scenario must know which account it works with before it goes further.

When to use it
add it when several Bluebarry connections exist in your Make organization and you want the scenario to confirm which one it used.
Watch out
Make publishes no description of what this module returns, so run it once and read the bundle before mapping anything.
Bluebarry2

Make an API Call

ActionIn the docs only

This module lets your scenario call any endpoint of the Bluebarry API with the connection you already set up, so you are not limited to the three other modules.

When to use it
reach for it when a trigger gives you an item and you need data or an action the listed modules do not offer.
Watch out
you write the request yourself, so keep the Bluebarry API reference open and check the answer in Run once.
Need help

Need help automating Bluebarry with Make?

A person reads every message.

FAQ

Bluebarry Make integration: common questions

01Is the Bluebarry Make integration free?
Yes, Bluebarry is a standard app in Make, so it works on the Free plan. That plan has limits: 2 active scenarios, at least 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 (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations per month, one operation being one module run on one bundle. Any cost on the Bluebarry side is outside the scope of this page.
02What does it take to connect Bluebarry to Make?
A Bluebarry account and a Make account are enough. The Make documentation lists no other prerequisite and no Bluebarry-specific steps, so the generic flow applies: add a Bluebarry module, click Create a connection, optionally give it a name, then either approve Make on the Bluebarry page or paste the key Bluebarry provides, and click Save. The connection is created once and every Bluebarry module in your scenarios can reuse it afterwards. If the screen asks for something you do not recognize, look in your Bluebarry account settings.
03Do the Bluebarry triggers in Make fire in real time?
No, not as far as the documentation shows. Both Watch Answered Questions and Watch Viewed Results are treated as scheduled triggers, a type inferred from their names since Make gives none. A scheduled trigger means Make checks Bluebarry on the scenario's schedule, every 15 minutes by default, with 15 minutes as the floor on the Free plan and 1 minute on paid plans. An answer or a view is therefore picked up at the next check. If a delay matters for your use case, tighten the schedule on the first module.
04What if a Bluebarry module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Bluebarry API with the connection you already have, so it covers what the two triggers and Get the Connection Metadata do not. You build the request yourself, which means reading the Bluebarry API reference. Keep in mind that Make states its own Bluebarry documentation is limited because public information about the app is scarce, so test every call with Run once and inspect the bundle before wiring more modules after it.
05Make or n8n for Bluebarry: which one fits?
It depends on the tool you already work in. Bluebarry may have a node in n8n as well, so check both catalogs before you decide. On the Make side, this page can confirm 4 modules: 2 scheduled watch triggers, Get the Connection Metadata, and Make an API Call for everything else. There is no fair ranking to give between the two tools here, and no cost comparison either. Pick the one where your other apps and your team already live, then test the Bluebarry modules you need there.
Same platform

Other docs you might need on this stack.

Browse all integrations