Resources · Make integration

Mindspun Make integrationAutomate Mindspun with Make.

Can Make pick up what happens on your Mindspun site? The Mindspun Make integration offers 2 modules: one trigger that watches subscriptions and one API call. This guide shows site owners how to connect the account and run a first scenario.

Try the Mindspun integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Mindspun Make integration do?

The Mindspun Make integration links your Mindspun account to Make, a no-code tool where you build a scenario: the automation itself, made of modules placed one after the other. Here you get a trigger that looks for subscriptions and a module that calls the Mindspun API directly, so a new subscriber can set off the rest of your process.

React to a new subscriber. Watch Subscriptions starts the scenario whenever it finds subscriptions it has not seen yet. Each one travels through the scenario as a bundle, meaning one item passed from a module to the next, so the following modules can reuse its details.

Reach what the list does not cover. Make an API Call sends a request to any endpoint of the Mindspun API through the same connection. It is the way to do something the trigger does not offer, as long as the Mindspun API exposes it.

Feed your other tools. A subscription picked up in Mindspun can continue into a module of another app you already use in Make, such as your CRM or your team chat.

Be aware of the gaps. Make itself says its documentation for Mindspun is limited, because little public information exists about the app: no official description of the modules, no listed prerequisites. Test each module with Run once before relying on it. If you hesitate between tools, the n8n vs Make comparison lays out the criteria, the Make pricing page explains the plans, and the Make training helps you build more advanced scenarios.

Connect

How do you connect Mindspun to Make?

  1. 01

    Add a Mindspun module

    In a new scenario, click the +, type Mindspun in the search box and pick one of its two modules. Make then asks for a connection, which is your Mindspun account linked to Make once and reused by every Mindspun module.

  2. 02

    Create the connection

    Click Create a connection. You can give it a name if you manage several Mindspun sites, which makes each one easy to spot later in the list of connections.

  3. 03

    Authorize and save

    Depending on what Mindspun asks for, either approve access on the Mindspun page that opens or paste the key Mindspun gives you. Then click Save: the module can now read your account.

First scenario

Your first scenario with Mindspun

GoalWhen a new subscription appears in Mindspun, Make passes its details to a Mindspun API endpoint you choose.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the editor to place the first module.

  2. 02

    Add Watch Subscriptions

    Search for Mindspun, pick Watch Subscriptions and select the connection you just made, or create it here. Fill the fields Make shows for this module.

  3. 03

    Add the API call

    Click the + to the right of the trigger and pick Make an API Call. Enter the endpoint you need and map the subscription details coming from the trigger.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, which tells you what a Mindspun subscription really contains.

  5. 05

    Schedule and switch on

    Open the clock on the first module: a new scenario checks every 15 minutes by default. Keep that or change it within your plan, then switch the scenario on.

Triggers

What triggers a Mindspun scenario

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

Mindspun1Watch Subscriptions

Watch Subscriptions

triggerIn the docs only

With Watch Subscriptions, your scenario gets the Mindspun subscriptions it has not processed yet and hands each one to the next module as a bundle. The documentation gives no description of this module, so what it returns is best learned with a test.

How it fires
scheduled, Make checks the app on the scenario's schedule. This type comes from the module's name rather than from an official listing, so look for the clock badge when you add it.
When to use it
any scenario that should act when someone subscribes on your Mindspun site.
Watch out
on the Free plan, two checks are at least 15 minutes apart.
Modules

What the Mindspun modules can do

Mindspun gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Mindspun1

Make an API Call

ActionIn the docs only

Make an API Call gives you access to any endpoint of the Mindspun API from your scenario, using the connection you already created. It covers everything the trigger alone cannot do.

When to use it
you need an action in Mindspun that no dedicated module offers, for example acting on a subscription just found by the trigger.
Watch out
you pick the endpoint and the data yourself, so check what the Mindspun API offers and verify the answer with Run once.
Need help

Need help automating Mindspun with Make?

A person reads every message.

FAQ

Common questions about Mindspun and Make

01Is the Mindspun Make integration free?
Yes, Mindspun is a standard app in Make, so it works from the Free plan onward. 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 and remove the cap on active scenarios. Usage is counted in operations, one execution of one module on one bundle, so the more bundles your scenario processes, the more of your monthly allowance it uses.
02What do you need to connect Mindspun to Make?
A Mindspun account and a Make account are enough to start, since the documentation lists no other prerequisite. You add a Mindspun module, click Create a connection, then either approve access on the Mindspun page or paste the key Mindspun provides, depending on what your account offers. Once saved, the connection is reused by both modules. Because Make describes its Mindspun documentation as limited, keep your Mindspun admin access at hand in case the authorization needs a second attempt.
03Does the Mindspun Make trigger fire instantly?
No. Watch Subscriptions is a scheduled trigger: Make checks Mindspun on the scenario's schedule instead of being notified the moment a subscription happens. A new scenario checks every 15 minutes by default. On the Free plan you cannot go below 15 minutes, while paid plans allow checks as often as every minute. Note that this type is deduced from the module's name, as the official listing was not available, so confirm the clock badge on the module in the editor.
04What if the Mindspun module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Mindspun API through the same connection, so an action without its own module stays within reach as long as the API offers it. You choose the endpoint and the data, and Run once shows you what Mindspun sends back. Keep in mind that Make has little public information about Mindspun, so the official module documentation is thin; test each call with Run once before relying on it.
05Should you use Make or n8n for Mindspun?
It depends on where the rest of your automations already run. On Make, Mindspun comes with two modules: Watch Subscriptions and Make an API Call, which together cover new subscriptions and any other endpoint of the API. The same app often has a node in n8n too, so check that side before choosing. Neither tool is ranked here: compare the modules each one offers for Mindspun and pick the one your team already knows how to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations