Resources · Make integration

Kantree Make integrationAutomate Kantree with Make.

Can Make create projects, update cards and invite people in Kantree for you? Yes. The Kantree Make integration gives you 18 modules, 13 actions and 5 searches, for teams who plan work in Kantree. This page links your account and walks you through a first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Kantree Make integration do for your team?

The Kantree Make integration lets a scenario, the automation you build in Make, work on your Kantree organizations, projects, cards and members. Each scenario is a chain of modules, one brick per step, and the Kantree modules are the ones that create, read, update or delete things in your account, fed by data coming from your other tools.

Client onboarding without the copy and paste. A new client signs, and Create an Organization, Create a Project and Invite a Project Member set up their space and bring their contact in. Nobody retypes a name or an email address.

Cards that follow reality. When a payment lands or a ticket closes in another tool, Search Cards finds the matching card and Update a Card changes it. Delete a Card cleans up the ones that no longer mean anything.

A project list you can report on. List Projects hands every project to the next module as a bundle, one item at a time, and Get a Project reads the details of a single one before you send them to a spreadsheet or a chat channel.

What Make cannot do here: Kantree has no trigger module, so a change inside Kantree never starts a scenario on its own. The scenario starts on its schedule or on an event in another app. For anything the listed modules skip, Make an API Call reaches the rest of the Kantree API. If you are new to the editor, the Make training covers the basics, and Make pricing explains how operations are counted. The same app often has an n8n node too; the n8n vs Make comparison helps you pick.

Connect

How do you connect Kantree to Make?

  1. 01

    Add a Kantree module

    Open your scenario in Make, add any Kantree module, then click Create a connection. The connection is your Kantree account linked to Make once and reused by every Kantree module afterwards.

  2. 02

    Name the connection

    The Connection name field is optional. Filling it still pays off when you run several Kantree accounts, because a clear name tells you at a glance which workspace a module talks to.

  3. 03

    Paste your credentials

    Enter the credentials you copied from Kantree, or follow the on-screen instructions. For an API key, go to your Kantree account settings, open the Developer section and copy the key shown there.

First scenario

Build your first scenario with Kantree

GoalWhen a deal is marked won in your CRM, Make creates the matching project in Kantree and invites the client contact to it.

  1. 01

    Start from your CRM

    Create a new scenario from the Scenarios page and click the + to add the first module. Kantree has no trigger, so this first module comes from the CRM where your deals are won.

  2. 02

    Add Create a Project

    Click the + on the right of the CRM module, search Kantree and pick Create a Project. Link your account, then map the deal name from the previous module so each project carries the client's name.

  3. 03

    Invite the client

    Add Invite a Project Member after it. Map the project created one step earlier and the contact's email address from the CRM, so the invitation goes to the right person in the right project.

  4. 04

    Test with Run once

    Click Run once and read the bundles each module received, which tells you whether the project name and the email went where you expected.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, which is every 15 minutes by default on a new scenario, then switch the scenario on. From there, every won deal gets its Kantree project.

Modules

What each Kantree module does

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

Kantree1

Create an Organization

Action

In MakeCreates a new organization.

Adds a new organization to Kantree without opening the app, so a fresh space is waiting the moment your scenario runs.

When to use it
you sign a client in your CRM and want a dedicated organization ready for them, named with data from the previous module.
Watch out
every run creates one more organization, so check the name Make sends with Run once before you switch anything on.
Kantree2

Create a Project

Action

In MakeCreates a new project.

Opens a new project in Kantree and passes its details to the next module, so you can invite people or add work to it in the same scenario.

When to use it
a form submission, a won deal or a signed quote should turn into a project without anyone copying the client name by hand.
Watch out
map the project name from real data rather than a fixed text, or you end up with a pile of projects sharing one title.
Kantree3

Delete a Card

Action

In MakeDeletes the selected card.

Removes a card from Kantree, which keeps boards clean when the work behind the card no longer exists anywhere else.

When to use it
an order is canceled in your shop or a support ticket is closed as spam, and the matching card should disappear too.
Watch out
treat a deletion as final and test on a throwaway card with Run once before the scenario goes live.
Kantree4

Delete an Organization

Action

In MakeDeletes the selected organization.

Wipes an entire organization out of Kantree, the heaviest cleanup this app offers in Make.

When to use it
a client contract ends and your offboarding process says their whole organization has to go, not only one project.
Watch out
treat this deletion as final: feed it an organization picked by Get an Organization or List Organizations and read the bundle carefully during Run once.
Kantree5

Delete a Project

Action

In MakeDeletes the selected project.

Takes a finished or abandoned project off Kantree, so the project list only shows work that is still alive.

When to use it
a deal is marked lost in your sales tool and the team should stop seeing the project that was opened for it.
Watch out
treat the deletion as final; if you only want to change its name or details, Update a Project is the safer module.
Kantree6

Get a Card

Action

In MakeReturns information about the selected card.

Reads one card and hands its information to the following modules as a single bundle.

When to use it
the scenario already knows which card matters, for example from an ID saved in a spreadsheet row, and you want its content in an email or a status message.
Watch out
it aims at one specific card; to look for cards you cannot name yet, start with Search Cards instead.
Kantree7

Get an Organization

Action

In MakeReturns information about the selected organization.

Brings back the details of one organization so later modules can reuse them without you typing anything.

When to use it
a scenario needs the organization's information before creating a project inside it or before sending a summary to an account manager.
Watch out
it returns one organization only; when you do not have its identifier at hand, run List Organizations first and map the one you need.
Kantree8

Get a Project

Action

In MakeReturns information about the selected project.

Fetches the current state of one project, useful right before the scenario makes a decision about it.

When to use it
you are about to update a project and want to read what it looks like first, or you want to post its details to the team chat.
Watch out
pair it with List Projects whenever the scenario does not already know which project it is dealing with.
Kantree9

Invite a Project Member

Action

In MakeInvites an email address or an existing user via its username.

Sends a project invitation in Kantree, either to an email address or to someone who already has a Kantree username.

When to use it
a new hire appears in your HR tool or a client signs, and they should land in the right project without a manual invite.
Watch out
map the email address from the previous module rather than typing it, otherwise the same person gets invited on every run.
Kantree10

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Reaches any endpoint of the Kantree API from your scenario, reusing the connection you already set up for the other modules.

When to use it
none of the ready-made modules covers the request you have in mind, and the Kantree API offers it.
Watch out
you write the request yourself, so keep the Kantree API documentation open next to Make while you fill in the module.
Kantree11

Update a Card

Action

In MakeUpdates the selected card.

Changes an existing card so Kantree reflects what just happened in another tool.

When to use it
a payment is received or a task is finished in another app, and the card must say so without someone editing it by hand.
Watch out
the module needs a card to aim at, so place Search Cards or Get a Card before it and map the card from their result.
Kantree12

Update an Organization

Action

In MakeUpdates the selected organization.

Edits an organization's details from a scenario, keeping Kantree in line with the tool your team treats as the reference.

When to use it
a client renames its company in your CRM and you want the Kantree organization to follow the change.
Watch out
a wrong mapping overwrites real details, so try it with Run once on a sample organization before switching the scenario on.
Kantree13

Update a Project

Action

In MakeUpdates the selected project.

Rewrites a project's details in Kantree when something changes upstream, without anyone reopening the project.

When to use it
a deal's scope changes in your sales pipeline and the project should carry the new information.
Watch out
placed after List Projects, it runs once per bundle, and each run is one operation, the unit Make counts on your plan.
Kantree14

List Invited Project Members

Search

In MakeLists invited project members.

Returns the people invited to a project, one bundle per invitation, ready for the next module.

When to use it
before inviting someone, to check whether an invitation already went out, or to send the invited people a reminder from your email tool.
Watch out
like every search module, it can return zero, one or many bundles, so the modules after it run as many times as there are results.
Kantree15

List Organizations

Search

In MakeLists all organizations.

Lists all organizations in your Kantree account, each one as its own bundle.

When to use it
a scenario has to go through every client, or find one organization by name before Get an Organization or Update an Organization.
Watch out
on a busy account this produces many bundles, and every module downstream then counts one operation per bundle.
Kantree16

List Project Members

Search

In MakeLists project members.

Returns the people already in a project, which is handy for building a team roster somewhere else.

When to use it
you want to copy a project's team into a spreadsheet, or notify everyone on it after an important change.
Watch out
the result depends on the project you pick, so map it from List Projects or Get a Project when the scenario handles several.
Kantree17

List Projects

Search

In MakeLists all projects.

Lists all projects in Kantree, each as its own bundle, ready to feed a report or a sync.

When to use it
a report needs to go through every project, or a scenario must find one project before updating it.
Watch out
if you already know the exact project you want, Get a Project is lighter, because it returns a single bundle instead of the whole list.
Kantree18

Search Cards

Search

In MakeSearches for specific cards or lists them all.

Finds specific cards, or pulls all of them when you leave the search open.

When to use it
you need the card tied to a customer or an order before Update a Card or Delete a Card acts on it.
Watch out
a search can match several cards; read the bundles during Run once so a later update does not touch more cards than you meant.
Need help

Need help automating Kantree with Make?

A person reads every message.

FAQ

Kantree and Make: common questions

01Is the Kantree Make integration free?
Yes, Kantree is a standard app, so it works on the Make Free plan. That plan allows 2 active scenarios, a minimum 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 and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. On the Kantree side, you still need an active account; check the Kantree pricing page for your subscription.
02What do you need to connect Kantree to Make?
An active Kantree account and one way to authenticate: an API key, or an OAuth 2 client ID and secret. The API key sits in your Kantree account settings, under the Developer section. In Make, add any Kantree module, click Create a connection, give it a name if you like, and paste the credentials or follow the instructions on screen. That connection then serves every Kantree module in all your scenarios.
03Can Kantree start a Make scenario in real time?
No. Kantree has no trigger module in Make, scheduled or instant, so nothing that happens in Kantree can launch a scenario by itself. You have two ways around it. Start the scenario with a trigger from another app, such as your CRM or a form tool, and use Kantree modules after it. Or let the scenario run on its schedule, every 15 minutes by default, and begin with List Projects or Search Cards to pick up what changed.
04What if a Kantree module is missing in Make?
Use Make an API Call. It calls any endpoint of the Kantree API with the same connection as the other modules, so you can cover what the 18 listed modules do not, as long as the Kantree API allows it. You write the request yourself, so keep the Kantree API documentation open. Also note that Make's own page for this app says its content was generated with AI from the Kantree documentation, so verify important details with Kantree.
05Should you use Make or n8n for Kantree?
It depends on the tool your team already uses. In Make, Kantree comes with 18 modules for organizations, projects, cards and members, plus Make an API Call for the rest, and it works from the Free plan. n8n often has a node for the same app, so check what it offers for Kantree before deciding. Compare the actions you actually need rather than the brand, and pick the platform where your other automations already run.