Resources · Make integration

BurstyAI Make integrationAutomate BurstyAI with Make.

Can Make start your BurstyAI workflows and bring back what they produce? The BurstyAI Make integration gives you 4 modules: 3 actions and 1 search. This guide explains each one in plain words, then walks you through a first scenario you can test before switching it on.

Try the BurstyAI integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the BurstyAI Make integration let you automate?

The BurstyAI Make integration links your BurstyAI account to Make so a scenario (the automation you build in Make, a chain of modules) can launch a BurstyAI workflow, pick up its result and pass it on to your other tools. A module is one brick of that chain: here, an action or a search.

Launch a workflow without opening BurstyAI. Execute a Workflow starts one of your BurstyAI workflows from inside a scenario, so the run happens as part of a bigger process rather than by hand.

Hand the output to the rest of your stack. Chain Get Workflow Result right after it and the result becomes a bundle (one item passed from module to module) that the next app can store, send or file.

Keep an eye on what exists. List All Workflows returns every workflow of the account, handy to pick the right one or to keep an inventory in a spreadsheet.

Be aware of one real limit: Make itself says its documentation for BurstyAI is limited, because there is little public information about the app. There is no trigger either, so a scenario starts on Make's schedule or on another app's event. When the three named modules fall short, Make an API Call reaches the rest of the BurstyAI API with the same connection. The n8n vs Make comparison helps if you are still choosing a tool, and Make pricing explains how runs are counted.

Connect

How do you connect BurstyAI to Make?

  1. 01

    Add a BurstyAI module

    In a scenario, click the +, type BurstyAI in the search box and pick any of its modules. The module opens with a Create a connection button: the connection is your BurstyAI account linked to Make once, then reused by every BurstyAI module.

  2. 02

    Name it and authorize

    Give the connection a name if you like, which helps when a team shares several accounts. Then either approve access on the BurstyAI page that opens, or paste the key BurstyAI gives you, depending on what the connection window asks for.

  3. 03

    Save and check

    Click Save. The connection now appears in the module's dropdown, and Make can start reading your account, so the module fields can be filled with real values instead of typed guesses.

First scenario

Your first scenario with BurstyAI and Make

GoalWhen the scenario's schedule comes around, Make starts a BurstyAI workflow and then fetches its result.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the canvas. BurstyAI has no trigger, so the first module will be an action started by Make's clock.

  2. 02

    Add Execute a Workflow

    Search BurstyAI, choose Execute a Workflow and click Create a connection to link your account. Once linked, fill in the module fields; Make shows what it can read from your account.

  3. 03

    Chain Get Workflow Result

    Click the + on the right of the first module and add Get Workflow Result. Map the data it needs, most likely the run started by Execute a Workflow, from the bundle that module produced, instead of typing values by hand.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time; click the bubble above each module to read the bundles it received and check the result looks like what you expected.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, and the Free plan does not go below that. Pick the interval that fits, then switch the scenario on.

Modules

What the BurstyAI modules do

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

BurstyAI1

Execute a Workflow

ActionIn the docs only

This action starts one of your BurstyAI workflows from Make, so a workflow you usually launch by hand becomes one step of a scenario. It is the module most scenarios with this app are built around.

When to use it
a new lead lands in your CRM or a form is submitted, and you want BurstyAI to run on that input straight away.
Watch out
each run counts as an operation on your Make plan, so place it after a filter if only some bundles should reach it.
BurstyAI2

Get Workflow Result

ActionIn the docs only

As its name says, it brings back the result of a BurstyAI workflow into Make, where the following modules can use it. Without it, the output stays in BurstyAI and your scenario has nothing to pass along.

When to use it
right after Execute a Workflow, to send the output to a spreadsheet, an email or a shared folder.
Watch out
Make's documentation does not say how long a workflow takes, so test with Run once before trusting the chain.
BurstyAI3

List All Workflows

SearchIn the docs only

Judging by its name (Make gives no description), this search returns the workflows of your BurstyAI account, likely one bundle per workflow. It gives you a quick view of what you can run without switching tabs.

When to use it
to fill a sheet with your workflows, or to find the one a later module should start.
Watch out
a search can return zero, one or many bundles, and every module placed after it runs once per bundle, which multiplies operations.
BurstyAI4

Make an API Call

ActionIn the docs only

Your way out when the three named modules do not cover a need: it calls any endpoint of the BurstyAI API from the scenario, using the connection you already created, so there is no second login to manage.

When to use it
the action you need exists in the BurstyAI API but not as a ready module in Make.
Watch out
you write the request yourself, and Make says little public information exists on BurstyAI, so start from the API details your BurstyAI account gives you.
Need help

Need help automating BurstyAI with Make?

A person reads every message.

FAQ

BurstyAI and Make: common questions

01Is the BurstyAI Make integration free?
Yes, BurstyAI is a standard app in Make, so you can use it on the Free plan. That plan has limits worth knowing: 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 and remove the cap on active scenarios. Every module run counts as an operation against your plan. Your BurstyAI subscription is a separate matter and is not covered here.
02What do you need to connect BurstyAI to Make?
A BurstyAI account and a Make account. Make's documentation lists no specific prerequisite for BurstyAI and gives no official connection steps, so you follow Make's generic flow: add a BurstyAI module, click Create a connection, optionally name it, then authorize Make on the BurstyAI page or paste the key BurstyAI provides, and click Save. The same connection then serves all 4 BurstyAI modules, including Make an API Call, so you only set it up once per account.
03Can BurstyAI start a Make scenario in real time?
No, not with the modules Make offers today: BurstyAI has no trigger in Make, neither scheduled nor instant. You still have two ways to start. Put Execute a Workflow first and let Make's schedule run the scenario, every 15 minutes by default and down to 1 minute on paid plans. Or open the scenario with a trigger from another app, such as a form or a CRM, and place the BurstyAI modules after it, so the workflow runs each time that other app reports something new.
04What if the BurstyAI module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the BurstyAI API from your scenario with the connection you already have, so you are not limited to the three named modules. Keep in mind that Make says its own documentation for BurstyAI is limited because little public information exists about the app, which means you shape the request from whatever API details BurstyAI gives you. If that still does not work, another app in your scenario may handle the step instead.
05Should you use Make or n8n with BurstyAI?
It depends on the tool you already run, not on BurstyAI. On the Make side, the facts are 4 modules: Execute a Workflow, Get Workflow Result, List All Workflows and Make an API Call, with no trigger. Many apps also have an n8n node, so check whether one exists for BurstyAI and compare the operations it offers with this list, action by action. Pick the side that covers the steps your process actually needs; neither tool is ranked above the other here.
Same platform

Other docs you might need on this stack.

Browse all integrations