Resources · Make integration

KeaBuilder Make integrationAutomate KeaBuilder with Make.

Every checkout, form and new contact in KeaBuilder can start work on its own. The KeaBuilder Make integration gives you 13 modules: 7 triggers and 6 actions on contacts, tags and lists. This guide links your account and walks you through a first scenario.

Try the KeaBuilder integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the KeaBuilder Make integration do for you?

The KeaBuilder Make integration links your KeaBuilder account to Make, a no-code tool where you chain apps into a scenario (the automation you build). KeaBuilder events like a completed checkout or a submitted form start the scenario, and Make then tags, updates or moves the contact for you.

Buyers sorted the moment they pay. Watch Checkout Completed picks up each finished checkout, and Add Tag marks the buyer so your KeaBuilder emails and funnels treat customers differently from prospects. A coach selling a program gets clean segments without touching a spreadsheet.

Form leads routed to the right list. Watch Form Submitted hands each submission to Make, and Add to a List drops the person into the sequence that matches the form. An agency running several lead magnets keeps one list per offer.

Contacts kept current from other tools. Start a scenario in another app, then use Create Contact for someone new or Update Contact for someone KeaBuilder already knows. Remove Tag and Remove From a List clean up when a status changes.

Know the limits before you start. Make's documentation lists the 7 KeaBuilder triggers without a type; judging by their Watch names, all are scheduled and none is instant. There is no Make an API Call module for this app, so anything outside the 13 modules needs another route. Make also flags its KeaBuilder documentation as AI-generated and asks you to verify important points with KeaBuilder. If you are weighing tools, the n8n vs Make comparison lays out the criteria, the Make pricing page explains how operations are counted, and the Make training covers scenario building step by step.

Connect

How do you connect KeaBuilder to Make?

  1. 01

    Add a KeaBuilder module

    Log in to Make, open a scenario and add any KeaBuilder module. A connection is your KeaBuilder account linked to Make once and reused by every KeaBuilder module, so click Create a connection to set it up.

  2. 02

    Name the connection

    The Connection name field is optional. Filling it still helps: a name such as Main funnel account tells you at a glance which KeaBuilder account a scenario uses when you run more than one.

  3. 03

    Enter your credentials

    Paste the authentication credentials you copied from your KeaBuilder account, or follow the instructions Make shows on screen. Make's documentation points to the account login screen in KeaBuilder as the place to find them.

First scenario

Build your first scenario with KeaBuilder

GoalWhen someone submits a form in KeaBuilder, Make adds that person to the list you picked.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the big +. That empty circle becomes your first module, the brick that starts everything.

  2. 02

    Pick the form trigger

    Search for KeaBuilder, choose Watch Form Submitted and select your connection. Once it exists, Make lists the KeaBuilder items it can read, so fill the fields from those choices.

  3. 03

    Add the list action

    Click the + to the right of the trigger and add Add to a List. Choose the list, then map the data coming from the trigger into the fields Make asks for.

  4. 04

    Test with Run once

    Submit a test entry on your form, then click Run once. Open each module's bubble to read the bundle it received, meaning the single submission passed along, and confirm the person landed in the list.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set the schedule. A new scenario runs every 15 minutes by default, and 15 minutes is also the shortest gap on the Free plan. Then switch the scenario on.

Triggers

Which KeaBuilder events can start a scenario?

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

KeaBuilder1Watch Checkout Completed

Watch Checkout Completed

triggerIn the docs only

Turns each finished KeaBuilder checkout into a bundle in Make, so a sale can start your follow-up without anyone exporting orders by hand.

How it fires
scheduled. Make checks KeaBuilder on the scenario's schedule, every 15 minutes by default, rather than hearing about the checkout instantly.
When to use it
you sell a course through a KeaBuilder funnel and want every buyer tagged as a customer or moved to an onboarding list.
Watch out
each checkout is one bundle, and every module after the trigger spends one operation per bundle on your plan.
KeaBuilder2Watch Contact Created

Watch Contact Created

triggerIn the docs only

Catches every new person added to KeaBuilder and brings them into Make, giving you one place to react whenever your audience grows.

How it fires
scheduled. Make polls KeaBuilder on the scenario's schedule, so new contacts arrive in batches at each run instead of one by one.
When to use it
you want a welcome tag or a starter list applied to anyone who joins, whatever page they came through.
Watch out
contacts your own scenarios add with Create Contact are new contacts too, so they can come back through here; plan for it.
KeaBuilder3Watch Contacts Updated

Watch Contacts Updated

triggerIn the docs only

Reports KeaBuilder contacts whose details changed, which lets you mirror those edits in another app without checking records one at a time.

How it fires
scheduled. Make looks at KeaBuilder on the scenario's schedule and passes along the updated contacts it finds.
When to use it
your sales team edits contacts in KeaBuilder and you want a CRM or a sheet elsewhere to stay aligned.
Watch out
pairing it with Update Contact on the same account can make a scenario react to its own edits, so send the changes to another app instead.
KeaBuilder4Watch Form Submitted

Watch Form Submitted

triggerIn the docs only

Hands each KeaBuilder form submission to Make, so a lead from an opt-in or a quiz page gets processed without you copying entries around.

How it fires
scheduled. Make checks KeaBuilder for submissions on the scenario's schedule, every 15 minutes by default on a new scenario.
When to use it
you run several lead magnets and want each form's leads added to the list that matches the offer.
Watch out
test it with a real submission before Run once, otherwise the trigger has nothing to return and the test looks empty.
KeaBuilder5Watch List Subscribed

Watch List Subscribed

triggerIn the docs only

Tells Make who just joined a KeaBuilder list, giving you a clean signal that someone opted into a specific sequence or newsletter.

How it fires
scheduled. Make queries KeaBuilder on the scenario's schedule and returns the new subscriptions it finds at each run.
When to use it
joining a list means interest in one product, and you want that interest copied to a sales tool or a team channel.
Watch out
adding people to lists with Add to a List inside the same scenario would feed this trigger again, so keep those two in separate flows.
KeaBuilder6Watch Order Created

Watch Order Created

triggerIn the docs only

Brings each new KeaBuilder order into Make, so fulfillment, invoicing or a thank-you message can start from the order itself.

How it fires
scheduled. Make checks KeaBuilder on the scenario's schedule; on the Free plan the shortest gap between two checks is 15 minutes.
When to use it
you ship a physical product or grant access in another tool and need the order passed on without retyping it.
Watch out
choose between this and Watch Checkout Completed for a given flow, since running both on the same sale can process it twice.
KeaBuilder7Watch Tag Added

Watch Tag Added

triggerIn the docs only

Lets a tag in KeaBuilder act as a switch: the moment Make sees a tag applied to a contact, your scenario can take over from there.

How it fires
scheduled. Make reads KeaBuilder on the scenario's schedule and picks up the tags added since it last looked.
When to use it
your team tags a contact as qualified by hand, and that tag should alert sales or push the contact into another tool.
Watch out
never follow it with Add Tag on the same contact inside the same scenario, or the new tag can start the scenario again.
Modules

What can Make change in KeaBuilder?

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

KeaBuilder1

Add Tag

ActionIn the docs only

Marks a KeaBuilder contact with a tag from your scenario, so the segments and automations you built in KeaBuilder around that tag can use it.

When to use it
a payment, a call booked in another app or a finished checkout should label the contact as a customer.
Watch out
a scenario started by Watch Tag Added should not end with this module on the same contact, or it may loop.
KeaBuilder2

Add to a List

ActionIn the docs only

Puts a contact into a chosen KeaBuilder list, so whatever you tied to that list in KeaBuilder, such as a sequence, can apply to them without manual work.

When to use it
each form or offer has its own nurture list and every new lead needs to land in the right one.
Watch out
pick the list from the menu Make shows after the connection works, so a typo never sends people to the wrong sequence.
KeaBuilder3

Create Contact

ActionIn the docs only

Adds a brand new person to KeaBuilder from data that came from somewhere else, such as a webinar tool, a payment app or a spreadsheet row.

When to use it
leads are captured outside KeaBuilder and you want them in your KeaBuilder audience before any sequence starts.
Watch out
use Update Contact for people who already exist, and keep in mind that a new contact can wake up Watch Contact Created.
KeaBuilder4

Remove From a List

ActionIn the docs only

Takes a contact out of a KeaBuilder list, so people stop receiving a sequence that no longer fits where they are.

When to use it
a prospect buys, and the sales sequence aimed at prospects should stop the moment their order reaches Make.
Watch out
pair it with Add to a List when someone moves between sequences, one module to leave the old list and one to join the new.
KeaBuilder5

Remove Tag

ActionIn the docs only

Clears a tag from a KeaBuilder contact, keeping your segments honest when a status such as trial or unpaid is no longer true.

When to use it
a refund, a cancelled plan or a completed onboarding means a tag should come off without anyone editing the contact.
Watch out
whatever you built in KeaBuilder around that tag no longer matches the contact once the tag is gone.
KeaBuilder6

Update Contact

ActionIn the docs only

Changes the details of a contact KeaBuilder already has, so fresh information from your other tools lands on the right record.

When to use it
a CRM or a billing app holds newer details than KeaBuilder and you want both to agree after each change.
Watch out
starting from Watch Contacts Updated and ending here on the same account can make the scenario chase its own edits.
Need help

Need help automating KeaBuilder with Make?

A person reads every message.

FAQ

KeaBuilder and Make: common questions

01Is the KeaBuilder Make integration free?
Yes, KeaBuilder 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) bring the interval down to 1 minute and remove the cap on active scenarios. Usage is counted in operations, meaning one module handling one bundle. You still need your own KeaBuilder account, whose price is set by KeaBuilder.
02What do you need to connect KeaBuilder to Make?
You need a KeaBuilder account and a Make account. Make's documentation gives no specific API access requirement for KeaBuilder and sends you to the KeaBuilder pricing page for subscription details. To connect, add any KeaBuilder module, click Create a connection, optionally name it, then enter the authentication credentials copied from your KeaBuilder account or follow the on-screen steps. The documentation says those credentials come from the account login screen. Make labels this documentation as AI-generated, so confirm anything unclear with KeaBuilder.
03Do KeaBuilder triggers in Make fire in real time?
No. Make's documentation does not type the 7 KeaBuilder triggers, but their Watch names point to scheduled triggers, not instant ones. Make checks KeaBuilder on the scenario's schedule, which is every 15 minutes by default on a new scenario. On the Free plan 15 minutes is also the minimum interval, while paid plans can go down to 1 minute. Events that happen between two checks are picked up at the next run. If Make ever shows an instant tag on a KeaBuilder module, its documentation says to click Create a webhook first, then Create a connection.
04What if a KeaBuilder module is missing in Make?
It depends on what you need. The KeaBuilder app covers 13 modules: 7 triggers plus actions to create and update contacts, add or remove tags, and add or remove list members. There is no search module and no Make an API Call module, so Make cannot reach other KeaBuilder data through a custom request. A workaround is to handle that step in another app your scenario already uses. If the gap blocks a project, the Hack'celeration team can look at the flow with you.
05Should you use Make or n8n for KeaBuilder?
It depends on your criteria. In Make, KeaBuilder offers 13 ready-made modules, runs on the Free plan, and every trigger is scheduled. Before picking n8n, check whether a KeaBuilder node exists there and which actions it covers, because the same app often has one but coverage varies. Then compare what matters for your project: the events you need to catch, the actions you need, and how operations fit your plan. The comparison page linked above lays out those criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations