Resources · Make integration

Bluedot Make integrationAutomate Bluedot with Make.

Every new Bluedot summary or transcript can start a Make scenario. This Bluedot Make integration gives you 2 scheduled triggers and no actions. The page shows how to link your account, build a first scenario and test it before you switch it on.

Try the Bluedot integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Bluedot Make integration let you automate?

The Bluedot Make integration links your Bluedot account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that each do one job. Bluedot only opens that chain here. Its two modules watch for new summaries and new transcripts, and the next module, taken from another app, decides where they go.

Brief a manager with each new summary. Put Watch summary created first, then add an email or messaging module from another app. The person who needs the short version gets it without logging into Bluedot.

Keep every transcript in one archive. Watch transcript created hands each new transcript to Make as a bundle, one item passed from a module to the next. A document or storage module can then file it where a legal or support team already looks.

Log new items in a follow-up sheet. Start from either trigger and add a spreadsheet or CRM module, so a sales team gets one row per new summary or transcript. The Make training walks through that mapping step if it is new to you.

What Make does not do here: Bluedot has no action module, no search module and no Make an API Call module, so a scenario cannot write anything back to Bluedot. The Make documentation for this app is also limited, and the trigger types are inferred from the module names. Apps in Make often have an n8n node as well; the n8n vs Make page puts the two tools side by side, and Make pricing covers the plans.

Connect

How do you connect Bluedot to Make?

  1. 01

    Add a Bluedot module

    Open your scenario, click the + and search for Bluedot. Pick Watch summary created or Watch transcript created, then click Create a connection. A connection is your Bluedot account linked to Make once, and both modules reuse it.

  2. 02

    Name the connection

    The name is optional. It pays off when several Bluedot accounts sit in the same Make organization: a label with the team or the account owner makes the right one easy to pick in the next scenario.

  3. 03

    Authorize and save

    Make then asks for access to Bluedot, either through an authorization page from Bluedot or with a key that Bluedot gives you. The documentation does not say which of the two applies. Complete that step, then click Save.

First scenario

Your first scenario with Bluedot

GoalWhen a new summary is created in Bluedot, Make passes it to a module of another app.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the + in the middle of the editor. That empty circle becomes the first module of the chain.

  2. 02

    Pick the Bluedot trigger

    Search for Bluedot, choose Watch summary created and select the connection you made earlier, or click Create a connection if none exists yet.

  3. 03

    Fill in the fields

    Fill in the fields the module shows. Once the connection works, Make lists what it can read from your account, so you choose from a list instead of typing values by hand.

  4. 04

    Add the next module

    Click the + on the right of the Bluedot module and add a module from the app that should receive the summary. Map the data from the Bluedot module into its fields.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, so you can check the summary data before anything goes live.

  6. 06

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Then switch the scenario on.

Triggers

What starts a Bluedot scenario?

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

Bluedot1Watch summary created

Watch summary created

triggerIn the docs only

You get a scenario that starts from each new summary Make finds when it checks Bluedot, so the rest of the chain can send or store it without any copy and paste. Each new summary reaches Make as one bundle for the next module.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, rather than waiting for Bluedot to call it.
When to use it
pick it when the short version matters more than the full text, for example to brief a manager who will not read everything.
Watch out
the documentation gives no description of this module and its type is inferred from its name, so look for the clock badge on it in the editor.
Bluedot2Watch transcript created

Watch transcript created

triggerIn the docs only

Full transcripts land in your scenario through this module: one new transcript, one bundle, ready for the next app in the chain to file or process.

How it fires
scheduled. Make checks the app on the scenario's schedule, not at the moment Bluedot creates the transcript.
When to use it
choose it over the summary trigger when the next app needs the complete text, such as an archive a support team searches later.
Watch out
every module that runs on a bundle counts as one operation, the unit Make tracks on your plan, so each transcript uses operations in every module it passes through.
Need help

Need help automating Bluedot with Make?

A person reads every message.

FAQ

Bluedot and Make: common questions

01Is the Bluedot Make integration free?
Yes. Bluedot is a standard app in Make, so its two triggers work on the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to one minute and lift the cap on active scenarios. Make counts usage in operations, one per module run on one bundle. Your Bluedot subscription is a separate matter, and this page gives no price for it.
02What do you need to connect Bluedot to Make?
A Bluedot account and a Make account. The Make documentation lists no prerequisite for this app and no official connection steps, so the generic flow applies: add a Bluedot module, click Create a connection, name it if you like, authorize Make on the Bluedot page or paste the key Bluedot provides, then click Save. You create the connection once and both triggers reuse it. Since the documentation for Bluedot is limited, note the exact message Make shows if a step does not match what you see.
03Does the Bluedot trigger fire in real time?
No. Both Bluedot triggers are listed as scheduled, which means Make checks the app on the scenario's schedule instead of receiving a webhook call from Bluedot. A new scenario checks every 15 minutes by default. On the Free plan that is also the shortest interval, while paid plans go down to one minute. The type is inferred from the module names, because the documentation describes neither module. The badge in the editor settles it: a clock means scheduled, a lightning bolt would mean instant.
04What if a Bluedot module is missing in Make?
It depends on what you need. Bluedot offers only two triggers in Make, one for new summaries and one for new transcripts, with no action, no search and no Make an API Call module. A scenario can read from Bluedot but cannot create or change anything there. For every later step, use another app in Make that has the module you need. If the gap blocks a whole process, the team can look at it with you through the help form on this page.
05Is Make or n8n better for Bluedot?
It depends on what each tool offers for Bluedot and on the one your team already runs. On the Make side, Bluedot brings two scheduled triggers, one for summaries and one for transcripts, and every other step comes from another app. Apps in Make often have an n8n node too, so check whether Bluedot has one and what it exposes before you choose. This page does not rank the two tools or compare their prices. The n8n vs Make comparison on this site goes through the differences if you are still deciding.
Same platform

Other docs you might need on this stack.

Browse all integrations