Resources · Make integration

KIS Make integrationAutomate KIS with Make.

Can Make keep your KIS collections current without any code? The KIS Make integration gives you 6 modules: 5 actions and 1 search. This guide is for teams already on KIS. It shows how to connect your account and build your first scenario.

Try the KIS integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the KIS Make integration do for you?

The KIS Make integration links your KIS account to Make, a tool where you build a scenario: an automation made of modules, each one a brick that reads or changes data in one app. Once your account is connected, a scenario can create, find, update and delete KIS data for you, with no code.

New records land in KIS without retyping. When a form tool or a CRM receives a new entry, its trigger starts the scenario and Create data writes a matching item into the KIS collection you pick. Each item that flows from one module to the next is called a bundle: one contact, one row.

Existing items stay current. Pair Search data with Update a data: the search finds the item, the update rewrites it with fresh values from the other app. A good fit for an operations team that keeps its reference list in KIS.

Cleanup follows the source. When a record is closed elsewhere, Delete a data removes its KIS counterpart. And before building anything, Get all collections returns, as its name says, the collections of your account.

One limit to know: KIS has no trigger in Make, so a scenario starts from another app or from a schedule. Whatever the six modules leave out goes through Make an API Call, which reaches any endpoint of the KIS API with the same connection. New to Make? The Make training starts from zero, and Make troubleshooting helps when a run fails. Weighing two tools? Read n8n vs Make.

Connect

How do you connect KIS to Make?

  1. 01

    Create an API access in KIS

    Start in KIS, not in Make. In your administration space, open the section for API access and create one if you do not have it yet. Note the App token and the Secret it shows, since Make asks for both.

  2. 02

    Add a KIS module and create the connection

    In your Make scenario, add any KIS module and click Create a connection. A connection is your KIS account linked to Make once, then reused by every KIS module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste your credentials

    Enter the App token and Secret you copied from KIS, or follow the on-screen instructions, then save. From there, Make lists what it can read in your account instead of making you type every value.

First scenario

Your first scenario with KIS

GoalWhen a new entry arrives in another app, Make finds the matching KIS item and updates it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Since KIS has no trigger, the first module comes from the app where your fresh data lives, for example a form tool.

  2. 02

    Add Search data

    Click the + to the right of that module, search for KIS and pick Search data. Choose your connection, then map the value from the first module that identifies the item you want.

  3. 03

    Add Update a data

    Place Update a data after the search. Point it to the item returned by Search data and map the new values from the first module. Make lists what it can read from KIS.

  4. 04

    Test with Run once

    Click Run once. The scenario runs a single time, and each module shows the bundles it received. Check that the search found the right item before you trust the update.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set Scheduling: a new scenario runs every 15 minutes by default. Then switch the scenario on, and KIS stays in line without you touching it.

Modules

What each KIS module does

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

KIS1

Create data

ActionIn the docs only

A fresh item appears in the KIS collection you choose, filled with values mapped from earlier modules, so nobody copies entries from one tool to another by hand.

When to use it
whenever a sign-up, request or order recorded in another app should also exist in KIS.
Watch out
run a search first if the same entry can arrive twice, or you will end up with duplicates.
KIS2

Delete a data

ActionIn the docs only

Items you no longer need leave KIS by following what happens in your source tool, instead of waiting for a manual cleanup.

When to use it
a record is closed or removed in another app and its KIS copy should go with it.
Watch out
test before you trust it. Do your first Run once on a throwaway item, and put a search just before so the module targets exactly one item.
KIS3

Get all collections

ActionIn the docs only

You get the collections of your KIS account back as bundles, as the module name says, which shows where data can be written before you build the rest.

When to use it
at the start of a scenario that has to pick a collection, or when you plan a new flow and want to see what exists.
Watch out
the doc says nothing about what each returned bundle holds, so read the output of a Run once before you map it.
KIS4

Make an API Call

ActionIn the docs only

Anything the five other modules miss becomes reachable: this module calls any endpoint of the KIS API with the connection you already set up.

When to use it
a KIS feature has no dedicated module and you still want it inside the same scenario.
Watch out
here you work with the API itself, so keep the KIS API documentation at hand and test each call with Run once.
KIS5

Search data

SearchIn the docs only

Matching KIS items come back into your scenario, ready for the next modules to read or change, without you opening the collection.

When to use it
right before an update or a deletion, to find the exact item the scenario should act on.
Watch out
a search can return zero, one or several bundles. Each bundle runs the following modules once and uses operations, the unit Make counts on your plan.
KIS6

Update a data

ActionIn the docs only

An existing KIS item picks up new values on its own, so the data your team relies on matches what changed in another tool.

When to use it
a status, an address or an amount changes in the source app and KIS should follow.
Watch out
the module has to know which item to change. Feed it the result of Search data rather than typing the item by hand.
Need help

Need help automating KIS with Make?

A person reads every message.

FAQ

KIS and Make: common questions

01Is the KIS Make integration free?
Yes, KIS is a standard app, available from the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, up to 5 minutes per execution, 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, remove the cap on active scenarios and allow 40 minutes per execution. Make counts usage in operations, one per module run on one bundle. Your KIS subscription is a separate matter that this page does not cover.
02What do you need to connect KIS to Make?
An active KIS account and an API access. In your KIS administration space, create an API access if you have none, then note the App token and the Secret it gives you. In Make, add any KIS module, click Create a connection, name it if you like, and paste the two values. The connection is saved once and reused by all six KIS modules, so there is no need to repeat the setup for each module you add later.
03Can a KIS scenario start as soon as something changes in KIS?
No, not from KIS itself: the app has no trigger in Make, neither scheduled nor instant. A scenario still has two ways to start. The first module can be a trigger from another app, such as a form tool or a CRM, with the KIS modules after it. Or the scenario runs on its own schedule, every 15 minutes by default on a new scenario, with Search data or Get all collections as the first step. An instant trigger, which an app calls through a webhook, can only come from that other app.
04What if the KIS module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the KIS API with the connection you already have, so a missing feature does not force you out of the scenario. The other five modules cover the everyday work: create, search, update and delete data, plus listing collections. One caution: the KIS documentation in Make is short and flagged as AI-generated from the vendor docs, so check important details with KIS directly before you rely on them.
05Make or n8n for KIS?
It depends on your criteria, not on a winner. In Make, KIS comes with 6 modules, Make an API Call included, and a scenario is built visually from the Scenarios page with no code. Many apps also have an n8n node, so check whether KIS has one before you choose, then compare how each tool fits the apps your team already uses. The n8n vs Make comparison on this site sets out both tools side by side, without naming a winner for KIS.
Same platform

Other docs you might need on this stack.

Browse all integrations