Resources · Make integration

Kwala Make integrationAutomate Kwala with Make.

Can your Kwala contacts keep themselves up to date? The Kwala Make integration gives you 5 modules: 1 trigger and 4 actions built around contacts. This guide is for sales and ops people who know Kwala and are new to Make, and it walks you from the API key to a working scenario.

Try the Kwala integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Kwala Make integration do for you?

The Kwala Make integration links your Kwala account to Make, a visual tool where you chain apps together without writing code. You build a scenario, which is the automation itself, out of modules: each module is one brick, such as a trigger that starts things or an action that changes a contact in Kwala.

New leads land in Kwala without retyping. When a form tool or a spreadsheet in another app receives a new person, Add a contact creates the matching record in Kwala. Your sales team opens the CRM and the lead is already there.

Records stay correct when details change. Update contact rewrites an existing Kwala contact with fresh data coming from another tool, and Delete a contact removes one when someone asks to be taken off your lists. Deleting is final, so it deserves a filter before it.

Kwala activity reaches the rest of your stack. Watch Action is the only trigger. The documentation gives no description of it, so run it once and look at what it returns before you rely on it.

What the app does not offer in Make: no search module and no instant trigger. For anything outside the listed modules, Make an API Call reaches the Kwala API with the same connection. If you are still choosing a tool, the n8n vs Make comparison and the Make review lay out the criteria, and Make pricing explains the plans.

Connect

How do you connect Kwala to Make?

  1. 01

    Copy your Kwala API key

    In Kwala, open the Settings page from your dashboard and find the section that shows your API key. Copy it. You need an active Kwala account for this; the key is what lets Make act on your data.

  2. 02

    Add a Kwala module in Make

    In your Make scenario, add any Kwala module and click Create a connection. A connection is your Kwala account linked to Make once, then reused by every Kwala module you add later.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps if you ever manage several Kwala accounts. Paste the API key you copied and follow the on-screen instructions to create the connection.

First scenario

Build your first scenario with Kwala

GoalWhen a new lead shows up in another app, Make creates that person as a contact in Kwala.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module. This one comes from the app where your leads arrive, like a form or a sheet.

  2. 02

    Pick the source of your leads

    Search that app by name, choose its trigger and connect your account. Make then lists the forms, sheets or objects it can read, so you pick one instead of typing it.

  3. 03

    Add the Kwala module

    Click the + on the right of the first module, search Kwala and choose Add a contact. Create the connection with your API key, then map the lead details from the first module into the fields Make shows for Kwala.

  4. 04

    Test with Run once

    Click Run once to run the scenario a single time. Each module shows the bundles it received, a bundle being one item, here one lead. Check in Kwala that the contact appeared.

  5. 05

    Schedule and switch it on

    Click the clock on the first module. A new scenario checks every 15 minutes by default; the Free plan cannot go below that. Then flip the scenario on and new leads keep flowing into Kwala.

Triggers

What starts a Kwala scenario

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

Kwala1Watch Action

Watch Action

triggerIn the docs only

Watch Action is the one Kwala module that can open a scenario, so it is your way to let something happening in Kwala set off work in other apps. The official documentation lists it without a description; the name suggests it follows actions in Kwala, but what exactly it returns is not documented.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, rather than hearing from Kwala the moment something happens.
When to use it
when an event in your CRM should push data to a spreadsheet, a chat tool or another database.
Watch out
click Run once with a recent action in Kwala and read the bundles before mapping anything, since no field list is published.
Modules

What the Kwala modules do

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

Kwala1

Add a contact

ActionIn the docs only

Add a contact creates a new person in your Kwala CRM from data another module hands over, so leads captured elsewhere reach your pipeline without copy and paste.

When to use it
right after a form, a signup or a new row in another app, when that person does not exist in Kwala yet.
Watch out
the documentation says nothing about duplicates, so run the scenario once with a lead already in Kwala and see what happens before you switch it on.
Kwala2

Delete a contact

ActionIn the docs only

With Delete a contact, a person disappears from Kwala as soon as the scenario reaches this step, which keeps your CRM clean when someone leaves or asks to be forgotten.

When to use it
when an unsubscribe, a churn signal or a removal request arrives from another tool and the record should go too.
Watch out
a deleted contact cannot be restored from Make, so place a filter before this module and test on a dummy record.
Kwala3

Make an API Call

ActionIn the docs only

Make an API Call lets you reach any endpoint of the Kwala API from your scenario, reusing the connection you already created. It fills the gaps the four ready-made modules leave open.

When to use it
when you need something no listed module does, such as looking up a contact before updating it.
Watch out
you write the request yourself, so keep the Kwala API documentation open and check the response bundle with Run once.
Kwala4

Update contact

ActionIn the docs only

Here the goal is fresh data: Update contact rewrites an existing Kwala record with new values coming from another step, like a changed phone number or company.

When to use it
when a person you already track edits their details in a form, a billing tool or a support desk and Kwala should follow.
Watch out
the module changes a contact that already exists, so the scenario has to know which one; add a lookup through Make an API Call if you lack that reference.
Need help

Need help automating Kwala with Make?

A person reads every message.

FAQ

Kwala Make integration: common questions

01Is the Kwala Make integration free?
Yes, on the Make side. Kwala is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) drop the interval to 1 minute and remove the cap on active scenarios. Every module run counts as an operation, the unit Make bills on. Your Kwala subscription is separate and set by Kwala.
02What do you need to connect Kwala to Make?
An active Kwala account and its API key. You find the key in Kwala under the Settings page of your dashboard, in the section that displays it. In Make, you add a Kwala module, click Create a connection, give it a name if you like and paste the key. That single connection then serves every Kwala module in all your scenarios, so you only do this once per account. If the key ever changes in Kwala, update it in the connection.
03Does the Kwala Make integration react in real time?
No. Its only trigger, Watch Action, is scheduled: Make checks Kwala on the scenario's schedule, every 15 minutes by default, and cannot go faster than that on the Free plan. Paid plans let you set a 1 minute interval. Kwala has no instant trigger in Make, meaning no webhook that alerts Make the moment something happens. If you need speed, start the scenario from another app that does offer an instant trigger.
04What if a Kwala module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Kwala API with the connection you already set up, so you can cover what Add a contact, Update contact and Delete a contact leave out, such as finding a contact first. Make itself flags its Kwala documentation as AI-generated from the vendor's docs and possibly wrong, so check important details with Kwala directly and test each call with Run once.
05Should you use Make or n8n with Kwala?
It depends on where your other tools live. In Make, Kwala comes with 5 modules, a scheduled trigger and Make an API Call for the rest, all usable from the Free plan. Many apps also have an n8n node, but this page does not confirm one for Kwala, so check the n8n catalog before choosing. Pick the platform that already connects the other apps in your workflow; the comparison linked above lists the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations